You test a real device, you note measurements and in the end you hand over a record that withstands an audit. XPressRT is the software for exactly that workflow: you run your test manually first, automate individual steps as soon as it pays off – and every run writes its own record as it goes.
Basics
What is XPressRT?
XPressRT is software for system tests on real devices. You build your test procedure from manual operator steps and automated instrument steps – both run one after another in the same procedure and produce an audit-ready record per unit: the measured value against its limit, serial number, firmware state, the instrument used and the tester.
XPressRT is part of our holistic test management: where you test against real embedded hardware, LoopCheck (Hardware-in-the-Loop) covers the real signal side.
Six months on, your customer asks about serial number 0042
The device left your plant long ago, and now the question is on the table: what exactly was tested on this one unit? A record kept by hand reaches its limits here – the answers are scattered across spreadsheets, emails and people’s heads:
- Was the measured value – 4.7 V against a limit of 4.5 to 5.0 – really inside the window?
- Which firmware state was on serial number 0042 when it was tested?
- Was the multimeter calibrated in March, when the run took place?
- Who tested it – and were they qualified to do so?
For a handful of units you can reconstruct this. At 5,000 you can’t.
How you test
The manual step and the measurement in one procedure
The operator’s action and the instrument’s measurement belong in the same procedure – not in two tools with the record falling apart in between. In XPressRT both kinds of step sit side by side:
The operator fits the sensor
A manual step states what to do – fit a connector, a visual check, read a value and confirm it – and goes into the record like any other.
The power supply ramps to 24 V
An automated step has an instrument measure or drive. You choose rather than program: which instrument, what it should do, which limits apply, how it is reported.
Your equipment
Your multimeter goes for calibration – your test cases stay
A test procedure asks for “a multimeter”, not your specific unit with that serial number. Send one meter off for calibration and plug in another, and your test cases run on unchanged – no scripts to rewrite, no requalifying the whole test. Swapping an instrument is a matter of minutes.
Your path
Start by hand, automate later
You don’t have to choose between manual work and automation, and you don’t set up a project for it. You start with the procedure you already have today and replace individual steps when they pay off:
By hand
You work through the steps, XPressRT records along. Ready to use immediately, with no instrument connection.
Step by step
You let an instrument take over the worthwhile steps. The rest stays manual – in the same run.
Full test stand
You connect equipment and test stand completely. The same procedure as on day one, just faster.
Record & audit
Every run writes its own record
Which device
Serial number, product and firmware state – scanned or entered at the start and the key for everything that follows.
What was tested
Every step in plain words, marked passed, failed or skipped – manual and automated alike.
What was measured
The actual value against its limit – as a table or a curve, with the instrument used and its calibration state.
Who, where and when
Tester and qualification, test bench, timestamp and the duration of every step.
So the record answers the question about serial number 0042 itself – without the person who built the test, and without hunting through spreadsheets and emails. Alongside the readable report there is machine-readable output (JUnit XML and a raw log) for your own analysis.
Getting started
Your existing procedures come along
Your test instructions live in documents and spreadsheets today. You don’t retype them: XPressRT reads them in and presents them to you as a suggestion to confirm. The original document and its version stay attached to the test case, and what was already approved stays approved.
Traceability
Your requirements system stays where it is
XPressRT does not replace Polarion, Codebeamer, Jama or DOORS – your requirements stay there. XPressRT adds the execution and evidence layer on top:
The requirement on the step
Every test step carries the requirement ID it covers – the link is made where testing actually happens.
What is proven
A coverage matrix shows which requirement is proven by which run – down to the individual record.
No write-back
Requirements come in by ID, ReqIF, Word or Excel. XPressRT writes nothing back into your system.
Price
The frontend is free
Creating procedures, testing by hand and documenting – you pay nothing for that, and you can self-host the frontend permanently. A licence only applies where hardware is involved: the equipment plugins and the runner that execute your steps automatically. You pay for automation when you use it – not to get started.
Frequently asked questions about XPressRT
What is XPressRT for?
For system tests on real devices that have to be documented: verification, acceptance, end-of-line. Manual and automated test steps run in one procedure and produce an audit-ready record per unit.
Do I have to automate everything?
No. You start by hand and replace individual steps as soon as it pays off – no automation project and no migration. The same procedure carries you from manual work to a fully automated test stand.
What happens when I swap an instrument?
Nothing changes in your test cases. They are bound to a role ("a multimeter"), not to a specific serial instrument – swapping means minutes instead of requalifying the whole test.
Does XPressRT replace my requirements system?
No. Your requirements stay in Polarion, Codebeamer, Jama, DOORS or the specification. XPressRT provides the execution and evidence layer on top – requirement ID on the step, coverage matrix, integrated by ID, ReqIF, Word or Excel, with no write-back.
Can I adopt my existing test procedures?
Yes. Procedures from documents and spreadsheets are imported as a suggestion to confirm, with the original document and version kept attached to the case. Approved test cases stay approved.
Test and document – from the first manual run
The full user documentation – procedures, manual and automated steps, instruments, records and traceability – is on the XPressRT docs.
- Manual and automated steps in one procedure
- An audit-ready record per unit: value, limit, calibration, tester
- Adopt existing procedures instead of retyping them
- Evidence layer on top of Polarion, Codebeamer, Jama, DOORS