Document paths limit of cobertura report parsing
The following discussion from !48048 (merged) should be addressed:
-
@morefice started a discussion: question: Should we set a tracking event here in case the limit has been reached?
Question
Do we find value in tracking this? Do we intend to track each time a certain limit is reached? Or should we sometimes rely on user feedback in some cases like this?
Answer - No.
As discussed instead the limit of 100 should be documented.
Proposal
Add to the docs about test coverage visualization that a limit of 100 source nodes is enforced and that some test coverage may be missing if more than 100 source nodes are contained in a cobertura file(s) being uploaded as part of an MR.
Edited by James Heimbuck