Created the new CIRecordHelper behaviour and an associate rake task:
Recording the deprecations whitelist for thousands of tests is a
real pain depending on how your CI is setup.
Most CI runs test in parallel in different machines, the regular
Record Behaviour from this gem will create bunch of YAML files,
but since multiple test from the same test file runs on different
machines, you end up with multiple yaml files for the same test
suite. You'd need a way to download all artifacts from CI and
"merge" all files, it's a nightmare.
This PR introduce a new behaviour that leverage a feature that most
CI have which is to download the log output from the test run.
The CIRecordHelper behaviour will output a JSON representation of
your deprecations. You'll simply have to download the log output
locally and finally run the associate rake task meant to parse this
log file and generate proper deprecation as YAML file.
Created the new
CIRecordHelperbehaviour and an associate rake task:Recording the deprecations whitelist for thousands of tests is a real pain depending on how your CI is setup.
Most CI runs test in parallel in different machines, the regular
RecordBehaviour from this gem will create bunch of YAML files, but since multiple test from the same test file runs on different machines, you end up with multiple yaml files for the same test suite. You'd need a way to download all artifacts from CI and "merge" all files, it's a nightmare.This PR introduce a new behaviour that leverage a feature that most CI have which is to download the log output from the test run. The
CIRecordHelperbehaviour will output a JSON representation of your deprecations. You'll simply have to download the log output locally and finally run the associate rake task meant to parse this log file and generate proper deprecation as YAML file.