Who is it for?
- Test software vendors who want a product that fits the reality of battery labs.
- Bench integrators who deliver a complete bench and must make it work at the customer's site.
- Test teams building their own automation tool or upgrading an existing one.
What I bring
Testing requirements translated for developers
I write functional specifications from real tests: control modes (current, voltage, power), step transition conditions, software safety limits, climatic chamber control, structure of the recorded data.
Test writing and libraries
Writing test sequences, parameter setup, reusable test libraries and complete campaign set-up. It is also the best way to find what the software is missing.
Hardware integration
Power supplies, cyclers, NI PXI and cDAQ acquisition systems, climatic chambers: configuration, commissioning procedures and measurement checks.
Acceptance testing on real benches
Software test plans, bench tests, issue reporting and tracking, corrective and application support until production.
Documentation
Configuration procedures, user guides and technical notes, written for the operators and technicians who will use the bench every day.
Why a testing expert rather than one more developer?
Bench software problems rarely come from the code itself. They come from a misunderstood test, a missing safety limit, poorly synchronised measurements, or a data format nobody can use afterwards. My job is to catch them early, before they reach the end user.
Real example: automating a power electronics test bench with PAtools.