Test case template reference

You can use a predefined test case template or create a template. This reference shows which sections that each predefined test case template includes.
You can view a description of each predefined artifact template on the Manage Artifact Templates page.
In the following table, an X indicates a section that is in a template.
Test case section Section description Basic test case template Default test case template Collaborative ALM test case template Agile test case template Software test Description Test Case Template Classic Test Case Template SAFe test case template
Summary A detailed description of the test case. In this section, you can also set up categories to organize your test cases into logical groups. This section uses a full-text editor. X X X X X X X
Test Case Scope The software and system for the test case. In this section, include an overview of the purpose, security, or privacy implications of the software or system. This section uses a full-text editor.         X    
Test Case Design The overall design of the test case, including any background setup information or topologies. You can generate manual test scripts automatically from this content. This section uses a full-text editor.   X   X X X X
Normative and Informative Documents Attached or linked normative and informative documents, such as applicable standards or guidelines specific to an industry or organization.         X    
Formal Review A formal review process that can help your business processes comply with applicable industry standards and regulations.   X     X X  
Development Items Work items, such as defects and plan items that you submit in Engineering Workflow Management.   X X X X X X
Requirements The requirements for a test cycle. X X     X X  
Requirements Links The requirements that link to external applications.   X X X X   X
Risk Assessment The risks that are associated with the test case.   X     X X  
Test Preparation The test-preparation details for the test, such as the preparations, procedures, or personnel actions that are required to run the test. In this section, include the procedures necessary to prepare or configure the hardware or software that is used in the test. This section uses a full-text editor.         X    
Test Description The description of the test case. The description might include a project-unique identifier of the test case, prerequisites for running the test, a description of the test data, an explanation of the criteria to evaluate the results with, and any assumptions or constraints that are associated with the test case. This section uses a full-text editor.         X    
Pre-Condition The information that must be true before you run the test case. This section uses a full-text editor.   X     X X X
Post-Condition The information that must be true after you run the test case. This section uses a full-text editor.   X     X X X
Expected Results The conditions that must be met before a test case is considered to be successful. This section uses a full-text editor.   X     X X  
Test Scripts The test scripts that are associated with a test case. X X X X X X X
Test Case Execution Records The execution records for a test case.   X X X X X X
Attachments The files and documents that are attached to the test case, such as screen captures and other supporting material. X X     X X  
Execution Variables The execution variables for manual test scripts. You can set the execution variable values and then pass those values to the manual test scripts during run time. When you create a manual test script, add variables with the same names to the Execution Variables view in the Manual Test editor.   X       X X

video icon Video

Jazz.net channel
Software Education channel

learn icon Courses

IoT Academy
Skills Gateway

ask icon Community

Jazz.net
Jazz.net forums
Jazz.net library

support icon Support

IBM Support Community
Deployment wiki