Welcome to PragmaTest

You're in the middle of re-running a faulty unit through production test because there wasn't a clear answer in the data. Your latest hire knows Python from school and your professional networks have turned into a non-stop advertisement for AI productivity gains. Your software subscriptions cost more every year and you're stuck wondering if you're still getting enough value. Do you adopt Python? Do you build or buy a test framework? How do you integrate with your company's existing data platform? Where can AI actually improve your test processes? The pragmatic answer is to keep what works and add new tools where they earn their keep. This is why PragmaTest exists.

My career has lived at the crossroads between the software and Test & Measurement industries. I have seen many different answers to the questions above across companies and test phases in the electronics, mil/aero, automotive, semiconductor, and academic sectors. There are common themes that can be addressed by taking a page from the last decades of software practices and capabilities such as cross-phase reuse, code development and review, data standards and platforms, and bridging interactive and automated workflows. PragmaTest seeks to identify software designs, best practices, and processes, and apply them to the persistent problems of Test & Measurement automation. Sometimes that will take the form of information sharing and sometimes it will be through sharing software tools.

If that sounds like your cup of tea, welcome to PragmaTest.