Define the sequence of the steps in a test case that resemble the flow of a test scenario.

You need to add or edit some or all the steps manually for a test case in the following situations such as:

• To add certain actions that are not supported by Qualitia Automation Recorder.

• To create a test case to automate testing on desktop applications.

• To add certain General Web Actions and Mobile Actions.

• To define conditional statements at the appropriate places.

• To add custom actions at the appropriate places.

Before you start adding or editing steps manually, ensure that all the objects of the application under test are added in the Object Repository. For more information, refer to Working with Objects.

To add or edit a test case manually:

1. From the Expand Menu, click Develop.

2. On the Test Case Editor screen, from the left pane, open an existing scenario or create a scenario. For more details, refer to Working with Scenarios.

3. You can edit or add a test case of the selected scenario:

   1. To edit a test case

      • Select a test case
        The Test Case Editor screen opens.

        If a test case is underlined with the red color, open the test case to resolve the steps that are also underlined with the red color. For more information, refer to Editing a Step Underlined with the Red Color.

   2. To add a test case

      1. On the right pane, click the New Test Case button ().

      2. Enter a Test Case Name, Description, Manual TC ID, and File Name.

      3. Click OK.
         The Test Case Editor screen opens.

4. (Optional) To add a task from the first step, click Create Task. Enter a name and description for the task, and then click OK.
   To add steps for the added task, refer to step 4.

5. To add an independent step or a task step

   1. Click the Add Test Case Step button () to add a blank step in the Test Case Editor screen.

   2. To add an object, double-click the Object cell to open the Object Repository hierarchy, and then select an object. For more information on objects, refer to Working with Objects.
      Note: You can right-click the object and select Edit Object to edit its properties. For more information, refer to Editing an Object.
      Some Generic Actions do not require an object such as OpenURL, Maximize Browser, and so on.

   3. Double-click the Action cell and click the arrow button to select an Action.

      Note: As per the selected object, only the relevant actions are displayed. For more information, refer to Qualitia Actions.
      As per the selected action, the associated parameters in a single or multiple parameter cells are automatically displayed.

   4. Enter the relevant values for the parameters. For more information, refer to Quailtia Actions.
      Similarly, you can add more steps that you want to add to the test case.

6. To add a task using the steps that you have defined

   1. Select the steps, Press Ctrl and select the other steps that you want to add to the task, right-click and then select Add New Task.

   2. Enter a name and description for the task, and then click OK.
      To add steps to the task, refer to step 4.

7. To import an existing task, select a step from where you want to insert the task, click the Import Task button () from the Test Case Editor screen.
   To edit the steps for the imported task, refer to step 4.

   If you edit the steps of the imported task, ensure that there is no impact on other test cases that are using the same task. 
   The task steps have white background, whereas the independent test case steps

8. To move a task or step to its appropriate place, select the task or step, and then click the Move Up button () or the Move Down button ().

9. After adding or editing all the tasks and steps, click the Save button () to save the test case.

If a task step is added with test data, you need to update the same task in other associated test cases. The associated test cases and test scenarios are automatically underlined with the red color in the left pane. If you execute the associated test cases (underlined with the red color) without updating the test data, the test case execution fails.

For more information, refer to Editing a Step Underlined with the Red Color. 

You can now click the Run button () to dry run the test case to know whether expected results are achieved. For more information, refer to Dry Run a Test Case.

Editing a Highlighted Step

The Test Case Editor highlights the steps that have issues with a red underline and a vertical red line next to the step number. Similarly, the associated problematic tasks, test cases, and test scenarios that need resolution are also highlighted.

You must resolve the highlighted steps to avoid test case execution failures.

The following figure shows how steps, tasks, test cases, and test scenarios are highlighted:

The highlighted steps may have one of the following problems:

• The task step does not have test data. Add the relevant test data for that task step. For instructions on how to add test data, refer to Adding Test Data for a Test Case.
• The step contains an empty object, which means that one or more of the object property values are blank, such as locator type and locator value. 
• The step contains a deleted object, which is applicable for the desktop projects only. The object was deleted from the objects repository due to updates in the synchronized TSR file.

To navigate through the highlighted steps, select any step in the Test Case Editor screen, click the Next Error button () or the Previous Error button ().

About Qualitia Automation Studio Recorder

Qualitia Automation Studio Recorder automates and simplifies the process of creating test cases. It lets you record test cases for web or mobile applications, or a combination of both. The recorder captures the actions that you perform on the application as steps and stores them as objects, along with the associated actions and parameters.

