NextTest Automation Masterclass

Welcome to modern test automation. For over a decade, testing teams have faced a difficult compromise: low-code record-and-playback tools that break as applications scale, or code-heavy frameworks (Selenium, Playwright, Cypress) requiring hundreds of lines of boilerplate code.

NextTest bridges this gap. It provides a clean, visual desktop studio coupled with a headless command-line runner that executes on top of dual native engines: Selenium WebDriver and Playwright.

1.1 Core Platform Architecture

• Dual-Engine Core: Run tests on Selenium for cross-browser enterprise maturity or Playwright for high-speed modern web applications.
• Multi-Surface Coverage: Automate Web browsers, REST APIs, native Windows desktop software, and Visual regression checks in a single suite.
• Zero Installation Friction: NextTest is fully portable. No complex node_modules, Python virtual environments, or package registries required.
• Built-In Heuristic Auto-Healing: Dynamic locator recovery prevents flaky builds by auto-recovering changed selectors during execution.

In NextTest, test scenarios are stored in clean, transparent data formats: structured JSON files or standard Microsoft Excel (.xlsx) workbooks. This makes tests easy to version in Git, review in pull requests, and edit in any text editor.

2.1 Anatomy of a JSON Test Suite

Every NextTest suite is structured into metadata, shared suite data, and sequential test cases:

{
  "name": "User Authentication Smoke Suite",
  "platform": "WEB",
  "engine": "SELENIUM",
  "data": {
    "baseUrl": "http://127.0.0.1:3100",
    "adminUser": "admin@quickitdotnet.in"
  },
  "testCases": [
    {
      "testCaseId": "AUTH-001",
      "Case": "Successful Admin Login",
      "isRun": true,
      "hardStop": true,
      "testSteps": [
        {
          "steps": "Open Chrome to application login",
          "action": "openBrowserChrome",
          "value": "${baseUrl}",
          "isRun": true
        },
        {
          "steps": "Enter admin email",
          "action": "sendKeys",
          "locatorType": "id",
          "locatorTypeValue": "username",
          "value": "${adminUser}",
          "isRun": true
        },
        {
          "steps": "Click submit button",
          "action": "click",
          "locatorType": "css",
          "locatorTypeValue": "button[type='submit']",
          "isRun": true
        },
        {
          "steps": "Validate dashboard banner",
          "action": "validateText",
          "locatorType": "css",
          "locatorTypeValue": ".dashboard-welcome",
          "value": "Welcome back",
          "isRun": true
        }
      ]
    }
  ]
}

2.2 Important Suite Attributes

• isRun (Boolean): Enables or disables an entire test case or individual step without deleting it.
• hardStop (Boolean): If set to true, a failure in this step immediately aborts remaining cases (crucial for prerequisite login steps).
• data Dictionary: Stores environment variables and shared test data referenced via ${variableName}.
• {{PASSWORD}} Placeholder & enterEncryptedPassword: Secure AES-256-GCM encrypted credential protection. Plaintext is never written to disk or logs (••••••••), and tokens are automatically decrypted in memory for web inputs, mobile fields, desktop apps, and REST API calls.
• locatorType / locatorTypeValue: The canonical locator pair used by the shipped samples—for example css with button[type='submit']. Older suites may also use locator/locatorValue, which the loader still accepts.

NextTest catalogues 214 actions, prefixes, and keywords (including 200 core test execution actions), and the core web and API sets are verified against the shipped runner. From REST API calls, multi-tab management, and nested iframes to dropdowns, alerts, and drag-and-drop, modern interactions are covered natively out of the box.

3.1 Essential Web Action Catalog

The actions below are covered by the bundled suites and were exercised against the v1.0.0 runner.

Test maintenance is the #1 pain point in quality engineering. In modern web frameworks, developer updates to IDs, dynamic classes, and nested containers cause traditional test runners to throw NoSuchElementException, failing nightly build pipelines.

4.1 How It Works Under the Hood

1. Initial Execution: NextTest attempts to find the element using the configured locator (e.g. #submit-btn).
2. Heuristic Fallback: If not found within timeout, the auto-healing engine inspects candidate elements matching the element's tag, accessible role, and text content.
3. Live Recovery: NextTest performs the interaction on the highest-confidence recovered element and marks the test status as HEALED.
4. Persistent Suite Healing: When run with the --apply-healing flag, NextTest rewrites the healed selector back into your test suite JSON file on disk, permanently updating your test!

.\NextTest.bat --run .\sample-application\scenarios\01-admin-student-crud.json --headless --self-healing --apply-healing

Modern applications rarely consist of only a frontend UI. NextTest lets you describe API steps inside the same suites as your browser tests, so a single runner covers an end-to-end integration workflow.

5.1 Hands-On Token Chaining Workflow

A common enterprise pattern is authenticating via an API endpoint, extracting a dynamic JWT Bearer token from the response, and reusing that token in later requests:

[
  {
    "steps": "Authenticate Admin User",
    "action": "api-POST",
    "value": "/api/auth/login",
    "actualValue": "{\"BaseUrl\":\"http://127.0.0.1:3100\",\"Headers\":{\"Content-Type\":\"application/json\"},\"Payload\":{\"email\":\"admin@quickitdotnet.in\",\"password\":\"Admin@123\"}}",
    "isRun": true
  },
  {
    "steps": "Fetch Student Directory with Dynamic Bearer Token",
    "action": "api-GET",
    "value": "/api/students",
    "actualValue": "{\"BaseUrl\":\"http://127.0.0.1:3100\",\"Headers\":{\"Authorization\":\"Bearer {{authToken}}\",\"Content-Type\":\"application/json\"}}",
    "isRun": true
  }
]

NextTest parses the JSON response, extracts fields such as token, and maps them to {{authToken}} for reuse in later steps. The API Collection tab shows the traffic a run produced.

Validating that the user interface matches the underlying database is critical. NextTest includes a full JDBC Database Workbench supporting PostgreSQL, MySQL, SQL Server, Oracle, and SQLite.

6.1 Excel Data-Driven Iterations

Instead of hardcoding customer details, link an Excel spreadsheet in your suite data:

• Set "dataFiles": [{ "name": "data/students.xlsx" }] in suite data.
• Reference columns in steps: ${studentName}, ${email}, ${course}.
• NextTest runs the test case automatically for every row in your spreadsheet.

NextTest extends beyond the browser. It automates native Windows desktop software (WPF, Win32, WinForms, Electron) and provides pixel-accurate visual snapshot regression testing.

7.1 Visual Snapshot Verification

Using the action validateVisualBaseline, NextTest compares the live viewport against a baseline master image. Layout shifts, broken fonts, and pixel misalignments are flagged in red-line diff evidence reports.

NextTest can run entirely headlessly without a graphical display, making it ready for automated build pipelines such as GitHub Actions, GitLab CI, Jenkins, Azure DevOps, and Docker.

8.1 Ready-to-Use GitHub Actions Workflow

name: NextTest CI Pipeline

on: [push, pull_request]

jobs:
  test:
    runs-on: windows-latest
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-java@v4
        with:
          java-version: '17'
          distribution: 'temurin'
      - name: Execute NextTest Headless Regression
        run: |
          .\NextTest.bat --run .\sample-application\scenarios\01-browser-lifecycle-and-navigation.json --headless --self-healing --output-dir .\reports
      - name: Upload HTML Test Reports
        uses: actions/upload-artifact@v4
        if: always()
        with:
          name: test-reports
          path: .\reports

NextTest bundles an action catalog specification in COMMANDS.md. You can share this catalog with modern AI models (ChatGPT, Claude, Gemini) to transform everyday user stories into structured NextTest suites.

Congratulations on completing the modules! Put your skills to the test with the CampusFlow Student Registration capstone challenge bundled in sample-application/.

Capstone Objectives:

1. Start the CampusFlow web application (npm install && npm start at http://127.0.0.1:3100).
2. Author a UI scenario automating Admin Login and validating dashboard counters.
3. Execute a data-driven registration flow reading 5 student records from Excel.
4. Simulate an element ID rename in HTML and verify NextTest auto-heals the locator.
5. Verify the newly registered students via an api-GET request to /api/students.
6. Generate interactive HTML execution reports.

NextTest bundles 43 JSON suites and 35 Microsoft Excel (.xlsx) workbooks in sample-application/scenarios/. These scenarios demonstrate battle-tested automation across Web, REST API, native Windows Desktop, Accessibility, and Data-Driven workflows.

11.1 Shipped Scenario Catalog

All test suites can be executed interactively in NextTest Studio or headlessly via the command-line runner.

In modern enterprise test automation, functional correctness is merely the baseline. High-performing QA teams also continuously audit digital accessibility, link integrity, asset health, and tabular data reliability.

12.1 Automated Accessibility Audits (WCAG 2.1 AA)

NextTest provides the checkaccessibility action to run zero-configuration accessibility audits directly within your test scenarios. It analyzes the rendered DOM against international accessibility standards (WCAG 2.1 Level A and AA).

{
  "steps": "Audit campus student portal for WCAG 2.1 AA compliance",
  "action": "checkaccessibility",
  "locatorType": "NA",
  "locatorTypeValue": "NA",
  "value": "WCAG2AA",
  "isRun": true
}

12.2 Website Asset & Dead Link Detection

Broken hyperlinks and missing images degrade user experience and trigger customer support escalations. NextTest provides dedicated actions to validate these assets in real time:

• validatebrokenlink: Scans all <a href="..."> anchors on the active page, makes asynchronous HEAD/GET requests, and asserts that no links return HTTP 404 or 500 status codes.
• validatebrokenimage: Inspects all <img> tags, checks image HTTP status codes, and verifies via browser JavaScript that image.naturalWidth > 0.

{
  "steps": "Verify zero broken links on registration page",
  "action": "validatebrokenlink",
  "locatorType": "NA",
  "locatorTypeValue": "NA",
  "value": "NA",
  "isRun": true
},
{
  "steps": "Verify all course thumbnails and logos load successfully",
  "action": "validatebrokenimage",
  "locatorType": "NA",
  "locatorTypeValue": "NA",
  "value": "NA",
  "isRun": true
}

12.3 Advanced Grid & Table Data Validations

Enterprise applications rely heavily on data tables with sorting, pagination, and action buttons. NextTest provides specialized actions to validate complex data grid behaviors without fragile custom JavaScript: