The previous approach resulted in rare false positives. For example, this run: ``` Coverage report generated for 11 to /home/jeremy/code/ubicloud/coverage. Line Coverage: 48.18% (3951 / 8200) Branch Coverage: 21.42% (467 / 2180) ............................................................................................................................................Coverage report generated for 11, 13 to /home/jeremy/code/ubicloud/coverage. Line Coverage: 59.71% (4896 / 8200) Branch Coverage: 37.48% (817 / 2180) Coverage report generated for 11, 13, 16 to /home/jeremy/code/ubicloud/coverage. Line Coverage: 71.06% (5827 / 8200) Branch Coverage: 56.61% (1234 / 2180) Coverage report generated for 11, 13, 14, 15, 16 to /home/jeremy/code/ubicloud/coverage. Line Coverage: 90.32% (7406 / 8200) Branch Coverage: 84.59% (1844 / 2180) Coverage report generated for 11, 12, 13, 14, 15, 16 to /home/jeremy/code/ubicloud/coverage. Line Coverage: 100.0% (8200 / 8200) Branch Coverage: 100.0% (2180 / 2180) Coverage report generated for 11, 13, 14, 15, 16 to /home/jeremy/code/ubicloud/coverage. Line Coverage: 90.32% (7406 / 8200) Branch Coverage: 84.59% (1844 / 2180) ``` Note how the 100% coverage lines are present, but they aren't the final lines. This seems like a bug in simplecov's coverage merging, but this changes the approach to write the turbo_tests command output to a file, and then check for the "Line Coverage: 100.0%" and "Branch Coverage: 100.0%" in that file.
9.4 KiB
9.4 KiB