Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] Junit testing of CDT components

That could work as well. I would suggest keeping all the tests that triggers bugs in the source, but commented out instead of leaving them out, as it makes it a lot less work for developers to verify their bug fixes. With the way junit works this may be the best solution. Any objections to this?

Ed Burnette wrote:

How about:
5 - Add only tests that work (leave out or comment out the ones that don't work). A suite is a lot easier to work with if there are no errors. When a bug is fixed, then a test that verifies it could be added.

-----Original Message-----
From: Peter Graves [mailto:pgraves@xxxxxxx] Sent: Monday, January 27, 2003 4:10 PM
To: cdt-dev@xxxxxxxxxxx
Subject: [cdt-dev] Junit testing of CDT components

Hey all,
I have been working on the CDT JUnit test suites, and wanted to put a question out to the community.

My question related to test cases that trigger bugs that have bugzilla reports against them, but will not be fixed for a while. In this case with the current setup these failures will show up every time the tests are run, and make it a bit harder to pull out the new failures. What do people think we should do about this? Some options that have come to mind are:
cdt-dev mailing list

Back to the top