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

Tests contaminated #1112

Open
rvhonorato opened this issue Oct 21, 2024 · 0 comments
Open

Tests contaminated #1112

rvhonorato opened this issue Oct 21, 2024 · 0 comments
Labels
bug Something isn't working CI / repository Continuous integration or repository organization

Comments

@rvhonorato
Copy link
Member

Module/Workflow/Library affected

All tests

Expected behavior

For the tests to be able to be executed in any order

Actual behavior

The order in which the tests are executed affect the results

Steps to reproduce the behavior

Setup:

$ git clone https://github.com/haddocking/haddock3
$ cd haddock3
$ python -m venv .venv
$ source .venv
$ source .venv/bin/activate
$ pip install -e '.[dev]'

This will pass:

$ pytest tests/
$ pytest integration_tests/

This will fail:

$ pytest tests

To make it even more evident;

$ pip install pytest-random-order
$ pytest --random-order

Suggestions on how to fix it

This happens most likely because some of the tests are modifying the test data during its execution - need to identify which one, or which ones are doing that.

Version

ccb3aea581e0a0a930c21f36d135edf1bbdaad06

Additional context

@rvhonorato rvhonorato added bug Something isn't working CI / repository Continuous integration or repository organization labels Oct 21, 2024
@rvhonorato rvhonorato linked a pull request Oct 21, 2024 that will close this issue
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working CI / repository Continuous integration or repository organization
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant