Replies: 1 comment
-
|
Hi @ifeify,
That's strange, it should just run all tests and report failures. Are you passing
I don't think so, I would run pytest twice, once for |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
For example, if I have the following repo structure:
Is there a way to tell
xdistto run tests frompkg1on the local host and tests frompkg2on a remote host? The problem I'm trying to solve ispkg2is apysparkapplication and the tests need to run in a glue docker container.pkg1, on the other hand, has no special requirements and can run locally. I want to usepytest-covalong withpytest-xdistso I can get the coverage report for both packages at once. The idea is the glue container will act as the remote host and be ssh-able forxdist.For additional context, for
pkg2, I'm currently usingcoveragetool but I mount the source repo as a volume in the glue docker container. This way, I can grab the.coveragefile and combine it with the coverage file frompkg1to get the full report afterpytestruns. The problem here iscoverage run pyteststops after the first unit test failure and I don't get a full report.pytest-covplugin solves this issue for me and I get a full coverage report regardless of a failing unit test. Just need to make it work withxdistso I can test thepysparkapplication also.Thanks. Looking forward to hearing back.
Beta Was this translation helpful? Give feedback.
All reactions