Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Sirius/Automated Tests
< Sirius
Revision as of 12:56, 11 December 2013 by Hugo.marchadour.obeo.fr (Talk | contribs) (Created page with "Sirius comes with a huge set of legacy tests (JUnit and SWTBot) that need to passe the eclipse IP and License clean. Besides, the move to Eclipse gives the opportunity to thin...")
Sirius comes with a huge set of legacy tests (JUnit and SWTBot) that need to passe the eclipse IP and License clean. Besides, the move to Eclipse gives the opportunity to think back automated tests.
Note: the rules defined below are not yet finalized and implemented. See the discussions at https://bugs.eclipse.org/bugs/show_bug.cgi?id=423663. Feedback welcome.
General Rules
- Automated Tests will be physically stored in a dedicated folder called "tests"
- A test can be:
- a unit test
- an integration test
- a UI test
- Each plugins can have its releated test plugin
${plugin-name}.tests- All unit tests follow the package of the class under and are stored in
/unit - All integration tests are stored in
/integ
- All unit tests follow the package of the class under and are stored in
- Each UI plugins can have an additional UI test plugin
${plugin-name}.tests.swtbot