errors in a test simply cause the test to dissappear no diagnostics are produced

[Andy Whitcroft]

When updating a test if an error is introduced into the test definition it simply dissappears from the test sequence. No diagnostics are produced at all to indicate why the test was skipped or indeed that it was. This is a nightmare for a test developer.

[Daniel Manrique (roadmr)]

Hi Andy,

Could you perhaps provide steps to reproduce this? Usually if a test case is invalid an error is logged and is clearly marked with ERROR in the logfile.

Also, this was reported a while ago, so it's possible that the behavior has changed / improved in the meanwhile.

Still, it would be a great help if you could provide steps to reproduce, for instance, a test case definition with an error that we could try running to see what happens.

Thanks!

[Daniel Manrique (roadmr)]

It's been more than 60 days so I'll take that as confirmation that this bug is no longer relevant and mark as Fix Released, since errors are identified in the logfile, which should address the original reporter's concern.

If you feel this is inaccurate, please reopen and detail any remaining concerns.

Thanks!