Test Your OpenText Like Your Users Do
Automated end-to-end tests with Cypress and load tests with JMeter for OpenText Extended ECM. Know before every upgrade, patch or go-live that login, search, documents and workflows still work and stay fast.
Why OTMATE?
Changes to OpenText are risky. OTMATE makes them measurable.
Real User Journeys
A real browser logs in, searches, opens documents and starts workflows, exactly like your users. Every step is measured.
Safe Upgrades
Run the same tests before and after every upgrade, patch or configuration change and see immediately what has changed.
Known Load Capacity
Load tests with JMeter show how many users your platform carries and where it starts to slow down, before your go-live.
Clear Evidence
Reports with results, response times and screenshots of failed steps: documented proof for releases, audits and change approvals.
- ✓Login via single sign-on1.2 s
- ✓Search reference document0.9 s
- ✓Open document in viewer1.6 s
- ✓Upload and version document2.1 s
- ✗Start workflowtimeout
Example run. Failed steps include a screenshot and a video.
End-to-End Tests with Cypress
Technical checks show whether services run. End-to-end tests show whether people can actually work.
Your Business Processes
We automate the journeys that matter to you: login, search, document access, upload, workflows and more.
On Demand or Continuously
Run the tests before and after a change, or every few minutes in production to detect problems before users report them.
Every Environment
The same tests run on TEST, QA and PROD, so you compare like with like.
Load Tests with JMeter
We simulate many users at the same time and measure how your OpenText platform responds, before and after a change.
Performance Baseline
Clear reference values for response times and throughput of your environment under realistic load.
Before / After Comparison
Detect regressions after upgrades, migrations, database or infrastructure changes, and prove improvements.
Capacity Limits
Find out at how many users response times rise, so you can size servers and threads with confidence.
Example values for illustration.
How It Works
From your first workshop to repeatable tests in four steps.
Define
Together we select the business-critical user journeys and the load profile of your organisation.
Build
We build the tests for your environment, with a dedicated test user and test data that do not affect your business data.
Run
The tests run on demand before and after changes, or continuously, on TEST, QA and PROD.
Compare & Report
You receive clear results: what works, what is slower, and where to act, ready for change approval.
Services
Choose what fits your next change, or combine them.
Upgrade Check
For a planned upgrade, patch or migration.
- End-to-end tests of your key journeys
- Run before and after the change
- Comparison report for the change approval
Continuous Testing
For platforms that must work every day.
- End-to-end tests every few minutes on PROD
- Alerts when a step fails or slows down
- Trends and monthly reports
- Tests maintained with every release
Load Test Campaign
For go-lives, sizing and performance questions.
- Load profile based on your real usage
- Baseline and capacity limits
- Recommendations for sizing and tuning
OTMATE works stand-alone or together with OTWATCH: test results then appear in your monitoring dashboards and alerts.
Built by OpenText Operators
OTMATE is made by handel gmbh, the team behind OTWATCH. We have been running and supporting OpenText platforms for more than ten years.
We know where upgrades and changes hurt. With OTMATE we test exactly there, so your users never notice.
Ready for your next change?
Tell us about your planned upgrade, migration or go-live. We will get back to you shortly.
handel gmbh
Grabenstrasse 1
6340 Baar
Switzerland
Plan your first test
Send us your planned change and the most important user journeys. We will propose a test plan.
Send E-Mail