v4.4.20

Release notes

Changes

• TFCPS_CodeUnitSpecific_Flutter_Functions.run_testcases now executes the testcases of a flutter-codeunit one after the other (flutter test --coverage --concurrency=1) instead of one test-file per processor-core. The coverage which flutter collects while several test-files run at the same time is not reproducible: it attaches to the vm-service of every test-isolate, and under load a library which was loaded by another isolate is sometimes counted and sometimes not. The very same code produced 91.14, 91.14 and 90.58 percent in three runs before this change and produces exactly 90.30 percent in every run after it. A coverage-value which changes without the code changing makes the coverage-badge of a codeunit differ after every build (so scbuildcodeunits -u can never succeed) and can push a codeunit below its minimal-coverage-threshold by chance; the serial run is slower, which is the price for a value which can be compared at all.