Hi! Apparently, expectedFailure has a different behavior from the original SUnit. I have a test method declared in a expectedFailures method. However, this test method does not fail, but it triggers a MNU. Running the unit test tells me there is 1 error, the method that I declared as expectedFailure. I guess this behavior is the right one.
How can I fix this? There is no sender or implementer of expectedErrors. By the way, why TestCase>>expectedFailures is in the protocol 'history management'? There is also two empty method categories in TestCase. Cheers, Alexandre On 28 Dec 2009, at 02:27, Adrian Kuhn wrote: > Name: SUnit-AdrianKuhn.115 > Author: AdrianKuhn > Time: 28 December 2009, 2:22:16 am > UUID: 21af8078-0c75-4323-89aa-5f0142fa09d4 > Ancestors: SUnit-AdrianKuhn.114 > > Takes #expectedFailure into account. > > As required by Mariano Martinez Peck on the mailing list. He > uses the #expectedFailure method to dynamically create > expected failures, rather than a fixed set of failures as is > stored in stored history. > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project@lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
