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

Introduce pytest command as recommended entry point #1633

Merged
merged 2 commits into from Jun 21, 2016

Conversation

Projects
None yet
4 participants
@davehunt
Contributor

davehunt commented Jun 21, 2016

This fixes #1629. We'd like to include a test to ensure backwards compatibility with the py.test command. We were thinking of adding a "py-dot-test" environment to tox.ini that could simply call py.test --version and if that succeeds we assume it's still working. We're interested in hearing any other suggestions.

@coveralls

This comment has been minimized.

coveralls commented Jun 21, 2016

Coverage Status

Coverage remained the same at 92.381% when pulling 393167b on davehunt:issue1629 into 54872e9 on pytest-dev:features.

3 similar comments
@coveralls

This comment has been minimized.

coveralls commented Jun 21, 2016

Coverage Status

Coverage remained the same at 92.381% when pulling 393167b on davehunt:issue1629 into 54872e9 on pytest-dev:features.

@coveralls

This comment has been minimized.

coveralls commented Jun 21, 2016

Coverage Status

Coverage remained the same at 92.381% when pulling 393167b on davehunt:issue1629 into 54872e9 on pytest-dev:features.

@coveralls

This comment has been minimized.

coveralls commented Jun 21, 2016

Coverage Status

Coverage remained the same at 92.381% when pulling 393167b on davehunt:issue1629 into 54872e9 on pytest-dev:features.

@coveralls

This comment has been minimized.

coveralls commented Jun 21, 2016

Coverage Status

Coverage remained the same at 92.381% when pulling 393167b on davehunt:issue1629 into 54872e9 on pytest-dev:features.

@RonnyPfannschmidt

This comment has been minimized.

Member

RonnyPfannschmidt commented Jun 21, 2016

looks great, waiting for the test-case to verify the existence of the entry-points, then it can be merged
another pair of eyes might be a good idea (the content is necessarily massive and repetitive)

@nicoddemus

This comment has been minimized.

Member

nicoddemus commented Jun 21, 2016

Well done! 😁

Tested locally on my laptop since AppVeyor is stuck!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment