FloPay Backend Changelog

v1.10.38 - Flopay's full pre-merge test run is split into stages that fit build machine time limits #

A maintenance release that splits Flopay's own full backend test run into shorter stages and makes a stage that is stopped say so, with no change to checkout, payments or the public API.

Before a change to Flopay's backend is merged, its full automated test run checks the code, runs every backend unit test and builds the service. On build machines with few processors, running every backend unit test in a single step took longer than the machine lets one step run. The machine then stopped the step and reported a plain failure with no test results, even though no test had failed.

What changed

• The backend unit tests now run as four separate stages, each covering about a quarter of the tests, so each stage takes a fraction of the time the single step did.
• Each stage has its own time limit, set below the build machine's. A stage that runs too long, or that is stopped from outside, now reports that it timed out or was stopped, instead of a plain failure with no output.
• A stage that is stopped now ends together with every process it started.
• What the run checks is unchanged: the same code checks, every backend unit test and the build. The automated checks that run on every change are unchanged too.

Why it matters

• A failed pre-merge test run again points to a real problem in the change, so fixes reach merchants without being held up by failures that came from the build machine's time limit.

Developer notes

• No public API endpoint, request or response field, webhook payload, SDK export, or documented configuration changed.
• No merchant action is required. This release contains no breaking changes.