Issue 4566 in pharo: SUnit: Fix for tagging expectedFailure using pragmas

Status: Accepted
Owner: [hidden email]
Labels: Type-Feature Milestone-1.4

New issue 4566 by [hidden email]: SUnit: Fix for tagging  
expectedFailure using pragmas
http://code.google.com/p/pharo/issues/detail?id=4566


testShouldFail
       <expectedFailure>
       self fail.


... this is already there but disabled as it was too slow. Attached change  
set enables it with a
better caching.

Attachments:
        expectedfails.1.cs  678 bytes


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

Comment #1 on issue 4566 by [hidden email]: SUnit: Fix for tagging  
expectedFailure using pragmas
http://code.google.com/p/pharo/issues/detail?id=4566

Lukas says: Igor, why do you search up to Object? It should be enough to  
search to
TestCase only.



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

Updates:
        Status: Closed

Comment #2 on issue 4566 by [hidden email]: SUnit: Fix for tagging  
expectedFailure using pragmas
http://code.google.com/p/pharo/issues/detail?id=4566

in 14067


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