[ 
https://issues.apache.org/jira/browse/DISPATCH-1933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18018487#comment-18018487
 ] 

ASF GitHub Bot commented on DISPATCH-1933:
------------------------------------------

codecov-commenter commented on PR #1102:
URL: https://github.com/apache/qpid-dispatch/pull/1102#issuecomment-3259778576

   ## 
[Codecov](https://app.codecov.io/gh/apache/qpid-dispatch/pull/1102?dropdown=coverage&src=pr&el=h1&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache)
 Report
   :white_check_mark: All modified and coverable lines are covered by tests.
   :white_check_mark: Project coverage is 84.21%. Comparing base 
([`b919a63`](https://app.codecov.io/gh/apache/qpid-dispatch/commit/b919a638e75ce42b0561b70671127b4e51f95d28?dropdown=coverage&el=desc&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache))
 to head 
([`d57ce8f`](https://app.codecov.io/gh/apache/qpid-dispatch/commit/d57ce8f5d373d87282f135ad206e326ada98b743?dropdown=coverage&el=desc&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache)).
   :warning: Report is 352 commits behind head on main.
   
   <details><summary>Additional details and impacted files</summary>
   
   
   
   ```diff
   @@            Coverage Diff             @@
   ##             main    #1102      +/-   ##
   ==========================================
   - Coverage   84.22%   84.21%   -0.02%     
   ==========================================
     Files         111      111              
     Lines       27569    27569              
   ==========================================
   - Hits        23220    23216       -4     
   - Misses       4349     4353       +4     
   ```
   </details>
   
   [:umbrella: View full report in Codecov by 
Sentry](https://app.codecov.io/gh/apache/qpid-dispatch/pull/1102?dropdown=coverage&src=pr&el=continue&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache).
   
   :loudspeaker: Have feedback on the report? [Share it 
here](https://about.codecov.io/codecov-pr-comment-feedback/?utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache).
   <details><summary> :rocket: New features to boost your workflow: </summary>
   
   - :snowflake: [Test 
Analytics](https://docs.codecov.com/docs/test-analytics): Detect flaky tests, 
report on failures, and find test suite problems.
   - :package: [JS Bundle 
Analysis](https://docs.codecov.com/docs/javascript-bundle-analysis): Save 
yourself from yourself by tracking and limiting bundle sizes in JS merges.
   </details>




> Tests should produce JUnit-compatible XML report about individual tests (not 
> aggregated CTest test targets)
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: DISPATCH-1933
>                 URL: https://issues.apache.org/jira/browse/DISPATCH-1933
>             Project: Qpid Dispatch
>          Issue Type: Improvement
>          Components: Tests
>    Affects Versions: 1.14.0
>            Reporter: Jiri Daněk
>            Assignee: Jiri Daněk
>            Priority: Major
>             Fix For: 1.16.0
>
>
> We can use either {{unittest-xml-reporting}} or {{pytest}} as a dependency to 
> run the system-tests and obtain such XML report.
> We can modify the way tests are executed from {{run.py python -m unittest}} 
> to {{run.py python -m xmlrunner}} (or {{python -m pytest 
> --junitxml=path-to.xml}}) and it will generate the report. Each system-test 
> must produce differently-named report, to avoid overwriting.
> I prefer pytest for this (it is compatible with unittest tests), but I don't 
> mind using xmlrunner if there are any obvious advantages (like not having to 
> configure path to destination file?
> * https://pypi.org/project/unittest-xml-reporting/
> * https://docs.pytest.org/en/stable/usage.html#creating-junitxml-format-files
> CC [~fgiorget], thanks for describing how to do this with {{xmlrunner}}. 
> https://github.com/apache/qpid-dispatch/pull/944#issuecomment-768275130
> For unittests, the doctest framework can produce xml output. The bespoke test 
> macros used in the remainder of unittests cannot. These tests can be migrated 
> to doctest, or maybe simply ignored for now, because they always run anyways, 
> AFAIK there is no skipping.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

Reply via email to