OK, but it might be worth having a way to show when expected failures end up actually passing.
Not sure how best that would read or how it would be done with what is there. Its quite hard to think of a concise wording which captures all information.
However it could be very useful to know when an expected failure starts passing.
Michael Whapples On 06/06/2014 18:43, Mesar Hameed wrote:
On Fri 06/06/14,18:17, Michael Whapples wrote:One point I would raise about expected failing tests, even with a bug tracker it can be useful as if an expected failure does not happen, then some other code change (may be totally unintentional) has fixed an existing bug and one could then go into the tracker and mark the bug as fixed with unknown solution.yes you are right.Would this test system report expected failures actually passing?no, it shows them as expected failures. I do feel that we should be adding a lot more tests, initially this will take time away from development, but will definitely be worth while and will make both projects more robust. The nature of the libraries also makes testing relatively straightforward. Mesar
For a description of the software, to download it and links to project pages go to http://www.abilitiessoft.com
