Use case: Internal tools
End-to-end testing for internal tools
Internal tools such as admin panels, approvals and reports rarely get test engineers, yet the operations team depends on them every day.
Flows to cover first in internal tools: admin panels, approvals, reports. Each flow becomes a spec: a YAML file with plain-English steps that runs locally or in CI.
- Specs are plain English, so the operations person who knows the approval flow can read and review the test.
- Admin panels are rebuilt often. Locator and layout changes are healed and recorded for review.
- Tests can run locally in Chromium without the cloud, with npx aitp run.
1name: Manager approves a refund request2url: https://admin.example.com3tags: [approvals]4env:5 EMAIL: ${MANAGER_EMAIL}6 PASSWORD: ${MANAGER_PASSWORD}7steps:8 - Log in with EMAIL and PASSWORD9 - Open "Approvals"10 - Open the newest refund request11 - Click "Approve"12 - assert: The request status is "Approved"Capabilities used
Tests in plain English
A test is a list of steps in plain English in a YAML file; the platform resolves each step against the live page at run time.
Read moreHeals locator and layout changes
When a step no longer resolves because an element moved, was renamed or restyled, the platform re-resolves it, marks the test as healed and records the change for review.
Read moreRuns in CI
One CLI command runs a suite in CI and reports a pass, fail or healed status per test as a check on the pull request.
Read moreCommon integrations
Questions
Who writes tests for internal tools?
Anyone who can describe the flow in steps. Specs are plain English in YAML files, reviewed like code.
Can the tests run without the cloud?
Yes. npx aitp run runs all tests locally in Chromium.
Request early access
Early access: prices are the planned list prices. Billing starts when the platform enters beta; early-access use is not charged. We reply within 24 hours on business days.