Is your feature request related to a problem? Please describe.
Currently, all pytest tests are executed on every push to every branch. This significantly increases CI runtime and slows down development workflows, especially for smaller changes that don’t require running the full test suite.
Describe the solution you'd like
Introduce selective test execution for regular branch pushes. For example, only a subset of relevant or fast tests should run when pushing to feature or non-critical branches. However, once a pull request is opened, the full test suite should be executed to ensure overall integrity. Additionally, all tests should always run on the dev branch, regardless of how changes are introduced.
Describe alternatives you've considered
Additional context
This change would help speed up development iteration while still maintaining high code quality by enforcing full test coverage at critical stages (pull requests and dev branch).
Is your feature request related to a problem? Please describe.
Currently, all pytest tests are executed on every push to every branch. This significantly increases CI runtime and slows down development workflows, especially for smaller changes that don’t require running the full test suite.
Describe the solution you'd like
Introduce selective test execution for regular branch pushes. For example, only a subset of relevant or fast tests should run when pushing to feature or non-critical branches. However, once a pull request is opened, the full test suite should be executed to ensure overall integrity. Additionally, all tests should always run on the
devbranch, regardless of how changes are introduced.Describe alternatives you've considered
Additional context
This change would help speed up development iteration while still maintaining high code quality by enforcing full test coverage at critical stages (pull requests and
devbranch).