Jump to: navigation, search

Difference between revisions of "Sirius/Automated Tests"

(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...")
 
 
(One intermediate revision by one other user not shown)
Line 15: Line 15:
 
** All '''integration tests''' are stored in <code>/integ</code>
 
** All '''integration tests''' are stored in <code>/integ</code>
 
* Each UI plugins can have an additional UI test plugin <code>${plugin-name}.tests.swtbot</code>
 
* Each UI plugins can have an additional UI test plugin <code>${plugin-name}.tests.swtbot</code>
 +
 +
== Samples ==
 +
 +
[[File:SiriusSampleOfTestDependencies.png]]
 +
 +
[[Category:Sirius]]

Latest revision as of 06:33, 24 December 2013

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
  • Each UI plugins can have an additional UI test plugin ${plugin-name}.tests.swtbot

Samples

SiriusSampleOfTestDependencies.png