akuhn/SUnit, chrisma edition :)

Name: SUnit-AdrianKuhn.122
Author: AdrianKuhn
Time: 29 December 2009, 5:14:01 pm
UUID: cc99ab5b-294e-4142-a5da-baf8af550a0f
Ancestors: SUnit-AdrianKuhn.120

Renamed assumptions to #skipUnless:.

As suggested on mailing list renamed #assumeThat: to #skipUnless. A skipped
 test is marked as 'skipped' which counts as passed and is thus a green result.
 Also, added unconditional #skip message.


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

> This is an aspect that I changed. An outcome is unexpected if and  
> only if it
> does not match what is in the stored history. (For compatibility only
> #expectedFailures are added to the stored history.) So the preferred  
> way to
> mark an outcome as unexpected is to store the history.


Ok, I understand now.
Could be okay. But how can I distinguish an expected failure from a  
real failure ? At the first run, I get some failed tests. Are they  
real or expected failures?

Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.






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