Test web applications

Ready to create web application tests? Then this topic is for you. It explains the most important steps to your first web application test case.

Tosca Cloud supports the following web tests:

Supported versions

For information on supported versions, check out the system requirements.

Create workflow tests

Creating a workflow test is easy:

  1. Open your application under test.

  2. Scan your application to create modules. A module is the technical representation of a specific part of your application. It contains all necessary technical information that Tosca Cloud needs to find and steer elements of your application.

  3. Create a new, empty test case.

  4. Design your test case to build an automated test sequence. You can add the following design elements to your test case:

    • All elements we list in the design topic, such as the modules you created by scanning or standard modules. Standard modules are pre-built modules for common tasks that Tosca Cloud provides out of the box.

    • Standard modules specifically for steering web applications. You can find these modules under Build > Modules.

Work with web application controls

A control is a screen element in your application under test. For example, a button, text box, menu entry, or table cell. And when you use a module in your test case, you need to tell Tosca Cloud what to do with these controls.

For information on supported controls for web, check out Web application controls.

Create web accessibility tests

Accessibility tests verify whether your application is easy to use for all users. Automating accessibility tests as part of your development process helps you find and fix issues easily. This speeds up your release cycles and reduces costs for tricky after-the-fact fixes.

Tosca Cloud's web accessibility testing is based on the WCAG 2.2 Level A and AA rulesets. To learn more about Tosca Cloud accessibility testing basics, check out Understand basics and limitations.

You can create the following types of accessibility tests:

  • Run an accessibility check on a specific webpage. For example, to verify accessibility of a high-traffic page on your company's website.

  • Add accessibility tests to your regression tests, either before or after inputs. For example, to analyze the new UI state after user inputs.

Please choose your use case:

To create such a test case, follow these steps:

  1. Create a new, empty test case.

  2. Define which browser Tosca Cloud should use at runtime. To do so, add the parameter called Browser.

  3. Add the standard module Check Webpage Accessibility to your test case and fill out the resulting test step.

    Standard modules are pre-built modules for common tasks that Tosca Cloud provides out of the box. You can find them in the left pane of the test case building area, under Modules.

  4. Add a test case parameter with the name ReportSuccessfulExecutionOf. For the value, choose any option except TestCases.

  5. Configure your accessibility test. For example, make large results easier to read by not listing passes and only listing fails. To do so, add the parameter AccessibilityFastMode.

To create such a test case, follow these steps:

  1. Create a new, empty test case.

  2. Define which browser Tosca Cloud should use at runtime. To do so, add the parameter called Browser.

  3. Define what kind of test you want to run. To do so, add the parameter RunAccessibilityAnalysis and specify whether you want to run analyses before or after inputs.

  4. Add a test case parameter with the name ReportSuccessfulExecutionOf and the value TestStepValues - All.

  5. Configure your accessibility test. For example, make large results easier to read by not listing passes and only listing fails. To do so, add the parameter AccessibilityFastMode.

If you want to exclude test cases, add a test case parameter with the name RunAccessibilityAnalysis and the value Disabled.

Stay tuned for accessibility results and reporting, which are coming soon.

What's next

You've just created your first web test case. Well done!

Next up: do a test case trial run. Trial runs help you find and fix issues, so you can make your tests as stable and reliable as possible.

Once you're happy with your test case, pack it into a playlist, so you can run your tests in earnest.