You can access the Qualitia Automation Studio Recorder from the Test Case Editor screen. You can record the steps for an existing test case or for a new test case.

Watch the video tutorial about how to record test case using test recorder here: 

Recording a Test Case for a Web Application

You can record a web application using Google Chrome, Edge, Firefox, or Internet Explorer. 

To record a test case for a web application:

1. Create a new scenario or select an existing scenario that has the test case for which you want to record the steps. For instructions on how to create a scenario, see ​Creating a Scenario.

2. Create a new empty test case or select an existing test case for which you want to record the steps.
   For instructions on how to create a test case, see ​Adding a Test Case Manually.

3. Do one of the following:

   • To create a new test case, click the Web Recording button on the Test Case Editor screen.

   • To add new steps to an existing test case or a new test case that already has some steps, do the following:

     • To add the new steps after the last step, click the Start Web Recording button ()  on the Test Case Edition Button panel.

     • To add the new steps after a specific step, select the step, right-click and select Start Recording on Web.
       Note: If you start recording on a step that does not have an object and an action, or does not have an object and the action is set to NoOps, the recorder overrides the selected step with the recorded steps.

4. Do the following in the order listed:

   1. Select the browser that you want to use for recording.
      Note: If you have selected Internet Explorer to record any web application for the first time, Qualitia Automation Web recorder prompts you to install the IE recorder. For instructions on how to install the IE recorder, refer to Installing the IE Recorder.

   2. Enter the URL of the web application that you want to test, in the Website URL text box.

   3. Click Start Recording.
      The recorder controls toolbar appears on the application.

5. Start performing the actions that you want to record. Each action that you perform is recorded as a step along with the associated objects, actions, and parameters. For more information, refer to Web Actions.

6. (Optional) Click the Expand icon () on the recorder controls toolbar to see the object actions that you can enable for recording. Enabling the actions for recording let you choose the actions associated with the objects when you click on them while recording.

7. Select one of the following actions that you want to enable for recording.
   

   For Internet Explorer, the recorder controls toolbar displays the icons differently and does not provide the options to record the Browser actions.

Action	Description
	Lets you record the Verify actions for objects.
	Lets you record the Wait actions for the objects.
	Lets you record the Mouseover action for the objects.
	Lets you record the Keyboard actions. Note: You can enter values for the objects that have WebEdit class, such as text boxes, even if this option is disabled.
	Lets you record the following Browser actions. Navigate Back ( ): Click to navigate to the previous page of the application under test. Navigate Forward ( ): Click to navigate to the next page of the application under test. Refresh (): Click to refresh the application under test. Open URL ():  Click to switch to another application under test. Enter the URL of the application you want to switch to in the Enter Web URL text box, and then click the Arrow button next to it. After entering the URL, do not hit Enter on your keyboard to switch to another application. Delete Cookies: (): Click to delete cookies of the application under test.
	Lets you customize the sequence of locator types for recording the web objects. Select a locator type and use move up or move down arrow buttons to change the sequence. The default sequence of the locator types for a native application is as follows: Link Name ID XPath CSS Note: The QAS recorder supports only the CSS locator type to record the Shadow DOM objects for web and SFDC applications.

1. Click Pause to pause the recording at any point of time.

2. Click Stop Recording to finish recording the test case. All the steps that you performed are stored as steps under a single task that you selected.

You can now use the Test Case Editor to group the steps under separate tasks. Simply select the test case step you want to convert to Task, right-click and select Add New Task, enter a name and description and then click OK.

Considerations for Recording an SFDC Application

Recording an SFDC application is mostly similar to recording a web application. There are minor differences between these two types of recordings, which are as follows:

• Qualitia recommends that you record test cases for SFDC applications using an SFDC project only as an SFDC project enables you to add the pre-defined SFDC Actions and SFDC specific objects.

• You must record an SFDC application using Firefox or Google Chrome only.

• QAS SFDC Application recorder uses the locator types in the following sequence, which cannot be customized:

  • SFDC:Label

  • XPath

• Currently, SFDC projects do not support Wait Actions for SFDC objects. Hence, the Wait Action button in the Recording Toolbar does not allow you to add the Wait Actions for SFDC Objects.

• You can also record the associated web and mobile applications in an SFDC project.

