ALM: User Guide

Test scenarios contain the conditions to be checked. For different types of testing, test scenarios can be written in different ways. For example, for functional testing it is convenient to use a form with a list of steps, the required actions, and the expected result. Using test scenario templates, you can use the format required specifically for that type of testing. Add your own templates, or extend the ones offered by default.

For each test scenario you can set Importance, Effort, or other user-defined attributes. Tags make it easy to implement a custom classification and use it to select scenarios. Links (traces) let you record cause-and-effect relationships in order to answer the question of where this scenario came from and why it appeared. Attach files with test data to scenarios; such files are visible in test reports when tests are filled in.

Test scenarios can be created while editing test plans (test documents), or they can exist independently of them.

Use test documentation templates, which are created in the project settings, in the Text Templates section. Our demo processes include several examples, but you do not have to use them. You can develop your own templates.

For a template to be inserted automatically into the scenario text when it is created, bind that template to the test documentation type in the project settings.

In test documentation templates you can:

• set your own layout for the test documentation;
• use insertion of attributes;
• reuse texts from other typical scenarios, for example in order to describe typical steps.

Our typical processes are configured so that, at the corresponding stages of the lifecycle of requirements or enhancements, the system suggests creating test scenarios. In this way, development of test documentation is built into the process of implementing requirements. The system automatically creates all the required links, which can of course be edited later.

Import test scenarios from Excel. Two import modes are supported:

• Import rows from Excel. In this mode, the scenario content is placed in a single Excel cell. This option is suitable for importing checklists and other unstructured forms of test scenarios.
• Import scenarios. In this mode, the steps, actions, and expected result are filled in separately on each row of the Excel document.

When integration with a language model (LLM) is configured, you can quickly generate test documentation text from requirements. Because test documentation varies (step-by-step scenarios, acceptance, Gherkin, and so on), the generation method also differs for different types of test documentation.

In the settings of the test documentation types, specify which documentation format best matches the given type of test documentation:

When a test scenario is created from a requirement, or during bulk generation of test documentation, the system uses the corresponding mechanism: