# For Testers

{% hint style="info" %}
**Who is this for?** Manual testers, QA analysts, and automation beginners who want to write effective automated tests without learning to code.
{% endhint %}

You already know how to test software. The problem is translating that knowledge into automation — learning XPath, fighting flaky selectors, and babysitting scripts that break every sprint. ContextQA eliminates that translation layer. You write what to test in plain English and the AI handles the rest.

***

## What You Can Do Without Writing Code

| Task                        | How                                                                                         |
| --------------------------- | ------------------------------------------------------------------------------------------- |
| Create a login test         | Type: *"Go to /login, enter <user@example.com>, click Login, verify dashboard appears"*     |
| Test a checkout flow        | Describe each step as you'd explain it to a colleague                                       |
| Verify an error message     | *"Submit the form with an invalid email, verify the error message says 'Invalid email'"*    |
| Parameterize with test data | Upload a CSV with username/password pairs — ContextQA runs each row as a separate execution |
| Generate tests from Jira    | Paste a Jira ticket URL and get complete test cases generated automatically                 |
| Record a test               | Click through the UI once — ContextQA records your actions as reusable steps                |

***

## Your Day-to-Day Workflow

### 1. Create Test Cases

Go to **Test Cases → New Test Case**. Enter a starting URL and describe each test step in natural language:

```
1. Navigate to https://your-staging-app.com/login
2. Enter "testuser@example.com" in the Email field
3. Enter "SecurePass123" in the Password field
4. Click the "Sign In" button
5. Verify the text "Welcome back" appears on the page
```

No selectors. No code. ContextQA's AI identifies the correct elements.

→ [Creating Test Cases in detail](https://learning.contextqa.com/web-testing/creating-test-cases)

### 2. Run Your Tests

Click **Run** on any test case, suite, or test plan. Watch execution happen in real time — a browser opens, your steps execute, screenshots appear for each step.

→ [Running Tests](https://learning.contextqa.com/execution/running-tests)

### 3. Review Evidence

Every execution captures:

* **Screenshot per step** — see exactly what the browser showed
* **Video recording** — full playback of the test run
* **Network log (HAR)** — every API call made during the test
* **Console log** — browser errors and warnings
* **AI root cause analysis** — when a test fails, AI explains why in plain English

→ [Video & Screenshots](https://learning.contextqa.com/execution/video-and-screenshots)

### 4. Let AI Fix Broken Tests

When a developer changes a button label or moves a form field, your tests automatically heal. The AI detects the change, finds the correct element, and repairs the step. You get notified if the confidence is below 90% and a manual review is needed.

→ [AI Self-Healing](https://learning.contextqa.com/web-testing/self-healing)

***

## Common Tester Scenarios

{% tabs %}
{% tab title="Login Testing" %}
**Testing login flows:**

1. Create a test case with your login page URL
2. Write steps: *Navigate → Enter credentials → Click Submit → Verify redirect*
3. Add a Test Data Profile with valid/invalid credential rows
4. Run — ContextQA tests every combination

For invalid credential testing, add a step: *"Verify the error message 'Invalid password' is displayed"*
{% endtab %}

{% tab title="Form Validation" %}
**Testing form validation:**

1. Describe each invalid input scenario as a separate step group
2. Use `Verify` steps to assert error messages: *"Verify the text 'This field is required' appears below the Email input"*
3. Group happy-path and error-path scenarios into separate test cases

Tip: Use the **Step Group** feature to create a reusable `SG_FillContactForm` group and insert it into multiple test cases.
{% endtab %}

{% tab title="Regression Testing" %}
**Running regression suites before a release:**

1. Organize your test cases into a **Test Suite** (e.g., "Smoke Tests", "Full Regression")
2. Create a **Test Plan** targeting the regression suite on Chrome + Firefox
3. Enable **parallel execution** — all tests run simultaneously
4. Review the summary: passed count, failed count, flaky tests detected

→ [Managing Test Suites](https://learning.contextqa.com/web-testing/managing-test-suites)
{% endtab %}

{% tab title="Test Data" %}
**Data-driven testing:**

1. Create a Test Data Profile with columns matching your test's variables
2. Add rows for each scenario (valid login, expired account, locked user, etc.)
3. Reference variables in steps: *"Enter `{{username}}` in the Email field"*
4. ContextQA runs one execution per data row automatically

→ [Test Data Management](https://learning.contextqa.com/web-testing/test-data-management)
{% endtab %}
{% endtabs %}

***

## Frequently Asked Questions

**Do I need to know how to code?** No. Test steps are plain English. The AI generates selectors, handles waits, and adapts when elements move.

**What if the AI picks the wrong element?** Use the **Test Steps Editor** to inspect what element was selected and adjust the description if needed. You can also add explicit identifiers like *"the button labeled 'Submit'"*.

**How do I test on different browsers?** Test Plans let you target Chrome, Firefox, and Safari in one run. Results are shown per-browser.

**Can I test behind a login that needs MFA?** Yes. Add MFA handling instructions to your **Knowledge Base** — the AI will follow them every time it encounters the MFA prompt.

***

## Start Here

{% hint style="success" %}
**Recommended path for new testers:**

1. [Quickstart Guide](https://learning.contextqa.com/getting-started/quickstart) — create your first test in 5 minutes
2. [Creating Test Cases](https://learning.contextqa.com/web-testing/creating-test-cases) — full step-by-step guide
3. [Test Data Management](https://learning.contextqa.com/web-testing/test-data-management) — run multiple scenarios from a CSV
4. [AI Self-Healing](https://learning.contextqa.com/web-testing/self-healing) — understand how your tests stay healthy
5. [Mobile Testing](https://learning.contextqa.com/mobile-testing/mobile-testing) — automate iOS and Android app testing
   {% endhint %}

***

{% hint style="info" %}
**Ready to see ContextQA in action?** [**Book a Demo →**](https://contextqa.com/book-a-demo/) — Get a 30-minute walkthrough tailored to your application and testing goals.

*Join teams that reduced manual test maintenance by 70% with AI-powered self-healing.*
{% endhint %}