Testing

Mon, 01 Jan 0001 00:00:00 +0000

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 prove runners — 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.

Talk to us

simon@unisolve.com.au or scottp@dd.com.au

Testing on Fortran 2026

Testing

Where we add value

Talk to us