• The QAS Recorder identifies the web objects and adds them automatically in the following cases:

  • Recording certain SFDC components that are not yet defined in the rules set for identifying SFDC objects.

  • Recording a customized SFDC page that uses web objects.

  • Recording an associated web application.

Recording a Test Case for a Mobile Application

Qualitia Mobile Recorder enables you to record test cases on a mobile application. It supports Android and iOS platforms and works with most of the popular mobile brands. You can record a mobile application in an environment that can be a virtual device (Emulator or Simulator), or a real device.

Before you begin recording a test case, ensure that you have to:

• Install Microsoft ODBC Driver 13

  • For SQL Server: Use this link to download.

  • For SQL Server 2012 Native Client: Use this link to download.

• Install Mobile Recorder components. For more details, refer to Install Mobile Agent Dashboard Components.

• Configure Mobile Agents. For more details, refer to Configure Mobile Agents.

• Configure the appropriate mobile emulators and simulators. For more details, refer to Configure Mobile Emulators or Simulators.

• Configure the Qualitia Mobile Recorder URL in the MOS URL field, in the General Settings dialog box.
  You can verify whether you are able to connect to MOS Server.

To record a test case for a mobile application:

1. Create a new scenario or select an existing scenario that has the test case for which you want to record the steps. For instructions on how to create a scenario, see Creating a Scenario.

2. Create a new empty test case or select an existing test case for which you want to record the steps.
   For instructions on how to create a test case, see Creating a Test Case Manually.

3. Do one of the following:

   • To create a new test case, click the Start Mobile Recording button on the Test Case Editor screen.

   • To add new steps to an existing test case or a new test case that already has some steps, do the following:

     • To add the new steps after the last step, click the Record button on the Test Case Edition Button panel.

     • To add the new steps after a specific step, select the step, right-click and select Start Recording on Mobile.
       Note: If you start recording on a step that does not have an object and an action, or does not have an object and the action is set to NoOps, the recorder overrides the selected step with the recorded steps.

4. Do the following in the order listed:

   1. Click the Mobile Recorder tab.

   2. Select the browser that you want to use for recording.

   3. Click Start Recording.
      The Mobile Recording Platform opens in the selected browser.
      

1. Click CONNECT to connect to the appropriate environment.

2. Do one of the following:

   To launch a native/ hybrid application

   Do one of the following: To select an application that is already installed, from the Select an application drop-down list, select the appropriate application, and then click the Arrow button. To install a new application, under Install New, enter the path of the mobile application package, and then click Install. After installing the application, from the Select an application drop-down list, select the application, and then click the Arrow button.

   To launch a web view application

   Click the Provide Web URL button, enter the mobile application URL, and then click the Arrow button.

   The recorder controls toolbar appears on the screen.

   1. Start performing the actions that you want to record. Each action that you perform is recorded as a step along with the associated objects, actions, and parameters. For more information, refer to Mobile Actions.
      Note: While recording a mobile web application, Qualitia recommends to keep the size of the browser as 100%. If you Zoom In or Zoom Out the browser, the UI may distort, which makes it difficult to identify the objects.

   2. Click the Click the Expand icon () icon on the recorder controls toolbar to see the object actions that you can enable for recording.

      Enabling the actions for recording let you choose the actions associated with the objects when you click on them while testing. Select one of the following actions that you want to enable for recording.

      Recording Panel Button	Description
      	Lets you record verify actions for an object.
      	Lets you record wait actions for an object.
      	Lets you enter texts in text boxes.
      	Lets you remove texts from text boxes.
      	Lets you customize the sequence of locator types for recording the mobile objects. Select a locator type and use move up or move down arrow buttons to change the sequence. The default sequence of the locator types is as follows: UiAutomator ID Accessibility ID Class XPath The default sequence of the locator types for a mobile web application is as follows: Link Name ID XPath CSS

      1. Click Pause to pause the recording at any point of time.

      2. Click Stop to finish recording the test case.

You can now use the Test Case Editor to group the steps under separate tasks. Simply select the test case step you want to convert to Task, right-click and select Add New Task, enter a name and description and then click OK.

Recording a Mixed Test Case for Web and Mobile Application

You can record a single test case to capture steps on both mobile and web applications. For example, to log in to a banking web application, you need an OTP that you receive on your mobile application.

You can start recording on an application type, pause the recording, and then switch to continue recording on another application type.

A combination of mobile web application and mobile native or hybrid application is not supported.

To record a mixed test case for web and mobile application:

