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

[FR] Add integration tests to catch breaking changes in the API #2862

Closed
1 task done
abravalheri opened this issue Nov 8, 2021 · 0 comments · Fixed by #2863
Closed
1 task done

[FR] Add integration tests to catch breaking changes in the API #2862

abravalheri opened this issue Nov 8, 2021 · 0 comments · Fixed by #2863
Labels
enhancement Needs Triage Issues that need to be evaluated for severity and status.

Comments

@abravalheri
Copy link
Contributor

What's the problem this feature will solve?

It would be nice to have integration tests focusing on the usage of setuptools "public API" by some popular packages in the community.

This way we can catch breaking changes in the API before publishing new releases

Describe the solution you'd like

According to the discussion in #2844, if adding a new "integration test suite", the following characteristics are desirable:

  1. It should run separated from the main test suite (integration tests are resource intensive and time consuming, so the best is to avoid always running them and postponing until a new release is ready).
  2. It should test how setuptools' API is being used by popular packages in the community to catch rare errors.

Alternative Solutions

No response

Additional context

No response

Code of Conduct

  • I agree to follow the PSF Code of Conduct
@abravalheri abravalheri added enhancement Needs Triage Issues that need to be evaluated for severity and status. labels Nov 8, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Needs Triage Issues that need to be evaluated for severity and status.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant