Ericsson
Five years of automated 3DEXPERIENCE regression testing
Around 2,500 use cases, re-run on every release.
3DEXPERIENCE · Aras Innovator
Test Automation Suite
A configurable test automation suite that helps PLM teams build, run, and reuse automated tests across releases — reducing manual testing and shortening validation cycles.
- Reusable Test Cases
- Automated Regression Testing
THE REALITY OF PLM TESTING
PLM Testing Gets Harder With Every Change
Every upgrade, customisation, and release brings another round of testing. The same business processes need to be checked again, while changes in one area can affect another. As the PLM system grows, so does the effort needed to keep testing it.
Where the time goes
- The same tests run by hand, release after release
- Regression cycles that grow with the system
- Not enough time in the window to test everything
- A change in one area breaking something in another
- Business and QA people tied up in repeat testing
REUSABLE PLM TESTING
Automate the Tests You Keep Repeating
Create reusable test cases once and run them whenever you need them — after an upgrade, configuration change, new release, or other PLM change.
Build
Create the test once.
Reuse
Keep it in your test library.
Run
Run it against a new release, configuration, or environment.
Results
See what passed, what failed, and what needs attention.
What you can automate
- Functional Testing
- Regression Testing
- Workflow Testing
- Integration Testing
- Data Validation
- Release Testing
Less time repeating tests. More time improving the PLM system.
AI-ASSISTED TESTING
Record One Test. Get the Variations.
Record a test case once. The suite works out the permutations and combinations that the PLM process allows, and builds them out — so the team reviews variations instead of writing each one by hand.
Record
One test case, captured as you run it.
Derive
The permutations and combinations the PLM process allows.
Generate
The variations, written out as test cases.
Review
The testing team checks and adjusts.
The suite widens the coverage. The testing team still decides what ships.
BUILT FOR PLM
Test the PLM Systems You Actually Use
TAS is designed around PLM testing — not generic software testing — so test cases can reflect the objects, processes, workflows, and integrations used in your PLM environment.
How it fits together
Implementing Aras Innovator?TAS is the Test Automation step in Rabbit Implementation Studio
PROVEN IN REAL PLM PROJECTS
Built for the Testing That Happens in Real Projects
TAS has been used to support PLM testing across upgrades, customisations, releases, and ongoing changes.
By the numbers
- 5+
- Years in continuous use
- ~2,500
- Test use cases automated
- 2
- PLM platforms
Years and use-case figures are one customer’s, on 3DEXPERIENCE — the first story below.
Case studies
Multi-Site Enterprise
Release assurance on a high-risk change
Validating a change with a wide blast radius before it reached production.
Discrete Manufacturer
Wrong-BOM defect caught before go-live
A BOM error found in testing rather than in production.
GET STARTED
Spend Less Time Repeating Tests
Let us look at your current PLM testing process and identify what can be automated and reused.
PLM Quality Assurance
The suite is the tooling. If you would rather someone ran it, our Quality Assurance team does the testing alongside your own — or instead of it.
- Review the current testing process
- Pick the cycles worth automating first
- Build the reusable test cases
- Run them on each release
- Hand over, or keep running them
QUESTIONS
Before You Ask Us
Either. Teams use the suite directly, with our testers setting it up and handing it over. If you would rather not run it in-house, our Quality Assurance service does the testing for you. Which way round it works is worth a conversation — tell us who would be using it and we will tell you what that looks like.
3DEXPERIENCE and Aras Innovator. Connected systems such as ERP and MES can be tested to the extent the PLM process under test reaches into them, rather than as systems in their own right.
Functional, regression, workflow, integration and release testing, plus data validation. In practice that means the business processes you re-check after every change: creating and revising parts, moving a BOM, running a change through its workflow, and the exchanges with connected systems.
That is the point of building them this way. A test case lives in the library rather than in the release it was written for, so the same case runs against the new version. Where the upgrade genuinely changed a process, the test tells you — which is the result you wanted from running it.
You record one test case. The suite works out the permutations and combinations that the PLM process allows and builds them out as further cases, so the team starts from a set of variations instead of writing each one by hand. The team reviews them before anything runs — the AI widens the coverage, it does not decide what ships.