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

Individual tests cases should be self contained #2394

Open
389-ds-bot opened this issue Sep 13, 2020 · 2 comments
Open

Individual tests cases should be self contained #2394

389-ds-bot opened this issue Sep 13, 2020 · 2 comments
Labels
CI test Involves lib389 CI test
Milestone

Comments

@389-ds-bot
Copy link

Cloned from Pagure issue: https://pagure.io/389-ds-base/issue/49335


Some of the tests in tickets are not self contained, meaning that they require some specific setup to be executed. Generally it is solved by using pytest fixture, but not all our code uses that.

Why it's needed? Py.test allows execution in parallel using pytest-xdist. It distributes the tests across workers simply sending each test case to a different worker. When using pytest-xdist, many test cases fail in current state.

This effort can be combined with moving tests from tickets to suites. To preserve the relation between the test and the issue in pagure we can use pytest marks.

@389-ds-bot 389-ds-bot added this to the CI test 1.0 milestone Sep 13, 2020
@389-ds-bot
Copy link
Author

Comment from vashirov (@vashirov) at 2017-07-28 14:40:09

Metadata Update from @vashirov:

  • Custom field component adjusted to None
  • Custom field origin adjusted to None
  • Custom field reviewstatus adjusted to None
  • Custom field type adjusted to None
  • Custom field version adjusted to None
  • Issue priority set to: normal
  • Issue set to the milestone: CI test FUTURE

@389-ds-bot
Copy link
Author

Comment from vashirov (@vashirov) at 2020-02-12 17:53:33

Metadata Update from @vashirov:

  • Issue set to the milestone: CI test 1.0 (was: CI test FUTURE)

@droideck droideck added the CI test Involves lib389 CI test label Feb 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CI test Involves lib389 CI test
Projects
None yet
Development

No branches or pull requests

2 participants