The SystemWeaver Test Solution provides test organizations with powerful tools for the many common test tasks such as creating tests from requirements, traceability, test execution, requirements coverage, test system management, test analysis and test scripts. And in SystemWeaver, it is all customizable. However, the views described in Working with the Test Solution do depend on a specific meta model that is hard-coded. For the views to work properly, the SIDs listed in this article must be used. Similarly, these SIDs should not be used for other item, part and attribute types in the database.
Test Meta Model
Alternatively, using abstract types for Test Scope, Test Specification and Test case.
Below is a list of the above test and verification hard-coded SIDs for Items, parts as well as the SIDs for attributes. The names can be changed, but the SIDs must remain as specified.
|Test Suite||JBTE||A Test Suite represents one or many Tests. A Test Suite may include one or many sub Test Suites. This offers a flexible way of organizing many Tests, according aspects like different System under Test, different test runs or iterations, or tests performed by different organizations or persons.|
|Test||JSES||A Test represents a test of the System Under Test (SUT) as part of a Test System according to a Test Specification. The Test holds the result of the test as separate Test Status attribute values of each of the Test Cases included in the Test Specification.|
In addition to the Test Status there can be additional attributes, like comments on the outcome of each Test Case.
The Test Specification (TS) contains a description about what and how something should be verified. The TS hold Test Cases and the connection to the Requirement Specification. The test that can be performed according to a TS is assumed to be possible to complete in an un-interrupted sequence. If this condition cannot be fulfilled, the TS should preferably be split into separate TSs.
|Test Case||JTCS||This is a description on how something should be verified. It contains the Sequence(s) and can link to one or several requirements.|
|Abstract Artifact||AAR||This represents the System Under Test or Test System that is being tested. Artifacts can inherit from an Abstract Artifact.|
|Artifact||IAR||This represents the System Under Test or Test System that is being tested. This can be an instance of Abstract Artifact.|
|Test Case Script||JTCA||A Test Case Script is a test case that can contain Test Scripts.|
|Test Script||JTSC||A set of instructions that will be performed on the system under test to test that the system functions as expected. It is a single behavior of a Test Case Script.|
|Test Scope||JTSD||A set of test cases that defines a “test project” organised as a set of test specifications. A test scope has a part relation called specification, which points to the item under test (scope).|
|Owner||Defining Type (DefObj)|
|Test Specification Item||ITSI||JTSP||I|
|Test Specifications Requirements||ITTR||JTSP||RQ|
|Test Case Requirement||ITRQ||JTCS||RQ|
|Sub Test Script||ISTS||JTSC||JTSC|
|Test Case Behavior||ITCB||JTCA||JTSC|
|Test Case Status (i.e., the test result)||PTCS||Node attribute*|
|Test Sequence list||TSQL||On Test Case (JTCS)|
|Test Sequence Result List||TSRL||Node attribute on Test Case (JTCS)*|
|Annotation||ABAN||Node attribute on Test Case (JTCS)*|
|Rvf Annotation||ARAN||Node attribute on Test Case (JTCS)*|
|Test Procedure Sequence||TPSQ|
|Test Script Reference Deprecated||TSCR||On Test script (JTSC)|
|Test Script Version||PTSV||On Test script (JTSC)|
|Test Script Status||PTSS||On Test script (JTSC)|
|Test Script Action||TSCA||On Test script (JTSC)|
|Test Script Expected Result||TSCE||On Test script (JTSC)|
|Test Script Result Comment||TSRC||Node attribute on Test Script (JTSC)**|
|Test Script Ref||TSRE||On Test script (JTSC)|
* Requires the top node for Test in the context of Test Specification (i.e., TopNode/ISSP/ITEC if standing on a test case and using the Path Query language.
** Requires the context TopNode/ISSP/ITEC/ITCB.
Extended Model SIDs
|Abstract Test Procedure||JATP|
|Formal Function List||JFFL|
|Old Sub-Test Suite||ITSS|
|Main Test Procedure||ISVP|
|Sub Test Procedure||IQTP|
|Abstract Test Procedure TC Alloc||IPTA|
A list of the available test views can be found in Configure the explorer. Activate the ones you would like to utilize in your system.
|View pie chart of requirement coverage and test case results.|
|Create new tests from test specifications.|
|Add and remove requirements to the test specification.|
|View results in grid that supports grouping by column.|
|Result history||View result from multiple tests or test suites in grid|
|Scope result||View result in grid that supports grouping by column.|
|Test Protocol||Manage test results|
|Test case editor||Edit description and test case sequences.|
|Test case manager||Create test cases and add/remove requirements to them.|
|Test configuration||Set test configuration and SUT (system under test).|
|Create Test Plan extension view||For use when Test Cases or Test Scripts that can have parameters need to have their values specified before the actual tests are performed.|
Configuring Test Requirements Structure Tree View Setting
To ensure that the Requirements and Coverage views in the test solution work as expected, you will need to configure a "Test Requirements" structure tree view setting for the Test specification item type(s) in your test model.
To do this, open the Test specification item on a tab so that it is the top-level item.
Then, right-click on the Test specification item and select Save active settings to new view. Enter the name "Test Requirements" and click OK. (For more information on creating tree view settings, see Configuring Tree View Settings.)
Note: The name of the new view must be "Test Requirements", i.e., exactly the same spelling and same case (upper and lower) of the letters.
If the structure tree setting is not created, users will not see requirements listed in the views: