To create a Scenario, click on the Create Entity (+) icon on the top navigation and select Scenario.
Basic Details
Provide a meaningful name for the Scenario. Remember, the name should be unique in the project. Feel free to provide a functional and readable name to clearly suggest the purpose of the test. Remember you can use spaces and other special characters in the Scenario name (except for the characters greater than (>), less than(<), apostrophe (`), backslash (\), single quote ('), and double quote(")).
Description is optional, but we suggest you provide a brief explanation of what this Scenario tests.
Provide Tags to this Scenario. Tags are useful when you want to group or arrange the entities later as per their characteristics.
Requirements Mapping
Requirements mapping allows you to establish traceability of this Scenario with relevant Requirements or stories. ACCELQ supports Jira and TFS for this traceability.
Simply type the Requirement/Story ID and add it to this Scenario.
This feature requires setting up connectivity to Jira/TFS in your project configuration. Learn more
Custom Information
Custom fields allow capturing relevant information about an entity for governance and analysis purposes. You may also create Test Suites based on custom fields, for a specific purpose or functionality.
Custom fields are set up in project configuration. Based on the custom fields set up on your project, you will be required to provide values for all mandatory fields while creating the Scenario.
Learn more about the significance of custom fields.
Comments
1 comment
How can users see ALL the tags that have been created? For example: one person might tag 'Sprint1", another user 'Sprint #1', or 'Sprint 1'. Tags can get messy if users cannot see what tags have been created.
Please sign in to leave a comment.