mikebridge opened a new pull request, #45548:
URL: https://github.com/apache/superset/pull/45548

   ### SUMMARY
   The Python unit job currently runs the SQL and semantic-layer unit suites 
twice: once in the parallel full run and again for their 100% coverage gates. 
Reuse the combined `.coverage` file from the full run to check each package's 
statement and branch coverage without repeating those tests. The full-suite 
coverage file remains available for the existing upload, and the main JUnit XML 
contains both suites' test results.
   
   ### BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF
   Not applicable; CI workflow only.
   
   ### TESTING INSTRUCTIONS
   - Run the Python unit job and confirm both scoped `coverage report` commands 
pass at 100% after the parallel pytest step.
   - Confirm the uploaded JUnit artifact and full-suite coverage report are 
still produced.
   - Locally, 4,667 SQL and semantic-layer tests passed with xdist, and both 
scoped reports reached 100% statement and branch coverage. Each report returned 
exit code 2 when an uncovered line was temporarily added to its package; those 
lines were removed.
   
   ### ADDITIONAL INFORMATION
   - [ ] Has associated issue:
   - [ ] Required feature flags:
   - [ ] Changes UI
   - [ ] Includes DB Migration (follow approval process in 
[SIP-59](https://github.com/apache/superset/issues/13351))
     - [ ] Migration is atomic, supports rollback & is backwards-compatible
     - [ ] Confirm DB migration upgrade and downgrade tested
     - [ ] Runtime estimates and downtime expectations provided
   - [ ] Introduces new feature or API
   - [ ] Removes existing feature or API
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to