feat: Update acceptance test report to include changes in WARNINGS.#1354
feat: Update acceptance test report to include changes in WARNINGS.#1354bdferris-v2 merged 9 commits intomasterfrom
Conversation
|
✅ Rule acceptance tests passed. |
|
✅ Rule acceptance tests passed. |
|
Do we need to update https://github.com/MobilityData/gtfs-validator/blob/master/docs/ACCEPTANCE_TESTS.md as a result of this PR? |
…obilityData#1354) * Track changes to warnings in addition to errors in acceptance tests.
Refactor the acceptance test validation report comparison logic to consider changes to WARNING-level notices, not just ERRORs. We could more easily expand this to include INFO-level notices as well, if we so desire. Currently, this change does not cause automatic blocking of a change if the # of warnings changes significantly, but we could change that as well.
As part of this change, I refactored a bunch of logic out of
ValidationReportand moved it into a newNoticeSetto be separate some concerns. I also refactored a bunch of references to "errors" to more generic "notices".Closes #1349.
Please make sure these boxes are checked before submitting your pull request - thanks!
gradle testto make sure you didn't break anything