Web

A web test drives the site in a browser. General creation steps are in Creating Tests. The sections below are specific to web applications.

​

Suggested tests

For web applications, QA.tech continuously crawls your application to discover testable features and interactions. These appear as AI-generated suggestions you can select and add to your project. Click “Analyze my site” to trigger a new crawl if you want fresh suggestions.

​

Testing Email Flows

When writing tests that involve emails (like account resets or notifications), follow these best practices to ensure the agent can find the correct email:

• Specify the Recipient: Always mention the target email address in your test goal or step (e.g., “Wait for the welcome email sent to user@example.com”).
• Use Descriptive Queries: Describe the email content clearly (e.g., “Find the email with subject ‘Reset your account’”).
• Mind the Time Window: Remember that tests can only see emails received after the test started.
  • If Test A triggers an email and finishes, Test B cannot see that email if it starts afterwards.
  • Solution: Combine the trigger and verification into one test, or use dependencies where the second test triggers the email resend.

For more details on how the inbox works, see Email Inbox.

​

Multiple browser sessions

If your test requires multiple users logged in simultaneously (e.g., collaboration, sharing), create separate login tests for each user. Each login test becomes the root of an independent chain with its own isolated browser session, ensuring users don’t interfere with each other. Learn more about Multi-User Testing Scenarios.