Know what changed against the design before a release goes ahead
Axl Test checks an Ivalua environment against its design package and tells your team where the two disagree, so testers spend their time on the scenarios that need a person.
The problem
On most Ivalua programs, testing is squeezed. The design is long, the build arrives late, and testers check by hand what they can before the date. Differences between the design and the environment surface during user acceptance, or after go-live.
Where Axl Test helps
- Check a build against its design — Point Axl at the design package and an environment. It writes scenarios from the requirements and field dictionary and reports each place where the environment differs.
- Write tests before the build lands — Pre-build suites are written from the design up front. They fail until the release delivers what the design asks for, so you can watch the build catch up.
- Rerun on each drop — Read-only suites can be run again on the same environment for each release drop. In the September 2026 proof of concept, a read-only run took 2 minutes 38 seconds.
- Hand testers a shorter list — Scenarios that need a person are listed and counted as manual, so the test team knows exactly what is left for them.
- Give defects a head start — Each failed scenario comes with a defect draft for Jira, Azure DevOps or Ivalua Extranet, for someone on the project to review and file.
What a first pilot looks like
- Choose one module or business process that has a design package.
- Name the environments Axl may use and what it may do on each. Production-class environments stay read-only.
- Axl writes the scenarios. Your test lead reviews them before any are approved.
- A test lead starts a run, and a Modali operator approves it.
- Review the report with the design and build teams: what passed, what differs from the design, and what remains manual.
From the proof of concept
On the intake module of a US state e-procurement platform, Axl planned 64 scenarios. 36 ran automatically and 21 passed. 15 showed differences from the design across 5 of the 30 requirements, and 28 were left for manual testing. The design was provisional at the time, so the team reviewed the differences rather than logging them as defects.
Bring one design package and one environment. We'll show you what Axl Test finds.