Creating Test Cases

Create web test cases in minutes using ContextQA's AI agent — no code required. Every step, screenshot, video, and trace captured automatically.

Real execution evidence below. Every screenshot on this page was captured live by the ContextQA AI agent. Watch the full session recording →

Overview

ContextQA lets you create web test cases through three methods: AI-assisted generation, browser recording, and manual step creation. The AI agent handles navigation, interaction, and evidence capture automatically — you describe what to test, it does the rest.

---

Step-by-Step Workflow

1

Navigate to the Login Page

Open https://accounts.contextqa.com/onboard in your browser. The ContextQA authentication page loads with email and password fields.

Screenshot captured by ContextQA AI agent — execution result #47297

2

Sign In to Your Workspace

Enter your credentials and click Login. On successful authentication, you are redirected to your project dashboard.

• Email: your registered email address

• Password: your account password

New to ContextQA? Start your free trial — no credit card required.

3

Click the + Icon

From the dashboard, locate the + icon in the top navigation bar or sidebar. Click it to reveal the test creation options menu.

Screenshot captured by ContextQA AI agent — execution result #47297

4

Choose Your Creation Method

Three options appear in the dropdown:

Method	Best For	Time
AI Assistance	Complex scenarios, natural language	30 sec
Start Recording	Click-through workflows	2–5 min
Import	Existing test scripts	1 min

Click Start Recording to continue with the manual creation flow.

5

Select "Manually Create Test Case"

In the recording options dialog, click Manually Create Test Case. This opens the test case creation form where you name your test.

6

Enter Test Case Details

Fill in the test case creation form:

1. Name — Enter a descriptive name (e.g., ContextQA Test)

2. Tags (optional) — Add labels like smoke, regression, login

3. URL (optional) — Pre-set the starting URL for this test

Click Create when ready.

7

Test Case Created ✓

Your new test case appears in the test cases list. You can now:

• Add steps — Write steps in plain English, ContextQA converts them to actions

• Record steps — Use the browser recorder to capture interactions

• Execute — Run the test and get video, screenshots, and trace automatically

---

Execution Evidence

The workflow above was executed by the ContextQA AI agent. All artifacts below were captured automatically:

Evidence	Link	Description
🎬 Session Video	Watch in Portal →	Full recording of the AI agent completing the workflow
📸 Step Screenshots	View in Portal →	Per-step screenshots from execution #47297

🎬 Session recording not loading? Open in ContextQA →

---

Creation Methods in Detail

AI Assistance

AI-Assisted Test Generation

Describe your test scenario in plain English. ContextQA's AI generates all steps automatically.

Example prompt:

Navigate to the checkout page. Add the first product to cart.
Enter shipping address: 123 Main St, Chicago, IL 60601.
Complete payment with test card 4242 4242 4242 4242.
Verify the order confirmation page shows the order number.

The AI agent:

1. Parses your description into discrete steps

2. Generates locators for each element

3. Handles dynamic content and waits automatically

4. Captures screenshot at each step

5. Records full session video + trace

Best for: Complex multi-page flows, form submissions, checkout workflows

Browser Recording

Manual Step Creation

---

Frequently Asked Questions

How long does it take to create a test case?

With AI Assistance, describing a 10-step workflow takes under 60 seconds. The AI generates and validates all steps automatically. Browser recording typically takes 2–5 minutes for a complete user journey. Manual step creation varies by complexity but most teams create 20–30 step test cases in under 10 minutes.

Can I import existing Selenium or Cypress tests?

Yes. Use the Import option when creating a test case. ContextQA supports:

• Selenium WebDriver scripts (Java, Python, JavaScript)

• Cypress test files

• Playwright test scripts

• Gherkin / Cucumber feature files

ContextQA converts imported scripts into its visual step format, making them editable without code.

What browsers and devices are supported?

ContextQA supports all major browsers for test execution:

• Chrome (desktop + headless)

• Firefox

• Safari (macOS)

• Edge

• Mobile Chrome / Safari (via device emulation)

For real-device mobile testing, see the Mobile Testing section.

Are screenshots and videos stored automatically?

Yes. Every test execution automatically captures:

• Per-step screenshots — A screenshot is taken after each step completes

• Full session video — Complete recording from start to finish (WebM format)

• Playwright trace — Detailed trace file with network logs, DOM snapshots, and timing (downloadable ZIP)

All evidence is stored on S3 and linked directly in the execution results. No configuration required.

Can I run the same test case across multiple environments?

Yes. ContextQA supports environment-based test execution. You can define multiple environments (Development, Staging, Production) and run any test case against any environment by selecting it at execution time. Environment-specific variables (base URLs, credentials, API keys) are managed separately so your test cases remain portable.

How does self-healing work if my application changes?

ContextQA's AI Configuration (self-healing) continuously monitors element locators. When an element changes — for example, a button moves or an ID changes — the AI automatically finds the updated element using visual context, text content, and semantic analysis. Failed locators are flagged for review and healed with one click. See Self-Healing Tests for configuration details.

---

Best Practices

Name tests descriptively — Use the format [Page] - [Action] - [Expected Result] (e.g., Login Page - Valid Credentials - Dashboard Loads). This makes test results immediately understandable.

Start with happy-path tests — Create and validate your positive test cases first, then add negative scenarios (invalid inputs, error states) once the base flow is verified.

Avoid hard-coded waits — Don't use Wait 5 seconds steps. Instead, use Wait for element or Wait for network idle actions. ContextQA's AI handles timing automatically.

---

Related Documentation

• Test Steps Editor — Detailed guide to all available step actions

• Managing Test Suites — Organize test cases into suites for batch execution

• Self-Healing Tests — AI-powered test maintenance

• Test Data Management — Variables, CSV imports, and data-driven testing

• Execution & Reporting — Run tests, view results, set up CI/CD

---

Ready to create your first test?

🚀 Open ContextQA Platform · 📖 View Test Steps Reference · Book a Demo