-
Notifications
You must be signed in to change notification settings - Fork 1
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
fix entry point selector pytest_diff_selector.main:run-->pytest_diff_selector.main:main #3
Open
amielnoy
wants to merge
1
commit into
fruch:master
Choose a base branch
from
amielnoy:fix_entry_point_to_main
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,32 @@ | ||
INSTALLING THE TOOL IN THE USER ENVIRONMENT: | ||
|
||
pip install pytest-diff-selector | ||
|
||
RUNNING THE TOOL(WINDOWS): | ||
|
||
1.first option: | ||
cd [git-project-you-want-scanning] | ||
selector HEAD^ # scan last commit | ||
tests/test_something.py::test_01 | ||
|
||
2.second option: | ||
selector HEAD # scan unstaged/uncommited work | ||
tests/test_something.py::test_01 | ||
asciicast | ||
|
||
INSTALLING THE DEVELOPMENT ENVIORNMENT: | ||
|
||
pip install -e . | ||
|
||
RUNNING THE TESTS: | ||
|
||
cd pytest-diff-selector | ||
pytest tests | ||
|
||
Why | ||
When having a long integration tests you want your CI extra smarter and don't waste time on irrelevant tests | ||
|
||
How | ||
Figuring out which tests are affect by specific code changes It's scanning all the project python files and build a call graph using AST, and scans this graph to find paths that are part to the change (by line numbers from the diff) that leads to a test | ||
|
||
Currently it's only a commandline tool, but it should become a full fledged pytest plugin |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,5 @@ | ||
unidiff | ||
pyan3 | ||
tqdm | ||
pytest_git | ||
pytest |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like there are two readme files by mistake, can you move those instructions into README.md ?
Also try to stick to the markdown format
https://www.markdownguide.org/cheat-sheet/
Using headings and fenced code blocks
It would be nice that the readme change would be on its own commit, separated for the fix.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK
i will use a separate commit for the README.md
after applying usage and installation directions