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

Tosca Cloud offers different approaches to creating workflow tests for web applications:

  • Create tests with Tosca XScan. Tosca XScan is our all-purpose solution for any degree of complexity in your application or tests. It's a powerful tool to create a low-maintenance, end-to-end test suite. With Tosca XScan, you first scan your application and then create your test case.

  • Create tests with Cloud Scanner. Cloud Scanner is our zero-footprint solution for simple, one-off web tests. It's an easy, intuitive tool to get familiar with Tosca Cloud's most important tasks and concepts. With Cloud Scanner, you scan and create your test case at the same time.

For detailed information on important differences between the two approaches, check out Cloud Scanner vs. Tosca XScan.

Please choose your use case:

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:

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.