1. You can start recording on a web or a mobile application:

   1. To start recording on a web application, refer to ​Recording a Test Case for a Web Application.

   2. To start recording on a mobile application, refer to ​Recording a Test Case for a Mobile Application.

2. To switch to another application type, from the Test Case Editor screen, select a step from where you want to record, right-click and then select Start or Continue Recording from the appropriate application type.
   The subsequent steps are added from that step.

3. Click Save to save the recorded steps.
   W denotes that the steps are recorded on a web application and M denotes that the steps are recorded on a mobile application.

4. Click Stop to finish recording the test case.

You can now use the Test Case Editor to group the steps under separate tasks. Simply select the steps that you want to add to a new group, right-click and select Add New Task, enter a name and description and then click OK. A task too can be formed containing steps related to web and mobile application testing.

A dry run is a trial execution to verify whether a test case is created as per the test requirement.

The dry run test case execution results are not displayed in the Reports and Dashboard portal. A dry run covers all the task iterations and test case iterations as per the set of values defined in the associated Test Data explorer.

Before you dry run a test case, ensure that you have configured the settings in the System Execution Profile as per the requirements.

For more information, refer to the following topics:

• Configuring the System Execution Profile Settings for a Web/Mobile Project

• Configuring the System Execution Profile Settings for a Desktop Project

1. Open a Test Case. To know how to open a test case, refer to Adding a Test Case Manually.

2. Click the Dry Run button ( ) to dry run the test case.

   To dry run a test case on mobile platform, ensure that you have configured the system requirements and settings in the associated execution profile. 
   For more information, refer to Requirements and Configuration Settings for Mobile Environments.

   You can start a dry run of a test case from any step for a desktop project only. You need to select the step from where you want to execute, right-click it, and select Execute from the Step.

3. If you want to stop the test execution at any step, click Stop.

4. After the dry run completes, the test case execution report is displayed.
   For more details on the Test Case Execution report, refer to Test Case Iteration Detailed Report.

   • If some steps have failed in the dry run, you can refer to Failure Summary to know the reasons for their failure.

   • If the Keep Dry Run Reports checkbox is not selected in the System Execution Profile, the associated test case report is automatically stored in the following location:
     <LocalAppData>\QualitiaWDClient\app-8.3.x\WebDriver\ReportResources\1\ITR_xxx
     In this case, when you dry run the same or another test case, this report is overwritten.

   • If the Keep Dry Run Reports checkbox is selected in the System Execution Profile, the associated test case report is automatically stored in the following location:
     AppData\Local\Qualitia\WD\Client\ResultPath\DryRun\<machinename>\<username>\<projectname>\<Buildname>\<Releasenumber>\ITR_xxx

   • You cannot log a defect from the dry run test case execution report even if the Qualitia project is integrated with a defect management system, such as Jira or TFS/Azure DevOps.

A test case contains the following two types of test data:

• Static Data

• Parameterized Data

Static Data

As the name suggests, static data denotes a single static value for a parameter of an action. The static data must be enclosed in double-quotes (""). For example, if a step contains an object as username and Action as Set, then under the Parameter column, enter “John”.

Whenever you change the static data for a step of a task, the change is reflected in all the associated test cases.

Parameterized Data

You can define multiple sets of data to execute a test case in multiple iterations using the Test Data explorer. Also, you can have multiple task iterations within a test case iteration.

To parameterize the test data for a test case:

1. Open the test case in which you want to add test data or edit its existing test data. For instructions on how to open a test case, refer to Adding or Editing a Test Case Manually.
2. In the test case, under the Parameter columns, for the data you want to parameterize, replace the existing values with a unique value without enclosing in double-quotes. 

3. Click the Test Data button () to open the Test Data explorer.

4. Click the Edit Data button.
   The test case and test data are locked for other users.
   

5. To add a test case iteration, under the following columns, enter the following details:

   1. TC Iteration: Enter a number for every test case Iteration. 
      Note: After saving the test data, the values in TC Iteration are automatically numbered from 1, even if you provide any number in TC Iteration.

   2. DataSetTag: Enter a unique value for a data set test case iteration. DataSetTag simplifies finding a test case iteration in the test case execution report, 

   3. Selection: Enter True to enable the execution for the test case iteration or enter False to disable the execution for the test case iteration. You must enable at least one test case iteration to execute the test case, 

   4. Enter the values in their relevant formats for each parameterized data.

      • Enter $NULL$ in the cell where you want to have a blank value.

      • You can move and resize the Test Data explorer.

      • You can import test data for a test case from an excel file and also export it as an excel file.

