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

[CHORE] add pytest to vscode settings.json #2930

Merged
merged 1 commit into from
Sep 26, 2024
Merged

Conversation

andrewgazelka
Copy link
Member

No description provided.

@github-actions github-actions bot added the chore label Sep 25, 2024
Copy link

codspeed-hq bot commented Sep 25, 2024

CodSpeed Performance Report

Merging #2930 will not alter performance

Comparing andrew/vscode-pytest (1e07011) with main (6460a0e)

Summary

✅ 17 untouched benchmarks

Copy link

codecov bot commented Sep 25, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 78.37%. Comparing base (6460a0e) to head (1e07011).
Report is 5 commits behind head on main.

Additional details and impacted files

Impacted file tree graph

@@            Coverage Diff             @@
##             main    #2930      +/-   ##
==========================================
- Coverage   78.38%   78.37%   -0.01%     
==========================================
  Files         596      596              
  Lines       69685    69685              
==========================================
- Hits        54625    54619       -6     
- Misses      15060    15066       +6     
Flag Coverage Δ
78.37% <ø> (-0.01%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

see 2 files with indirect coverage changes

@andrewgazelka andrewgazelka merged commit a5cb55d into main Sep 26, 2024
40 checks passed
@andrewgazelka andrewgazelka deleted the andrew/vscode-pytest branch September 26, 2024 01:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants