Configuring Thresholds

BlueRacer comes with sane default values for when to scream at you that your Pull Request made the tests too slow. These values can now be customized for each of your repos using a .blueracer.cfg file, like so:

[fail]
# Percentage increase of test suite duration to fail pull request
suite_duration = 30

# Percentage increase of duration per 100 tests to fail pull request
duration_per_100_tests = 20

[warn]
# Percentage increase of test suite duration to raise a warning comment
suite_duration = 10

# Percentage increase of duration per 100 tests to raise a warning comment
duration_per_100_tests = 10

# Percentage increase of number of tests to raise a warning comment
number_of_tests = 10

[comments]
# Update existing comment on reruns instead of posting a new one
update_existing_comment = true

This is useful if you are running self-hosted CI runners where you can better control the hardware variance and have lower variance in tests duration. Or if you have tons of flaky tests in your suite and get too many false positives from BlueRacer!