Thanks for sharing the experience :)
It sounds true, and I hope we will manage to have some good doc for Spec
and that the code will reach a good quality level :)
Ben
On 09 Jan 2014, at 14:44, Sven Van Caekenberghe s...@stfx.eu wrote:
One thing I have learned (about myself) is this: first you
We should have a policy on this. I've been guilty of writing new features
without tests too. It's bad enough we have to deal with untested legacy
code, but to replace key parts of the system with untested code doesn't seem
like such a good idea. In particular, the latest Spec refactoring broke a
+1 to just add things with appropriate tests.
in the case of Spec in particular, the problem is that is really hard to have
UI testing :(
Also… sometimes you break backward compatibility, that’s inevitable… and is ok
if is for the best (like in the case of Spec… it was to gain ui platform
+1
So, what do we do to make it happen?
Doru
On Thu, Jan 9, 2014 at 12:28 PM, Esteban Lorenzano esteba...@gmail.comwrote:
+1 to just add things with appropriate tests.
in the case of Spec in particular, the problem is that is really hard to
have UI testing :(
Also… sometimes you break
Le 09/01/2014 12:28, Esteban Lorenzano a écrit :
+1 to just add things with appropriate tests.
in the case of Spec in particular, the problem is that is really hard to have
UI testing :(
I'd say that Pharo makes it easy to do UI testing. Look, you can test an
app by opening a window,
EstebanLM wrote
in the case of Spec in particular, the problem is that is really hard to
have UI testing :(
I don't mean to pick on Spec. I'm very grateful for all the work Ben is
doing. It's just that it has become essential to getting any work done in
Pharo, and is undergoing a lot of
On 09 Jan 2014, at 18:14, Benjamin benjamin.vanryseghem.ph...@gmail.com wrote:
For Spec, I actually sent a mail in the mailing list when integrated
explaining how to move to the new version :)
But indeed, not enough documentation about it is present, this is why I am
currently spending
As usual the problem is that it takes time :)
(and also that I am a newbie when it comes to write :P)
Ben
On 09 Jan 2014, at 14:26, Sven Van Caekenberghe s...@stfx.eu wrote:
On 09 Jan 2014, at 18:14, Benjamin benjamin.vanryseghem.ph...@gmail.com
wrote:
For Spec, I actually sent a mail
One thing I have learned (about myself) is this: first you write a cool piece
of library/framework/tool/... and you make it as good and as clean as possible
(first iteration).
When you write unit tests (which you should do during development, let's leave
in the middle whether that should be
