TotalApp Docs
Ctrl K
EN | TR
Go to App

Web Test Module Coming Soon

Visual test recorder and multi-browser executor powered by Playwright.

In Active Development

Web Test Module is not yet available. This page describes the planned feature set so your team can plan ahead. The screen appears in the Manage Screens modal as a disabled entry — it will become active automatically when it ships.

What Web Test Module Will Do

Web Test Module brings Playwright test authoring and execution directly into TotalApp, eliminating the need to switch between your browser, a code editor, and a terminal to write and run end-to-end tests. The module is designed for QA engineers who want a guided, visual workflow without giving up the power of the full Playwright API.

Visual Test Recorder

Record tests by interacting with your application in a built-in browser panel. Playwright codegen captures every click, fill, and navigation as typed TypeScript test code in real time.

Multi-Browser Execution

Run tests against Chromium, Firefox, and WebKit from a single interface. Select one or all three browsers per run. Results and artifacts are grouped by browser.

Parallel Workers

Configure the number of Playwright workers to parallelise test execution. A slider controls worker count from 1 (serial) to the maximum your machine supports.

Planned Workflow

  1. Open Web Test Module from the QA section of the sidebar.
  2. Click New Recording to open the visual recorder. Enter the target URL and click Start.
  3. Interact with your application — clicks, form fills, navigations. The recorder panel shows the generated Playwright TypeScript code updating in real time.
  4. Click Stop Recording when done. Review and edit the generated code in the built-in editor.
  5. Click Run to execute the recorded test. Select target browsers and worker count from the run options panel.
  6. Results appear in the Results panel with pass/fail per browser. Artifacts (screenshots, traces) are automatically sent to Artifact Vault.
  7. Save the test to your suite. It will also appear in Test Plan as a new test case.

Browser Support

Web Test Module will support all three Playwright browser engines:

Engine Covers Notes
Chromium Chrome, Edge, Brave Default browser for recording. Fastest and most widely used.
Firefox Firefox Useful for catching CSS rendering differences and Web API gaps.
WebKit Safari, iOS Critical for catching Safari-specific issues before they reach production.

Run all three for cross-browser confidence

Running the same test suite across all three engines adds less than 30% to total run time (thanks to parallel workers) but catches a significant share of browser-specific bugs before they reach users.

Integration with Other QA Screens

Web Test Module is designed to feed the rest of the QA module automatically:

  • Artifact Vault — Every test run automatically pushes screenshots and traces to Artifact Vault. No manual upload step.
  • Flake Tracker — Retry data from Web Test Module runs is reflected in Flake Tracker's retry rate calculations. A test that passes on the second attempt increments the retry count for that test.
  • Test Plan — Saved tests from Web Test Module appear as test cases in Test Plan. Execution results are linked to the plan so coverage metrics stay up to date.

FAQ

When will Web Test Module ship?
The screen appears in the Manage Screens modal as a disabled entry today. It will become active and clickable automatically when development is complete — you do not need to do anything to enable it.
Will it replace my existing Playwright project?
No. Web Test Module is an authoring and execution layer on top of Playwright. Tests recorded here will be standard Playwright TypeScript files that you can also run from the CLI, CI, or your existing playwright.config.ts.
Is there a limit on the number of tests I can record?
There is no planned hard limit on test count. Storage and concurrency limits will depend on your plan and infrastructure configuration.