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

[Testing] Speed up Test Suite, Push Code Coverage above 90% #311

Closed
jpmoutinho opened this issue Jan 30, 2024 · 2 comments · Fixed by #626
Closed

[Testing] Speed up Test Suite, Push Code Coverage above 90% #311

jpmoutinho opened this issue Jan 30, 2024 · 2 comments · Fixed by #626
Assignees
Labels
testing Everything related to tests

Comments

@jpmoutinho
Copy link
Collaborator

Main bottlenecks:

  1. not using pytest-xdist (TOP prio which has been investigated by both @seitzdom and @m.dagrada only to result in issues with gitlab runners, this however change when we switch to github)
  2. shadows/tomography
  3. PSR tests in general
  4. PSR tests which compute higher order derivatives
  5. tests which train models (ML tools)
  6. redundant test cases in many mark.parametrize-tests
  7. tests which do exactly the same thing, like in test_quantum_models and test_backends for example (test run,sample, expectation for random circuits)
@jpmoutinho
Copy link
Collaborator Author

@dominikandreasseitz maybe some of the above has already been done, could you check and update? Thanks

@RolandMacDoland RolandMacDoland added the testing Everything related to tests label Apr 5, 2024
@RolandMacDoland RolandMacDoland changed the title Speed up Test Suite, Push Code Coverage above 90% [Testing] Speed up Test Suite, Push Code Coverage above 90% Apr 5, 2024
@RolandMacDoland
Copy link
Collaborator

@dominikandreasseitz @jpmoutinho Is it still relevant ? Some of these tests have move in few other places.

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

Successfully merging a pull request may close this issue.

3 participants