Issue 4132 in pharo: Deprecate LongTestCase

Status: Accepted
Owner: [hidden email]
CC: [hidden email]

New issue 4132 by [hidden email]: Deprecate LongTestCase
http://code.google.com/p/pharo/issues/detail?id=4132

 From COTDC:

Laurent:
> I'm the base class for TestCases which take long time to run and that may  
> be discarded from default SUnit runs.

> It seems to me it's not supported by tools.

> (Personnally I think long tests should be better tagged with pragma  
> instead of subclassing).

Marcus:

Yes, we should remove (deprecate) this...


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

Comment #1 on issue 4132 by [hidden email]: Deprecate LongTestCase
http://code.google.com/p/pharo/issues/detail?id=4132

oups: How do we deprecate a Class ?


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

Comment #2 on issue 4132 by [hidden email]: Deprecate LongTestCase
http://code.google.com/p/pharo/issues/detail?id=4132

ok found


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

Comment #3 on issue 4132 by [hidden email]: Deprecate LongTestCase
http://code.google.com/p/pharo/issues/detail?id=4132

But we have really LongTest so may be before removing it we should try to  
see if we cannot use it.


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

Comment #4 on issue 4132 by [hidden email]: Deprecate LongTestCase
http://code.google.com/p/pharo/issues/detail?id=4132

It's only used by DecompilerTest.

I think it's dangerous to leave it in this state because actually  
DecompilerTests are not run, even on Hudson (see  
https://pharo-ic.lille.inria.fr/hudson/view/Pharo/job/Pharo%20Core%201.3/lastCompletedBuild/testReport/CompilerTests/ 
- not here) and there's 2 errors out of 54 tests on a Pharo1.3 one click  
image.




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

Comment #5 on issue 4132 by [hidden email]: Deprecate LongTestCase
http://code.google.com/p/pharo/issues/detail?id=4132

Yes but if the behavior is good and this is just because we never look at  
it then may be it is worth to look at long tests and turn them in  
LongTestCase?

What I want to say is that "not used in morphic/etoy = removed" makes sense  
after for the rest we should pay attention because doing is slower and more  
difficult than removing things.


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