6. If the test case contains tasks, the first row displays the task names. Each task covers its associated parameterized data in the second row.
   To add a task iteration within a test case iteration, do the following in the order listed:
   1. Insert a blank row after the test case iteration.

   2. Skip the TC Iteration number, Selection, and DataSetTag.

   3. Enter the values in their associated format for the task parameters only.

      • The values added for parameters of a task are not duplicated in the same tasks that are present in other test cases.
      • You do not need to enter the values for the parameters that are not associated with task iterations as they are not considered in the task iteration executions.

7. After adding or editing all the required data, click the Save button on the Test Case Editor screen.
   

   After saving a test data, to edit test data, click the Edit button to unlock the test data again.

   
   

8. Click the Test Data button present in the test case editor screen to close the Test Data explorer.
   You can now Dry run the test case to verify whether the test data meets the test requirements. For more information, refer to Dry Run a Test Case. 

Troubleshooting the Issues in Parameterizing Test Data 

The following table provides information to troubleshoot the issues you may face while parameterizing the test data.

Some test cases may become obsolete during application development life cycle. Qualitia allows you deleting unwanted test cases that are no longer in use. 

To remove Test case:

1. From the Expand Menu, click Develop. 
2. In the left pane, click the scenario under which the test case is added.
3. Select the required test case displayed on the right pane.
4. Click the Remove Test Case button ().
   
   
5. Click Yes.

The selected test case is removed. The test case is no longer visible on the left panel.

As a user, you may want to perform some tests with blank data as parameters. For example, a validation test to check that the user name field cannot be blank will require a blank value to be passed to the WebEdit type of object. This can be achieved with the help of Empty Data Handling feature.

Blank data can be passed to both, Static as well as Data sheet parameters.

Static

Use open and close double quotes with space inside it (" ") to pass a blank value as static data. 

Data Sheet Parameter

Enter $NULL$ in the data sheet for the required parameter to pass a data sheet parameter as blank value. By default, the first time a user opens the data sheet, $NULL$ will be displayed for all parameters.

• You must not execute test cases with the default data sheet values. The data sheet is required to be opened and attached at least once prior to execution.
• An empty cell in the data sheet acts as a break point for tasks and should be used for passing blank values to action parameters.   

There are two types of parameters; Mandatory and Non-mandatory.

For non-mandatory parameters, empty (" "/$NULL$) data is accepted as data. The action on receiving empty data, accordingly uses the default data for the parameter, however, for the string parameter, it will continue using the empty (zero length string).

For Mandatory parameters, empty (" "/$NULL$) data is not accepted as data and you will need to enter valid data. Custom Actions can have parameters set to mandatory/non-mandatory based on the requirement.

In automation projects, the scripts deal with various user IDs and passwords. Qualitia securely stores this critical information in order to be more robust. The automation scripts maintain these passwords in encrypted mode to prevent exposure of original data unnecessarily.

Qualitia provides two approaches to encrypt data:

Using Environment Variables:

1. Go to Setting > Environment Variable.
2. Enter the critical data using ENCRYPT(...) token and press Tab to shift focus out of the cell. 

After encryption, the data reflects as shown below:

Using Development Screen:

1. Go to Development > Test Cases.
2. Create a new test case or open an existing test case.
3. Enter the critical data using ENCRYPT (…) token and move out from the cell.

This token uses static data as well as data sheet for encryption.
After encryption, the data reflects as shown below:

Using Encrypted Data in Test Case(s).

Qualitia provides the following actions to set encrypt data. ENCRYPT token is only used in the actions mentioned below:

• SecureSet
• SecureSetTextinCellEdit
• SecureStoreVariable

These actions decrypt the encrypted data first and then set the original decrypted value in a password field.

These actions decrypt critical data only when it is in encrypted state. If we try to pass a plain (non-encrypted) password to these actions, then rather than decrypting the data, it gives an error as "the value is not in encrypted format."

Limitations

• The actions are applicable to non-secured edit boxes as well. This should be allowed only for the password field; however, it can be done on normal edit boxes as well.
• There is no provision to store secured value at run-time in encrypted state.
• Data once encrypted cannot be decrypted, not even within the application. This is to ensure utmost security.
• Once you have entered the data and it is encrypted, there is no way to validate if it is correct. This can be an issue if incorrect data is entered and it gets encrypted.
• Data comparisons for secured data will only be done on the encrypted data.