Re: --XFAIL--

On Sun, May 25, 2008 at 7:21 PM, zoe <zoe.slattery@googlemail.com> wrote: > > Hi > > I've just modified run-tests.php to handle an --XFAIL-- section. The intent > of --XFAIL-- is so that people can use it when they have tests that they > know will fail. > > For example, an --XFAIL-- section might look like this: > > --XFAIL-- > This test will fail until bug #123456 is fixed > > Or like this: > > --XFAIL-- > This test will fail until function whatever() has been written > > In general the idea is to be able to mark a set of tests that you don't want > to worry about right now (for whatever reason) so that it makes it slightly > easier to pick out unexpected failures. > > I'll add some notes to the QA pages - if anyone sees any problem with it > please let me know. I made the changes in PHP5.3 and PHP6. > > Zoe Hi, while I am still only studying how this testing is done in PHP if I understand what you are trying to do is a concept the Perl community marks as TODO. That is tests that check some feature that is either broken or not yet implemented. The harness tool - run-tests.php - in this case is then says OK when this test fails. Then when the test starts to succeed the harness can report about this. Earlier the harness used to report "unexpected success" now it just says something TODO passed: 3 marking the test number that was marked as TODO but unexpectedly succeeded. You can see a visualization of it on the Parrot test suit as well: http://smoke.parrotcode.org/smoke/ (currently the first report has one such result) regards Gabor -- Gabor Szabo http://www.szabgab.com/blog.html Test Automation Tips http://szabgab.com/mailman/listinfo/test-automation-tips