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.

Sign up for GitHub

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

Jump to bottom

Setting python.testing.pytestArgs not used #24168

Closed
bpasero opened this issue Sep 24, 2024 · 0 comments · Fixed by #24225
Closed

Setting python.testing.pytestArgs not used #24168

bpasero opened this issue Sep 24, 2024 · 0 comments · Fixed by #24225
Assignees
@eleanorjboyd
Labels
triage-needed Needs assignment to the proper sub-team

Comments

@bpasero
Copy link
Member

bpasero commented Sep 24, 2024 •
edited
Loading

Testing #24156

I was not able to get a coverage report. When I configured the setting according to TPI and run the test again with coverage, I did not see a coverage JSON file in the root dir.
@github-actions github-actions bot added the triage-needed Needs assignment to the proper sub-team label Sep 24, 2024
@eleanorjboyd eleanorjboyd mentioned this issue Oct 2, 2024
Merged
eleanorjboyd added a commit that referenced this issue Oct 2, 2024
@eleanorjboyd
support setting only --cov-report arg (#24225)
3e7d8e1 
fixes #24168. We should
support `--cov-report=` set without the need to set `--cov=` since the
default (`--cov=.`) will work for many users
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@eleanorjboyd eleanorjboyd

Labels
triage-needed Needs assignment to the proper sub-team
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

support setting only --cov-report arg eleanorjboyd/vscode-python
2 participants
@bpasero @eleanorjboyd