Our Badminton

Connecting to Quality Engineering

Confirming your Administration Suite access securely…

Our Badminton
Our Badminton Administration

Quality Engineering Centre

Configure, execute and govern quality assurance across every environment.

Welcome
Dashboard Administration Suite
Quality readiness

Know whether this release can be trusted.

Validate critical customer journeys, understand genuine automation coverage, and make an evidence-based release decision.

Current release confidenceAssessing…Revision not confirmed
Environment healthCheckingWaiting for configuration
Automated coverage0%Executable requirements only
Requirements without automation0P0 gaps block readiness
Failed or flaky tests0No successful critical journey yet

Changes since the last successful run

A deployed revision comparison will appear after the first successful critical run.

Choose what to validate

Select a business capability. The recommended smoke journey and required services will be prepared automatically.

Choose the environment

Production profiles should use dedicated smoke-test accounts and approved load-test windows only.
Controls environment-aware test behavior.
Applies common Our Badminton endpoint values for the selected environment.

Endpoints

Auth

Quality Engineering uses your active Our Badminton Administration Suite session. Access is controlled centrally through page-level RBAC; no separate Quality Centre username or password is required.

Execution

Functionalities

These selections write helper variables and suggested run scripts into the generated .env.
Use Command/Ctrl click to select multiple profiles.

Advanced

Review test coverage

Requirements are classified by their real execution capability. Catalogue-only entries are never counted as automated.

Choose the functionality whose requirements you want to review

The table will show what is automated, what still needs a manual check, and what is currently blocked.

Change the scope here without returning to the first workflow step.
AutomatedManualNot coveredBlocked
RequirementLayersPriorityCoverageEvidence source

Test runner

Choose a business suite or a focused quality gate, review its scope, then run it.

LOCAL
1
EnvironmentConfiguration selected
2
Choose scopeSuite or quality gate
3
ReviewConfirm command and impact
4
Run and inspectProgress, output, evidence
How to run a validation
  1. 1. Find the functionalityThe list is already filtered from your selected coverage scope. Clear the search to browse everything.
  2. 2. Select ReviewReview shows the scenarios, environment, execution mode and technical command before anything runs.
  3. 3. Start the runChoose a visual browser run when available, or a faster background run, then confirm.
  4. 4. Inspect evidenceFollow live steps on the right. Open Visual report or Test library when the run finishes.

Available test scopes

Business suites run mapped checks together. Quality gates run one framework.

Test library

Import a catalogue, review its coverage, then execute automated or manual cases.

1
Select fileExcel, CSV, or JSON
2
ValidateCheck fields and mappings
3
ImportCreate or update catalogue
4
ExecuteAutomation or manual steps

Import a test catalogue

Upload the workbook directly. Validation is read-only and always happens before the catalogue changes.

.xlsx · .csv · .json
Required columns TestCaseId (or id), TestCaseName (or name), and Suite. The attached Tournament Manager workbook uses the supported Test Cases sheet.

Cases and manual execution

Filter the catalogue, open a case, complete each step, and record evidence.

Test Case Suite / Type Status Priority Owner Expected result Action
No test cases loaded.
Page 1 of 1

Review evidence

Inspect business steps, browser evidence, API contracts, console errors and the exact revision tested.

No validation evidence yetRun the recommended smoke suite to produce release evidence.

Release decision

The decision is calculated from environment readiness, P0 coverage and execution evidence.

Calculated outcome
Do not release

Critical evidence is incomplete

P0 requirements without executable evidence prevent a trusted release decision.

Preview

Review test run

Confirm the scope and environment before any command is started.

Selection-
Environment-
Mapped scenarios-
Run experience

Visual mode shows a labelled cursor moving to each control before it acts. API, security, performance, and unit checks continue in the background. Screenshots, video, trace, and a detailed step timeline are captured automatically.

Command 
-
Imported cases become part of the catalogue and manual workspace. Automated results are recorded only when the mapped Playwright, Jest, Supertest, security, visual, Lighthouse, or k6 specifications emit evidence for those case IDs.

Test case

Review the data, complete the steps, and record evidence.

Suite-
Type-
Page-
Description

-

Preconditions

-

Expected result

-

Test data JSON 
{}
Manual steps
0 of 0 complete
Loading current configuration...