Issue 7367 in pharo: Add support for Phexample to Nautilus and cleanup testing for test methods a bit

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
22 messages Options
12
Reply | Threaded
Open this post in threaded view
|

Re: Issue 7367 in pharo: Add support for Phexample to Nautilus and cleanup testing for test methods a bit

pharo

Comment #20 on issue 7367 by [hidden email]: Add support for Phexample to  
Nautilus and cleanup testing for test methods a bit
http://code.google.com/p/pharo/issues/detail?id=7367

Hm, well, I added it to Nautilus because it wasn't easily extensible.
But actually, Phexample should come with a Nautilus plugin instead.

Just making the TestRunner executing 'should*' methods is not the way
to go. You need the framework to write proper Example driven tests...


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker
Reply | Threaded
Open this post in threaded view
|

Re: Issue 7367 in pharo: Add support for Phexample to Nautilus and cleanup testing for test methods a bit

pharo

Comment #21 on issue 7367 by [hidden email]: Add support for  
Phexample to Nautilus and cleanup testing for test methods a bit
http://code.google.com/p/pharo/issues/detail?id=7367

@stefan: I agree that a framework is the best solution, but I believe that  
even the mental shift from "test" to "should" moves us toward focusing on  
specifying behavior instead of testing. In addition, TestRunner and  
Nautilus are now inconsistent. There should be one definition of what a  
test method is, and everyone should use it - not Nautilus has one idea and  
TestRunner has another. If there is something that can't be extended that  
limits our expression, let's fix that!


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker
12