[
https://issues.apache.org/jira/browse/DISPATCH-1933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17275648#comment-17275648
]
Jiri Daněk edited comment on DISPATCH-1933 at 4/3/21, 7:45 PM:
---------------------------------------------------------------
doctest cannot output both to console and to a file
([issue#338|https://github.com/onqtam/doctest/issues/338]). Not a huge problem,
but annoying.
was (Author: jdanek):
doctest cannot output both to console and to a file
([issue#338|https://github.com/onqtam/doctest/issues/338]. Not a huge problem,
but annoying.
> 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
> 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.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
