A task is a collection of steps that you can reuse in multiple test cases. You can add tasks that are part of testing multiple scenarios. For example, you can create a task that automates to login into the application.
...
From the Expand Menu, click Develop.
Click the Tasks tab.
The Task Editor screen opens as shown in the following:
Image Removed
Image AddedIn the left pane, click the Add Task button (
).
Enter the following details:
Task name
Description of the Task,
File Name
| Info |
|---|
The task name must not contain the special characters:/, \, :, *, ", <, >, |, %, and #.
The File Name field is not editable after the task is saved. The task file is saved with .xml extension in the QualitiaProjectPath\<projectname>\Tasks folder. |
Click Save.
Click the Add Step button (
).
A new row is added to the task grid.
Do the following in the order listed:
If it is an object-based action, select the required object by clicking Object field.
Select the relevant Actions for the selected objects clicking Actions field.
Depending upon the Action selected, the Parameter fields get populated with the default parameter name.
Note: The Parameter fields are blank for the Actions that do not require any parameters.
Similarly, you can add more steps in the below rows.
Qualitia recommends clicking the Save button (
Image Removed
Image Added) regularly to save the updates that you have made in the task. After a task is created, you can import it when creating or editing test cases from the Test Case Editor screen.
...
Viewing Test Cases Associated with a Task
Qualitia allows you to view test cases associated with a task. You can view the associated test case names, their manual test case IDs, and descriptions.
To view the test case associated with a task:
From the Expand Menu, click Develop.
Click the Tasks tab.
In the left pane, right-click the task that you want to delete, and then select View Test Cases.
...
| Info |
|---|
Points To Know You cannot import tasks from a web/mobile project to a desktop project and vice-versa. After a task is imported: If the task name matches with an existing task in the current project, the imported task name is appended with _N, where N is a number that is incremented by 1 if there are multiple tasks with the same name.
For example, if a task called “login” is present in both, the imported and the current project, then after importing the task, it is named as “login_1” in the current project. If a task with a name “login_1” already exists in the current project, then it is named as “login_2”, and so on. If an object name matches with an existing object in the current project, the imported object name in the current project is appended with _N, where N is a number that is incremented by 1 if there are multiple tasks with the same name.. For example, if a button called "Submit"alr eady exists in the current project, and you import a task that contains a Submit button, then this object is named as Submit_1 in the current project.
If an object with a name “Submit_1” already exists in the current project, then it is named as “Submit_2”, and so on. Similarly, if an environment variable name in the import project matches with an existing environment variable name in the current project, but their value differs. Then, after the task is imported, the environment variable name is appended with _1. The imported custom actions along with their parameters are displayed in the Test Case Editor screen. However, you need to manually copy all the external files and codes of the imported custom actions to execute them. If the imported task contains rest header variable, the rest header should be copied manually from the source project to the target project.
In case of desktop projects, if the TSR file is different for import and current projects, then after importing the tasks the current project updates its TSR file with the additional objects and replaces the existing values for the same objects associated with the imported tasks from the TSR file of import project. Also, when you synchronize the TSR file for any other project that shares the same TSR file with the current project, the TSR file for other project is updated too. You can use the Search feature to find a task by its name, its associated test case names, and associated test scenario names. QAS stores the import details in a text file called Import.Log at the following location:
%localAppData%\Qualitia\WD\Logs
|
...
