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

Limit coverage and sqlite tests to a subset of test targets #382

Open
zerolab opened this issue Jan 18, 2024 · 0 comments
Open

Limit coverage and sqlite tests to a subset of test targets #382

zerolab opened this issue Jan 18, 2024 · 0 comments

Comments

@zerolab
Copy link
Member

zerolab commented Jan 18, 2024

As per https://drive.google.com/file/d/1Ks5_RrT_J64hOtGsRK3MMdovM_otvxDR/view?usp=sharing

it makes sense to limit coverage to a couple of full tox targets (e.g. py311-wagtail5.2-django-4.2-{sqlite,postgres}, as well we only run the sqlite tests for the same target. This should provide enough assurance and coverage, while limiting resource waste/carbon footprint

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

No branches or pull requests

1 participant