Open rbontrager opened 3 weeks ago
Planning on running a variety of detox-to-testrail runs against this branch, and one of them will eventually hit these circumstances. There's probably some upper limit on this (where, if I haven't had a fail outside of the e2e yet, I'll pass it anyways) but I don't think it'll actually come to that.
Proposed Change
If the detox run fails outside of the e2e test runs, no junit.xml is created and thus nothing is put into the test run for that test. This can cause confusion if it occurs when code reviewing a PR and make people believe that something is wrong with the PR (when it isn't). We should be able to add the ability to grab all tests the user wanted to be run, compare it to what is in the current test run and put any tests that aren't there as retest with a note saying that github actions has failed. This will hopefully remove some confusion.