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

Allow more control over tox Selenium tests #1897

Merged
merged 1 commit into from
Mar 18, 2024

Conversation

living180
Copy link
Contributor

Description

This is a follow-up to #1892.

Instead of unconditionally enabling Selenium tests for the py311-dj42-postgresql tox environment, enable them by default for that environment but allow them to be disabled if the user's DJANGO_SELENIUM_TESTS environment variable is empty. This will allow the user to run

DJANGO_SELENIUM_TESTS= tox

to run the full tox test suite with Selenium tests disabled.

Checklist:

  • I have added the relevant tests for this change.
  • I have added an item to the Pending section of docs/changes.rst.

Instead of unconditionally enabling Selenium tests for the
py311-dj42-postgresql tox environment, enable them by default for that
environment but allow them to be disabled if the user's
DJANGO_SELENIUM_TESTS environment variable is empty.  This will allow
the user to run

    DJANGO_SELENIUM_TESTS= tox

to run the full tox test suite with Selenium tests disabled.
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

Successfully merging this pull request may close these issues.

2 participants