Skip to content
This repository has been archived by the owner on May 20, 2021. It is now read-only.

Actual test plan #2

Open
xavfernandez opened this issue Jan 31, 2019 · 2 comments
Open

Actual test plan #2

xavfernandez opened this issue Jan 31, 2019 · 2 comments

Comments

@xavfernandez
Copy link
Member

From the Discuss, here is what I understood the tests could look like:

  • Prepare the artefacts:
    for all the packaging bricks: pip, setuptools, etc:
    • download the latest stable wheel release from PyPI
    • build a wheel from their development branch
  • For each brick A, the test would be:
    • launch a local PyPI exposing A master wheel + the stable wheels of the other bricks
    • create a virtualenv and install the different bricks
    • try to install a curated list of packages ? Maybe https://pypistats.org/top ?

What are the bricks we want to test ?
pip, setuptools, pep517, wheel, virtualenv, tox, (should we also include their dependencies ? like pytoml for pep517, etc).

@gaborbernat
Copy link
Contributor

gaborbernat commented Feb 1, 2019

Pushed on master provisioning the wheels into a devpi server. On my fork, I've started creating some tests for virtualenv.

@brainwane
Copy link

This could be something that one of the paid contractors on pip works on.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants