Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Publish test results in the AppVeyor UI #221

Merged

Conversation

webknjaz
Copy link
Member

@webknjaz webknjaz commented Jul 27, 2020

This change includes #220 adding one commit on top (see the second commit).

Here's how the tests show up in the AppVeyor UI: https://ci.appveyor.com/project/njsmith/trustme/builds/34322432/job/rygsb2do5tkmtmxc/tests.

@codecov
Copy link

codecov bot commented Jul 27, 2020

Codecov Report

Merging #221 into master will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##            master      #221   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            3         3           
  Lines          385       385           
  Branches        25        25           
=========================================
  Hits           385       385           

@webknjaz
Copy link
Member Author

@pquentin mind approving?

@pquentin
Copy link
Member

@webknjaz, sure, but can you only include the second commit to avoid blocking this on #220?

@webknjaz
Copy link
Member Author

@pquentin the second commit relies on the first one producing the JUnit XML report...

@webknjaz webknjaz force-pushed the testing/appveyor-tests-reporting branch from 64acb72 to 8a2966c Compare July 27, 2020 21:41
@webknjaz
Copy link
Member Author

@pquentin done!

Copy link
Member

@pquentin pquentin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! Nice UI

@pquentin pquentin merged commit 6691656 into python-trio:master Jul 29, 2020
@webknjaz
Copy link
Member Author

Oh... I forgot to pin the family to xunit1 when rebasing because it was in a separate commit with the config. The recent pytest switches to xunit2 that lacks filenames in the output: pytest-dev/pytest#7537 (comment).

(Still works but not as good)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants