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


Test Development


Test Execution


SIDs

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.


Item Types


Test SuiteJBTEA 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.
TestJSESA 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.

Test SpecificationJTSP

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 CaseJTCSThis is a description on how something should be verified. It contains the Sequence(s) and can link to one or several requirements.
Abstract ArtifactAARThis represents the System Under Test or Test System that is being tested. Artifacts can inherit from an Abstract Artifact.
ArtifactIARThis represents the System Under Test or Test System that is being tested. This can be an instance of Abstract Artifact.
Test Case ScriptJTCAA Test Case Script is a test case that can contain Test Scripts.
Test ScriptJTSCA 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 ScopeJTSDA 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).


Part Types




OwnerDefining Type (DefObj)
Sub-Test SuiteISSSJBTEJBTE
TestISESJBTEJSES
Test DescriptionISSPJSESJTSP
Test CaseITECJTSPJTCS
Test Specification ItemITSIJTSPI
Test Specifications RequirementsITTRJTSPRQ
Test Case RequirementITRQJTCSRQ
Test ObjectISSUJSESAAR
Test SystemIRTSJSESAAR
Test ScopeISSCJBTEJTSD
Test SpecificationITTXJTSDJTSP
SpecificationIBSFJTSDI
Sub Test ScriptISTSJTSCJTSC
Test Case BehaviorITCBJTCAJTSC


Attributes


Test Case StatusPTCS
Test Sequence listTSQL
Test Sequence Result ListTSRL
AnnotationABAN
Development StatusDEST
Review Status3RST
Rvf AnnotationARAN
Test Procedure SequenceTPSQ
Test Script Reference DeprecatedTSCR
Test Script VersionPTSV
Test Script StatusPTSS
Test Script ActionTSCA
Test Script Expected ResultTSCE
Test Script Result CommentTSRC
Test Script RefTSRE

Extended Model SIDs


Item Types


Test ProcedureJSTP
Abstract Test ProcedureJATP
Formal Function ListJFFL


Part Types


Old Sub-Test SuiteITSS
Sub ArtifactISUA
Main Test ProcedureISVP
Sub Test ProcedureIQTP
Abstract Test Procedure TC AllocIPTA
Controlled SystemISCT

Test Views

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. 


ViewDescription

Coverage

View pie chart of requirement coverage and test case results.

Create test

Create new tests from test specifications.

Requirements

Add and remove requirements to the test specification.

Result grid

View results in grid that supports grouping by column.
Result historyView result from multiple tests or test suites in grid
Scope resultView result in grid that supports grouping by column.
Test ProtocolManage test results
Test case editorEdit description and test case sequences.
Test case managerCreate test cases and add/remove requirements to them.
Test configurationSet test configuration and SUT (system under test).

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: