Conversation
Matches the explicit pytest install in test_dev / test_stable workflows. Neither requirements.txt nor dev_requirements.txt lists pytest, so the e2e job hit ModuleNotFoundError when invoking python -m pytest.
Up to standards ✅🟢 Issues
|
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The E2E browser workflow installs
dev_requirements.txtbut neitherthat file nor
requirements.txtlists pytest, sopython -m pytest test/e2e_test/ -m e2e -vaborted withNo module named pytestonthe GitHub-hosted runner. Add an explicit
pip install pyteststep,matching the pattern already used in
test_dev.yml/test_stable.yml.Test plan
E2E Browser Smokevia workflow_dispatch and confirmpytest resolves