You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Parse XCTest output anywhere in output lines (#1511)
Sometimes when running tests that print user output during their
execution this output can be printed on the same line as XCTest results
output, either before or after the results string. Previously this
showed as a test that never finished (pending) in then test explorer,
but with the introduction of #1505 tests that start but don't find any
completion output are assumed to be crashed and marked as failed.
This extra user output interleaved with XCTest output would cause false
positives, leading users to believe that their test never completed
(crashed) when really we just missed the success/failure message from
XCTest due to overly strict parsing.
Relax the XCTest output parsing regexes so that matched strings don't
need to be at the start of a line.
0 commit comments