Difference between revisions of "Testing"

From Developer Documents
Jump to navigation Jump to search
Line 13: Line 13:
 
[http://www.simantics.org/jenkins/view/Testing/job/Simantics%20Regression%201/ Simantics Regressions 1] is the main suite for simantics database regression tests. In this suite there is only the tests that will pass every time. If some test fails it will be moved to Simantics Regressions 2.
 
[http://www.simantics.org/jenkins/view/Testing/job/Simantics%20Regression%201/ Simantics Regressions 1] is the main suite for simantics database regression tests. In this suite there is only the tests that will pass every time. If some test fails it will be moved to Simantics Regressions 2.
  
== Simantics Regressions 2 ==
+
=== Simantics Regressions 2 ===
  
 
[http://www.simantics.org/jenkins/view/Testing/job/Simantics%20Regression%202/ Simantics Regressions 2] is the secondary suite for simantics database regression tests. This suite is the place for tests that have previously passed but then during the current sprint turned out to be failure.  After every sprint this suite will be cleaned and the tests that passes in this suite will be moved to Simantics Regressions 1. Tests that fails  will be either moved to Simantics Regressions 3 or dumpster.
 
[http://www.simantics.org/jenkins/view/Testing/job/Simantics%20Regression%202/ Simantics Regressions 2] is the secondary suite for simantics database regression tests. This suite is the place for tests that have previously passed but then during the current sprint turned out to be failure.  After every sprint this suite will be cleaned and the tests that passes in this suite will be moved to Simantics Regressions 1. Tests that fails  will be either moved to Simantics Regressions 3 or dumpster.
  
== Simantics Regressions 3 ==
+
=== Simantics Regressions 3 ===
  
 
[http://www.simantics.org/jenkins/view/Testing/job/Simantics%20Regression%203/ Simantics Regressions 3] is the suite for tests that will be repaired during current sprint and then moved to Simantics Regressions 1.
 
[http://www.simantics.org/jenkins/view/Testing/job/Simantics%20Regression%203/ Simantics Regressions 3] is the suite for tests that will be repaired during current sprint and then moved to Simantics Regressions 1.
  
== Simantics Regressions 4 ==
+
=== Simantics Regressions 4 ===
  
 
[http://www.simantics.org/jenkins/view/Testing/job/Simantics%20Regression%203/ Simantics Regressions 4] is the suite for tests that have been put on hold but maybe in future will be revived or not.
 
[http://www.simantics.org/jenkins/view/Testing/job/Simantics%20Regression%203/ Simantics Regressions 4] is the suite for tests that have been put on hold but maybe in future will be revived or not.

Revision as of 10:07, 7 February 2012

Overview

The testing section gives information about tests and their results. The build setups and automation are also explained here.

General

Tests will be a plug-in under org.simantics.tests and the tests will be run on jenkins in the section tab called Testing. All the tests and their results can be found on here

Test suites

Simantics Regressions 1

Simantics Regressions 1 is the main suite for simantics database regression tests. In this suite there is only the tests that will pass every time. If some test fails it will be moved to Simantics Regressions 2.

Simantics Regressions 2

Simantics Regressions 2 is the secondary suite for simantics database regression tests. This suite is the place for tests that have previously passed but then during the current sprint turned out to be failure. After every sprint this suite will be cleaned and the tests that passes in this suite will be moved to Simantics Regressions 1. Tests that fails will be either moved to Simantics Regressions 3 or dumpster.

Simantics Regressions 3

Simantics Regressions 3 is the suite for tests that will be repaired during current sprint and then moved to Simantics Regressions 1.

Simantics Regressions 4

Simantics Regressions 4 is the suite for tests that have been put on hold but maybe in future will be revived or not.

Current Database Tests

Current tests (db-tests)