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
To tracking UT coverage at daily basis, even commit basis, UT coverage should be integrated into CI pipeline.
An UT fail case report and an UT coverage report in junit xml format will be much helpful.
There are two problems in current ci for unit-test:
Current ci for unit-test print test result to jenkins console, it is not convenient to view failed cases.
Need a better way to display Unit-test coverage and ensure unit-test coverage is not below the baseline.
For the two reasons above, i suggest uniform unit-test and coverage output format(Junit XML).
How to do?
use go-junit-report to convert unit-test output to junit xml file
use gocov and gocov-xml to convert coverage report to junit xml file
What changes did we see after the modification?
A better ci display page for failed unit-test cases
A better ci display page for unit-test coverage detail
The text was updated successfully, but these errors were encountered:
I suggest you just inline the content of that doc in the issue. I don't think it requires a design but we'd better review the items you proposed. Also we can later split subtasks from this issue wrt the items.
Related to PingCAP-QE/devops-config#32
To tracking UT coverage at daily basis, even commit basis, UT coverage should be integrated into CI pipeline.
An UT fail case report and an UT coverage report in junit xml format will be much helpful.
There are two problems in current ci for unit-test:
For the two reasons above, i suggest uniform unit-test and coverage output format(Junit XML).
How to do?
What changes did we see after the modification?
The text was updated successfully, but these errors were encountered: