Skip to main content

Test Case Steps

Our generated tests may have steps that are not needed or require a simple update to fit what you're looking for. Instead of deleting the entire Test Case, you have the ability to add, delete, and edit the Test Case Steps!

List of Test Case Steps​

Every Test Case will have a Steps tab that shows its list of steps and their order. To view this:

  1. Click on any Test Case within a Test Folder
  2. Click on the Steps tab

Edit or Add a Test Case Step​

You can edit an existing step, or add a new step anywhere in the Test Case. To get started, open the Steps tab on any Test Case:

  1. Hover the step and click the add or edit button that appears to the right
  2. There are a few things you can fill in the modal:
    • Step description: plain English description of what the step does
    • Step type:
      • Action step: the step can generate and self-repair its code automatically
      • Assertion step: see the next page, Assertions
    • Code (optional): the nitty-gritty of how the step does its thing
info

If a Test Case Step has code specified, that's what Qualiti uses to execute the step. If there is no code, Qualiti AI uses the step's description to figure out what to do. If a Test Case Step isn't doing what you want, you can try deleting its code and running the test again, causing Qualiti AI to re-analyze the step.

Test Step Code​

For most scenarios you'll never need to manually write code, but Qualiti still gives you full control to see and edit the code, just in case you have a special use-case that requires it.

Environment​

Qualiti runs your test code using Python 3.11, and interacts with your web application using Playwright 1.50 (sync mode).

In addition to most of Python's builtins, the following identifiers are accessible to test steps' code:

  • variables: See docs on Variables
  • Playwright tools:
    • browser: Browser (e.g. Chromium)
    • browser_context: BrowserContext - similar to a browser window
    • page: Page - similar to a browser tab
    • expect: Function used to create a Playwright assertion; see Playwright docs
  • Python standard library:
info

Identifiers from the Python standard library are entire modules, rather than individual classes/functions such as datetime.datetime or random.random

info

Test code is not able to import additional modules. If there's another Python tool you'd like to use in Qualiti, let us know!

Use Trace Viewer to Locate Elements​

When writing code by hand, you can use the Trace Viewer to help you craft playwright code to interact with the right page element, saving you from manually inspecting the DOM or understanding complex CSS and XPath selectors. This makes it much simpler to include custom but accurate element locators in your test steps.

element = page.locator('[data-testid="button"]')
element.click()
info

See Playwright's Docs to learn the different ways to locate elements