We are considering to drop support for finding Tests and TestFixtures based on naming conventions, e.g. fixture names end with Test and tests starting with Test.
Instead we'd like to change the specification so that it becomes a requirement to use attributes, e.g. TestFixtureAttribute and TestAttribute, to mark fixtures and tests.
The benefits would be simplified code with less options for defects. Also, use of csUnit would be more consistent with TestAssemblyFixtureAttribute etc.
The impact would be that all test fixtures and all tests that still rely on naming convention would have to be augmented by assigning the TestFixtureAttribute to all fixtures and TestAttribute to all tests. Depending on the number of tests this might a substantial work.
Please feel free to comment!
Kind regards,
Manfred.
---
Manfred Lange
csUnit co-author
manfred at csunit dot org
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
We are considering to drop support for finding Tests and TestFixtures based on naming conventions, e.g. fixture names end with Test and tests starting with Test.
Instead we'd like to change the specification so that it becomes a requirement to use attributes, e.g. TestFixtureAttribute and TestAttribute, to mark fixtures and tests.
The benefits would be simplified code with less options for defects. Also, use of csUnit would be more consistent with TestAssemblyFixtureAttribute etc.
The impact would be that all test fixtures and all tests that still rely on naming convention would have to be augmented by assigning the TestFixtureAttribute to all fixtures and TestAttribute to all tests. Depending on the number of tests this might a substantial work.
Please feel free to comment!
Kind regards,
Manfred.
---
Manfred Lange
csUnit co-author
manfred at csunit dot org