TestingGuidelines: Difference between revisions
From KitwarePublic
Jump to navigationJump to search
Daviddoria (talk | contribs) No edit summary |
Daviddoria (talk | contribs) No edit summary |
||
| Line 7: | Line 7: | ||
* The "main()" function of the test file must be called TestClassName(int, char*[]) | * The "main()" function of the test file must be called TestClassName(int, char*[]) | ||
==Questions== | |||
* Do we bother covering deprecated classes? | |||
* Is there a way to mark deprecated classes as deprecated so they do not show up on the coverage dashboards? | |||
Revision as of 18:52, 21 August 2010
- When adding a new concrete class, a test should also be added in
...VTK/Package/Testing/Cxx/
- The name of the file for the test should be ClassName.cxx where the name of the class is vtkClassName.
- Each test should call several functions, each as short as possible, to exercise a specific functionality of the class. 1,000 lines in main() is very hard to maintain...
- The "main()" function of the test file must be called TestClassName(int, char*[])
Questions
- Do we bother covering deprecated classes?
- Is there a way to mark deprecated classes as deprecated so they do not show up on the coverage dashboards?
