Edit Scenario Secondary Screen View and Toolbars

TABLE OF CONTENTS

1. Overview

2.1 Scenario Form

2.2 Scenario Sequence

2. Related Articles

1. Overview

The Edit Scenario feature you manage your test scenarios. To access it, navigate to the Main Canvas > More > Edit Scenario.
You can access Edit Scenario secondary screen by clicking the Edit icon in the Edit Scenario Form.
 Secondary screen includes: 

1. Scenario Form 
2. Scenario Sequence

2.1 Scenario Form

The Scenario Form allows you to edit a specific scenario details. It includes various fields for the identification of a scenario, which are detailed in the following tabular format:
To access these fields in the Scenario Form, click this  icon located in the top-right corner of the Header bar.

Scenario Form  Fields and Descriptions

Field	Description
Scenario Name	Displays the Scenario name or Test Case name used while recording the scenarios using Follow Me feature. You can edit the name in this text box.
Custom Tag	Displays the tags that will group and execute the tests associated with the given tags. For example, if you provide a tag as @test001, then all the test cases tagged with @test001 will be executed. Similarly, you can provide tags like @Smoke001 & @Sanity001.
Separate Feature	Segregates the BDD feature files module-wise by generating them in separate feature file. For more information on generating a separate feature file, refer to Generate separate feature file in a separate folder. For example, Features - User Login, User dashboard and Payment processing.  The following screenshot represents a module-wise and  feature file structure:
Folder Structure	Segregates the BDD feature files Folder-wise by generating them in the separate folder. For more information, see Generating Separate Feature Files in a Separate Folder.
Scenario Outline	Provides brief test case summary or description as an outline given during recording of the scenario using Follow Me feature.

2.2 Scenario Sequence

The Scenario Sequence section allows you to manage the sequence of test case steps within a workflow. It enables you to:

• Edit: Modify existing test case steps.
• Add: Add new test case steps.
• Drag and Drop: Rearrange the steps as needed.

Scenario Sequence fields and descriptions

Field	Description
Feature Name	Displays the feature name that is being tested.
Control Name	Displays the UI element name provided during Node Configuration. You can modify the UI element in this textbox.
Alias Step	If you wish to add a user-specific step or modify an existing step manually, then you can use this text box. For example, a login scenario where you want to add an alias step for verifying user profile details in the Dashboard, Feature file will be generated with highlighted alias step, as shown:
Default/Custom Action	Default actions are the ones readily available as part of automation framework in algoQA.  algoQA platform allows you to create custom actions to incorporate your application specific  testing requirements. You can select the default/custom action from the drop down list.  For more information, For more information on Default Actions, refer to Default Actions  and For more information on Custom Actions, refer to Custom Actions.
Custom Value	You can provide user-specific value, keywords and parameters in the custom value text box. It will be reflected in the Feature File. For more information, see  Keywords Used in algoQA and Their Descriptions. When entering a value in the custom value field, adhere to the following:  Custom value cannot be just blank spaces. If you wish to include spaces, you can use the keyword _empty_. For more information, see Keywords used in algoQA. If you enter the only spaces, then following error message is displayed: You can include spaces at the beginning, end, or between words.
Alias Name	If you choose to add a new name or modify an existing name for an UI element or a Control, then you can use this text box. You can add Alias name in the Follow Me feature too.
Test Step Settings	You can select specific condition or a parameter from the dropdown list. Allows you to customize your test steps by selecting or excluding specific conditions, ensuring that only relevant steps are included. For example, if you wish to avoid generating the default post-condition step, you can select the 'No Postcondition' option from the dropdown. This will prevent the default last step from appearing in the Feature File.
GWT  Input	To add a prefix to a  GWT step, then you can update the textbox. By default, the initial context in a Given step is shown as "I".   For example, 'Given I have access to application' sets up the initial state for the test.
Message	You can provide a comment or text for a particular GWT step. When entering a value in the message field, adhere to the following:  Message field cannot be just blank spaces. If you wish to include spaces, you can use the keyword _empty_. For more information, see Keywords used in algoQA. If you enter the only spaces, then following error message is displayed: You can include spaces at the beginning, end, or between words.
Dataset	As a user, when you provide an Alias step, Dataset textbox will be enabled  for you to add the parameters manually.  For example, if you add 'And I verified the results in the Dashboard' as an alias step and as parameters provide 'profile details' in the Dataset text box then, feature file is displayed, as follows: Note that if you wish to update dataset in separate columns, then you can use this "|" symbol

2. Related Articles 

Managing Test Cases Using Edit Scenario Workflow