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

Refactor navigator testing #1681

Open
ssbarnea opened this issue Feb 12, 2024 · 0 comments
Open

Refactor navigator testing #1681

ssbarnea opened this issue Feb 12, 2024 · 0 comments
Assignees
Labels
bug Researched, reproducible, committed to fix

Comments

@ssbarnea
Copy link
Member

ssbarnea commented Feb 12, 2024

Testing on navigator must be refactored in such way that it will address the following:

  • tests can be run on and pass on both supported platforms
  • regenerating fixtures would not produce different dumps on different machines
  • we can test multiple versions of ansible
  • we can also test ansible-devel (unpinned dependencies!)
  • we would not need different fixtures for each version of ansible
  • the need to regenerate fixtures would be minimized
  • each test must be atomic, and we should be able to run a single test (not a single test file!). The multi step tests are not multiple tests, are in fact just more complex single tests. As a developer, if I do pytest --collect-only I should be able to pick any listed test and run it.
  • Add implicit exports into __init__.py tmux-python/libtmux#531
@ssbarnea ssbarnea added bug Researched, reproducible, committed to fix new New issues and PRs to triaged labels Feb 12, 2024
@Qalthos Qalthos removed the new New issues and PRs to triaged label Feb 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Researched, reproducible, committed to fix
Projects
Status: Roadmap
Development

No branches or pull requests

3 participants