This web template shows the distribution of the status or priorities of messages, by test plan, test package or business process. You can analyze and filter the message data by project or solution structure, or test plan attribute search criteria, and call messages directly.
You have selected the BW report in the Test Management work center, in the view Test Reports or Reports.
The web template gives you an overview of the processing of messages created by testers while performing test plans. The following basic display formats are available for your analysis, in the table and in two graphics:
Number of messages with a specified priority and resulting status
Number of messages with a specified status and resulting priority
By default, the filter is the date of the last data extraction.
There are also various filter levels, which you can expand:
Test plans
Business process hierarchy nodes
Test packages
You can change the display of the message data, by adding attributes as expansions of the axes. You can also filter the display by attribute values.
Attributes | Restriction by |
Calendar day | Number of messages with this processing status, on a specified calendar day |
Message priority | Number of messages with a specified message priority |
Message status | Number of messages with a specified message status |
Test plan | Number of messages with a specified processing status, per test plan |
Test sequence | Number of messages with a specified processing status, per test sequence |
Test package | Number of messages with a specified processing status, per test package |
Nodes | Number of messages for test cases which are assigned to specified business process hierarchy nodes |
Project | Number of messages for test cases in a project |
Solution | Number of messages for test cases in a solution |
As well as the dimensions, you can increase the detail of the data display with further filter groups. You can add filters as expansion, or select filter values.
Filter by time attributes (not in all web templates) |
|
---|---|
Calendar year |
|
Calendar month |
Calendar month of selected calendar year |
Calendar week |
Calendar month of selected calendar year |
Filter by node attributes |
|
---|---|
Nodes |
GUID of a node |
Node type |
Type of a structure node in the project/solution structure (e.g. folder node for business scenario) or test plan structure (e.g. manual test case or eCATT as leaf node) |
Business scenario |
|
Business process |
|
Process step |
Filter by test case attributes |
|
---|---|
Test case status |
|
Tester |
Person who runs the test case |
Tester (assigned) |
Test person assigned by the stat of test case processing (can be different from tester) |
Traffic light status |
Aggregate status of repeated execution of a test case |
Completed test case flag |
|
Customizing restriction |
Flag for a Customizing restriction which was determined during a test case |
Display restriction |
Flag for a user interface display problem which was determined during a test case |
Documentation restriction |
Flag for a missing test case documentation problem, which was determined during a test case |
Functionality restriction |
Flag for a missing functionality problem, which was determined during a test case |
Translation restriction |
Flag for a missing or incorrect translation problem, which was determined during a test case |
User guidance restriction |
Flag for a problem of insufficient user guidance, which was determined during a test case |
Other restriction |
Flag for another restriction, which is not in the list of restrictions |
Filter by test cases |
|
---|---|
Test case |
|
Test case type |
e.g. manual test case, external function |
Priority |
Priority of the function to be tested, in the test case attributes |
Person responsible for test case |
|
Logical component |
Filter by test plan attributes |
|
---|---|
System role |
The use to which a set of systems in your system landscape, in which the functions to be tested run, are put In the test plan attributes |
Person responsible for test plan |
In the test plan attributes |
Planned start date |
Plannned start date of a test package, in the test plan attributes |
Planned end date |
Plannned end date of a test package, in the test plan attributes |
Actual start date |
Time at which the first test case of the test plan begins |
Actual end date |
Time at which the last test cases of the test plan finishes |
BPCA ID |
Test plan with test cases for all modified transactions which the Business Process Change Analyzer has found |
Filter by test package attributes |
|
---|---|
Test package |
|
Priority |
Test package processing priority, in the test package attributes |
Planned start date |
Plannned start date of a test package, in the test package attributes |
Planned end date |
Plannned end date of a test package, in the test package attributes |
Actual start date |
Time at which the first test case of the test package begins |
Actual end date |
Time at which the last test cases of the test package finishes |
Filter by message attributes |
|
---|---|
Message number |
|
Message short text |
|
Message status |
|
Message priority |
|
Message component |
|
Message processor |
|
Code |
Message subject code |
Code group |
Message code group |
Transaction type |
Specifies the processing of a business case to which messages are assigned |
Filter by keywords (business process hierarchy) |
|
---|---|
Node type |
Type of a structure node in the project/solution structure (e.g. folder node for business scenario) or test plan structure (e.g. manual test case or eCATT as leaf node) |
Key word |
Attribute of nodes of the project/solution structure |
Filter by keywords/search terms (test structure/attributes) |
|
---|---|
Node type |
Type of a structure node in the project/solution structure (e.g. folder node for business scenario) or test plan structure (e.g. manual test case or eCATT as leaf node) |
Keyword/search term |
Test plan node attribute |
Filter by customer attributes |
|
---|---|
Node type |
Type of a structure node in the project/solution structure (e.g. folder node for business scenario) or test plan structure (e.g. manual test case or eCATT as leaf node) |
Customer attribute |
Customer attribute name |
Customer attribute instance |
Attribute value |
Filter by SAP attributes |
|
---|---|
Node type |
Type of a structure node in the project/solution structure (e.g. folder node for business scenario) or test plan structure (e.g. manual test case or eCATT as leaf node) |
SAP Attribute |
SAP attribute name |
SAP attribute value |
Attribute value |
For further information about the standard functions of a web template, see Context Menu Functions.
You can aggregate statuses in custom categories, and assign a message priority.
Choose the Configure View pushbutton.
To assign a test case status to a custom test case status category (1 to 6), insert rows.
Choose Execute.
For technical reasons (the master data collector is run only once a day), the data is not categorized by custom categories immediately.
To make the custom categories available to the other users of the system, choose the Store Global View pushbutton.
Note
The custom categories are valid for the system. They cannot be personalized.
The custom categories are lost and must be configured again when you upgrade SAP Solution Manager and activate the Test Workbench BI content again. For more information about forced BI content activation, see Configuration of BW-Based Reporting in Test Management.