Mariano Martinez Peck <marianopeck@...> writes:
So, what I would do is to "fix" it but (I don't know) put is as deprecated so that all the tests of the people are still green and give them time to change it to expectedErrors or similar. After a second release you can remove this fix :) What do you think?
Yes, that is how I planned it ... and then you came with your dynamically generated expectations. Which the new system does not support. It's an awesome idea, so I am thinking about a way to support dynamic expectations in the new system. I have one solution in mind: given your #expectedFailures, would the following work for you? testBlob self assume: SqueakDatabaseAccessor DefaultDriver ~~ SqueakDBXDriver. ... which runs the test if and only if the default driver is not SqueakDBXDriver. This would have the same effect as your #expectedFailures implementation, where you expected an error for that case. Like this your expectation is put closer to the code. --AA