Testing
Unit, integration, and regression testing for legacy and modern Fortran codebases.
Categories:
A lot of long-running Fortran codebases have no automated tests at all. Every release is “compile, run the smoke script, hope”. We change that — without rewriting the code first.
Where we add value
- Native unit tests in Fortran with TAP-style output and
proverunners — see the worked example at Examples → Unit Tests. - Regression testing by capturing the output of the existing system on real inputs and locking it down before any change is allowed.
- Integration tests across SQL, REST, and external libraries that we have added — see Examples → SQL and Examples → REST API.
- CI pipelines that run the test suite on every change, in containers, before any deploy.
- Test coverage specifically targeting the migration boundary so a 32 → 64-bit cutover is provably safe.