Apparently, expectedFailure has a different behavior from the original SUnit.
Yes, now as you mention errors. In the original it has the (undocumented) behavior of declaring expected failures *and* errors. I'll see how I can fix that.
Maybe introducing a method expectedErrors would do the thing.
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.
The preferred way is to store your results into the stored history. You can store the history with the context menu in the test runner. To do so, right click in the colored status field and choose `store history`. The stored results are treated as the expected results then.
Yes, but... how is this related to the expectedError?
By the way, why TestCase>>expectedFailures is in the protocol 'history management'? There is also two empty method categories in TestCase.
The empty protocols are left overs of the old implementations. I dont know how to tell gofer/monticello to delete them. Do you know how?
No idea. But this looks like to be a bug in Monticello no? Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.