A clearer workflow for automated web testing.
Testivra is being designed to connect test creation, execution, maintenance, and investigation in one workspace.
A check is a written user journey with assertions, statements of the expected result that each run compares against what the browser shows. Every capability below carries its stage label.
- Smoke3
- Critical journeys1 failed
- Regression1 failed
- SaaS account flows4
- Sign-up with email confirmationc-07
- Account email changec-08
- Password changec-09
- Checkout with saved payment methodc-10
- Order history lists the new orderc-11
- Expected
- Confirmation email link activates the account
Create and review scenarios
PlannedDesigned to let your team define user actions and expected results. Review generated checks before relying on them.
What it is planned to do
- Accept a written description of a user journey, its environment and the expected outcome
- Propose test steps and assertions for review
- Keep the reviewed version as the check that runs
What it will not do
- Decide which journeys matter; the team defines scope
- Run a check that has not been reviewed
Example. A team would describe 'new user signs up with email, confirms, lands on the dashboard' and review the proposed steps before saving the check.
Limitation. Proposed steps need review by someone who knows the application.
- Smoke3
- Critical journeys1 failed
- Regression1 failed
- SaaS account flows4
- Passed12
- Failed2
- Skipped1
- Purchase from product page to confirmationFailed
- Booking with date selectionPassed
- Subscription renewal and plan changePassed
Organize and run tests
PlannedDesigned to let your team group checks by workflow and run the scenarios relevant to a change.
What it is planned to do
- Group checks by workflow
- Run a selected group on demand
- Run a selected group on a schedule
What it will not do
- Run inside the customer's CI until a CI integration is available
- Test native mobile applications
Example. Before a release, the team would run the checkout group against staging and read the summary.
Limitation. Environment access and test data are set up by the team.
- Smoke3
- Critical journeys1 failed
- Regression1 failed
- SaaS account flows4
Review maintenance suggestions
PlannedDesigned to let your team inspect proposed updates when application changes affect existing tests.
What it is planned to do
- Detect when a check fails because a page or element changed rather than because behaviour changed
- Propose an update to the affected step for review
What it will not do
- Apply updates without review
- Promise that every change is detected
Example. A renamed button breaks a step; the suggested update would show the old and new step for approval.
Limitation. Suggestions are proposals; the team decides whether behaviour or the test should change.
- Smoke3
- Critical journeys1 failed
- Regression1 failed
- SaaS account flows4
- Purchase from product page to confirmationFailed
- Booking with date selectionPassed
- Subscription renewal and plan changePassed
Investigate failed checks
PlannedDesigned to let your team review execution details and screenshots to understand where a run went wrong.
What it is planned to do
- Show the failed step, expected and actual outcome, a screenshot and execution details in one view
- Mark items that need a human decision
What it will not do
- Diagnose the root cause in application code
- File tickets in external trackers until an integration is available
Example. A checkout check fails at 'confirm order'; the report would show the step, the screenshot at failure and the request log.
Limitation. Investigation and release decisions stay with the team.
What the product is designed for
Designed for
- Regression checks on existing workflows
- Smoke checks on essential functionality
- Critical user journey checks (sign-up, checkout, subscription changes)
Not designed for
- Mobile native applications
- Load and performance testing
- Security testing
- Accessibility audits
- Unit or API-only testing as a primary workflow
- Form factor
- Web application (hosted workspace)
- Target applications
- Web applications; functional testing of user journeys in a browser
- Browsers
- Not publicly specified
- Hosting
- Not publicly specified
- CI
- No CI integration is available yet; CI triggers are on the roadmap.
Data handling
- Test credentials are provided by the customer for test accounts only; production credentials are not requested.
What would you like to stop checking manually?
Tell us about your application and testing challenges. We'll follow up about early access and whether Testivra fits your needs.