Deduce offending code from failed spec and coverage analysis
(Include problem, use cases, benefits, and/or goals)
When a test fails, we know what code has changed in the MR, and what code the test covers from coverage analysis. Would it be valuable to intersect those to things and give the developer a hint as to which lines of code might be causing the error?
Links / references
What is it? Why should someone use this feature? What is the underlying (business) problem? How do you use this feature?
Who is this for? Provide one or more use cases.
Make sure these are completed before closing the issue, with a link to the relevant commit.