Platform · AI Test Center

AI Test Center

Give system administrators an isolated workspace for reviewed browser testing and verification evidence. Approved test environments, setup discovery, reviewed tests, execution evidence, and scheduled test packs.

In short

It is a dedicated administrative workspace for approved test targets, setup discovery, reviewed tests, execution, and retained browser-verification evidence.

What it does

AI Test Center

01

Define an isolated target

Configure the approved environment and test context before a browser-testing workflow is run.

02

Review the testing work

Use supported reviewed browser-testing workflows rather than treating the administrative tool as an unrestricted business-user feature.

03

Examine results and evidence

Review execution results and the evidence gathered during the verification run.

04

Support controlled troubleshooting

Use verification evidence to inform platform investigation while retaining the tool’s separate administrative access controls.

How it works

Administrators can review what was tested and what evidence supports the result.

  1. Configure the approved isolated test target.

  2. Review and execute the supported testing workflow.

  3. Inspect the result and supporting verification evidence.

Features

16 features

16 named features across the areas below.

Test-site setup

5 features

Use a controlled test target and its real configuration.

  • Approved test origins and sitesRegister the permitted test-copy address and enforce the supported target-origin controls.
  • Saved test loginsAssociate the authorized role/user login with the intended test environment.
  • Read-only setup discoveryRead supported company, currency, enabled areas, and sample master context from the target.
  • Standard setup-check packCreate the supported test pack using the target’s discovered configuration.
  • Retained setup notesKeep the test’s site, login, assumptions, and selected records with the test and its results.

Test authoring and review

5 features

Make the expected behavior explicit before a run.

  • Plain-language test definitionDescribe the user action, starting context, and expected visible result.
  • Prepared test stepsReview the supported generated or edited executable steps.
  • Version approvalRun only approved versions; editing a test resets its approval.
  • Related API and coverage contextInspect the supported related-service and coverage views under the technical tools.
  • Test packsGroup compatible tests under the permitted company/branch context.

Execution and evidence

6 features

Review the outcome rather than assuming that a run proves success.

  • Live run progressFollow the supported step-by-step test-machine execution state.
  • Result verdict and evidenceReview the result summary and the retained verification evidence.
  • Screenshots and replay artifactsInspect the supported browser evidence and technical downloads.
  • Scheduled pack runsConfigure the supported repeat interval and start time for approved tests.
  • Run and setup historyRead earlier execution and configuration context without losing the test’s assumptions.
  • Administrative access boundariesKeep test-site credentials, approvals, cleanup, and execution under the dedicated administrator permissions.

Worked example

A reviewed test keeps its assumptions

A result is useful only when the target, login, setup, steps, expected outcome, and evidence remain understandable.

  1. Prepare

    Approve the isolated test site and read its supported setup context.

  2. Specify

    Write the business action and expected outcome, then review the prepared steps.

  3. Approve

    Approve the eligible version; later edits require renewed approval.

  4. Execute and review

    Run the test or eligible pack and inspect the verdict and retained browser evidence.

What you get

What you get

  • Approved test sites and setup context

  • Versioned, reviewed tests and packs

  • Execution verdicts and browser evidence

  • Scheduled-run and configuration history

What is the AI Test Center?

It is a dedicated administrative workspace for approved test targets, setup discovery, reviewed tests, execution, and retained browser-verification evidence.

How does a reviewed test run?

Register the permitted test environment and login, read the supported setup, define and review the business steps and expected result, approve the eligible version, then run it and inspect the verdict and evidence.

Can an edited test run under its earlier approval?

The supported version workflow resets approval when the test changes. Only an approved eligible version may run.

How does a test retain the setup it depended on?

The test records its approved target, saved login, discovered setup, selected records, and setup notes. That context is retained with the result so it can be understood later.

Does one passing test establish that the whole ERP is correct?

No. Review the test’s actual steps, expected outcome, environment, and evidence. A passing result establishes only the observed result for that defined run.

Book a demo

See Prospiro run your own process.

Tell us what you sell, stock and deliver. We plan the session around the modules you need, in English or Arabic.

  • Built around your products, routes and documents
  • Includes the exceptions, not only the happy path
  • Your request goes straight to our team

Prefer email? info@prospiro.ai

What do you want to see?
We use your details only to reply to your request and follow up on it. Privacy policy
VAT calculator