Scripted Manual Tests

Share the article 

Test Steps

A test usually consists of several steps. The steps describe in detail the validation checks that need to be performed on your application or system.

To add steps to your tests, go to the Steps tab and add the steps one by one. You can either create a step or call steps from a different test using the test ID. Each test step contains the following fields: Name, Description and Expected Results. You can attach a file or link and add a comment to each step or to the entire test. During the run, you will be able to add files and links to the Step Run.

Generating Steps Using SmartFox

SmartFox is PractiTest’s built-in AI assistant designed to help you quickly generate and refine manual test steps based on your test’s name and description, saving time and reducing manual effort.

To learn how to use SmartFox for step creation, see the SmartFox Help Page.

Note: SmartFox must be enabled by your account owner and requires acceptance of the AI usage terms.

Step Attachments, Test Attachments, and Step Run Attachments

In the test’s general attachment section, you can add attachments that are relevant to the entire test rather than a specific step (e.g., system configuration document for the test).

Test step attachments are relevant to a specific step, such as a screenshot of how things should appear. While running, each step of a test run (e.g., step-run) will show the test library’s step fields and attachments. During the run, you can add attachments to the step run, for example, to show a log of the run or a screenshot of how things look while running the test.

step attachments in exiting tests

After saving a test, you can always go back and add, delete or reorder steps, or call steps from a different test. PractiTest even allows you to modify your steps as you run your tests.

Note: Each attachment has a maximum size limit of 50MB.

Step Parameters

Step parameters are a smart way to increase test reusability. Test step parameters allow you to reuse tests and run them in various test instances while changing the parameters/data being run. For example, when testing the same functionality but on different systems such as various OS’ or mobile devices, you can reuse a test rather than creating a new one.

When used in conjunction with the Call a Test feature, you can achieve even more flexibility and reusability. Calling tests with step parameters already defined in them increases QA coverage and enhances efficiency.

Adding Step Parameters to a Test

Go to any test in the Test Library. In the Steps tab, choose to add a new step or update an existing step.

  1. Add step name.
  2. In the Step Name/Description/Expected results field, add the parameter placeholder using double curly brackets.
  3. When beginning to add a parameter and type opening double curly brackets, a parameters dropdown list will appear. Select an existing parameter from the list or type a new parameter inside the curly brackets to create a new parameter.
  4. Add as many steps with parameters as needed, by repeating the steps above.
  5. Save and close. 

Step Parameter Settings

After adding parameters to the tests in the test library, you can edit the parameters and add predefined values for each one.

To do so, click on ‘Settings’ -> ‘Step Parameters’. Then click on the small pencil icon in the parameters line to edit an individual parameter.

step-parameters-settings-editing.png
To define values for the parameter, change the parameter’s format from ‘text’ to ‘list’ and add the values from the ‘Add possible values’ field. You can also define a list of URLs if you want the parameter to include clickable links during test execution.

Note: you can define a default value for the parameter and rename it.

Once you have finished editing the parameter, click ‘Save’.

edit-step-paramters-format

Run a Test With Step Parameters

Please see the instructions here.

Similar Tests (Anti-Duplication Mechanism)

PractiTest includes an AI-powered capability that helps you avoid creating duplicate tests. As you create a new test and start filling in details like the Name, Description, or Steps, the Similar Tests tab will display a list of existing tests with similar content, along with their names and IDs. This list updates in real time based on the information you enter.

Call a Test

When creating new tests or editing existing tests, it is possible to call test steps from other existing tests in the test library. This feature can save time by reusing already well-defined test steps.

Calling Test Steps Into a Test

To call a test, go to the Steps tab, and click on the ‘Call a Test’ button. If you wish to call a test between existing steps, click on ‘Add Steps’ at the relevant location and then choose ‘Call a Test’.

A new pop up window will appear showing all tests. Choose the relevant test/s you want to reuse its steps by ticking the box next to it, and click on ‘Add selected Tests’.

The called test will appear as a link to the original test within your steps tab display. Don’t forget to save your test.

A link to this called test will be added to the traceability tab.

Nested Tests

You can nest as many called “child” tests under any “parent” test with multiple levels, as seen in the diagram below:

call-a-test-presentation

Running Called Tests

Please see the instructions here.

Copy Step

When creating new tests or editing existing tests, it is possible to copy test steps from the same test or other existing tests in the test library. This feature can save time by reusing already well-defined test steps.

Copying Steps From One Test to Another

Go to the Steps tab and instead of manually adding a new step, select “Copy step here“.

A new pop up window will appear showing all tests.  To choose all steps within a certain test simply tick the box next to it. If you wish to copy only a specific step (or several steps), click the arrow next to the relevant test checkbox, and tick the steps you wish to copy. 

Once done, click ‘Add selected Steps’.

The copied step will appear within your steps tab with all information including attachments.

Shift your testing Forward