Around 2,500 use cases, re-run on every 3DEXPERIENCE release — for more than five years.
What happens when a PLM team stops re-testing by hand and keeps the tests instead.
Ericsson
Telecommunications equipment · Global
At a glance
- Platform
- 3DEXPERIENCE
- Tooling
- Test Automation Suite (TAS), on Playwright
- In use
- 5+ years
- Coverage
- ~2,500 test use cases
Results
~2,500
Test use cases automated
Regression coverage across the 3DEXPERIENCE processes in scope, as of 2026
5+ years
In continuous use
Release after release, upgrade after upgrade, on the same test library
The challenge and what we did
The challenge
- A 3DEXPERIENCE estate that never stands still: releases, customisations and platform upgrades, and each one a reason to re-check the same business processes.
- Regression done by hand does not scale with the system. Every change added to the pass; nothing ever came off it.
- The people who know the processes best — business users and QA — were spending their time re-running checks they had already run.
What we did
- Built the regression suite as reusable test cases in the Test Automation Suite, written in PLM terms through the Tag Libraries — create a Part, revise a BOM, route a Change — rather than as screen scripts tied to one release.
- Grew the library release by release to around 2,500 use cases, kept in one place and re-run rather than rewritten.
- Ran it as the regression pass on every release and upgrade: in parallel, on a schedule, with a report of what passed, what failed and what needed attention.
A system that never stands still
PLM at this scale changes constantly. A new 3DEXPERIENCE release, a customisation for one part of the business, a platform upgrade — each one has to be tested against the processes people actually run, and each one adds to the list. Done by hand, the regression pass only ever grows.
Test once, then keep it
The suite was built so that a test outlives the release it was written for. Cases are expressed in PLM terms through the Tag Libraries, so a test says “revise the BOM”, not “click the third tab”. Where a process genuinely changed, the test said so — which is the result you run it for.
- Reusable cases, kept in one library
- Written as PLM actions, not selectors
- Re-run, not rewritten, on each release
Five years later
The library now covers around 2,500 use cases and has run through more than five years of releases and upgrades. The manual regression pass those cases replace is no longer done by hand. That time is the return — and it comes back on every release, not once.
Filed under
- 3DEXPERIENCE
- Quality Assurance
- Test Automation Suite
- Regression testing
- Test automation
More customer stories
FMCG · 3DEXPERIENCE
Indexed Search, Without Losing the Last Five Minutes of Data
A North American FMCG manufacturer
3DEXPERIENCE upgraded to 2015x with a custom solution letting users switch between indexed search and real-time search, so newly created data stayed reachable.
Fashion Retail · 3DEXPERIENCE
Forty Enhancements and an Upgrade, With the Migration Scripts Rewritten to Run in Parallel
A fashion retail customer
3DEXPERIENCE upgraded from 2017x to 2021x alongside forty enhancements, with the upgrade’s data migration scripts re-engineered for concurrent execution across partitioned data.
Industrial Equipment · 3DEXPERIENCE
Two Million CAD Objects Upgraded Over a Single Weekend
A German industrial equipment manufacturer
3DEXPERIENCE upgraded from 2015x to 2018x, with the full CAD migration parallelised across multiple machines and completed inside one weekend.
Behind this story.
The services and products this project used, and an expert to talk to about yours.
Talk to a 3DEXPERIENCE expert