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

Release Testing #184

jmchilton opened this Issue May 6, 2015 · 2 comments


None yet
2 participants
Copy link

jmchilton commented May 6, 2015

There have been repeated examples with releases which pass tests in repo but have resulted in released artifacts to PyPI to and Homebrew with serious problems.

  • Refactor the CLI integration tests to allow for optional testing against an external planemo command.
  • Extend make release with some real testing. After publishing to test PyPI:
    • Create a temp virtualenv.
    • Install all dependencies
    • Install planemo from test pypi.
    • run release tests.

This comment has been minimized.

Copy link

peterjc commented May 6, 2015

So this is the planemo self-tests which have not caught major problems?


This comment has been minimized.

Copy link
Member Author

jmchilton commented May 6, 2015

Yeah - this is referring to planemo testing itself. The existing tox testing has missed relatively obvious problems such as 563963b ddd1643 5963ed2 (and that is just for the last couple weeks).

jmchilton added a commit that referenced this issue Nov 12, 2015

Add script to test a planemo wheel.
Test wheel directly in isolation by installing it into its own virtualenv and copying test data and required files out into a temp directory.

Progress toward issue #184.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment