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

fix entry point selector pytest_diff_selector.main:run-->pytest_diff_selector.main:main #3

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
32 changes: 32 additions & 0 deletions Readme.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,32 @@
INSTALLING THE TOOL IN THE USER ENVIRONMENT:
Copy link
Owner

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.

Copy link
Author

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


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
5 changes: 5 additions & 0 deletions requierments.txt
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
unidiff
pyan3
tqdm
pytest_git
pytest
2 changes: 1 addition & 1 deletion setup.cfg
Original file line number Diff line number Diff line change
Expand Up @@ -50,7 +50,7 @@ test=pytest

[options.entry_points]
console_scripts =
selector = pytest_diff_selector.main:run
selector = pytest_diff_selector.main:main

[options.extras_require]
test =
Expand Down