On Mon, Dec 28, 2009 at 2:27 AM, Adrian Kuhn <akuhn@iam.unibe.ch> 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.
Hi Adrian! Thanks for trying to fix this. However, I can still reproduce the problem. I put a halt in my expectedFailures method and it is being called, here: importExpectedFailures: aTestClass aTestClass new expectedFailures do: [ :each | self testFinished: (TestFinished new testClass: aTestClass; selector: each; outcome: TestFinished failures; yourself) ] The iteration throught the do: seems to be ok, but I don't know why, the tests are still considered as error (red) instead of expectedFailures in green. Is correct to put "outcome: TestFinished failures;" ??? I guess it would be something like "outcome: TestFInished expectedFailures" but I look in the class side methods of TestFInished and I only see passed, failure and error. Let me know if I can test something more. The versions I am using are: SUnit-AdrianKuhn.116 SUnitGUI-AdrianKuhn.58 Cheers Mariano
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project