Is this a new feature, an improvement, or a change to existing functionality?
Improvement
How would you describe the priority of this feature request
Low (would be nice)
Please provide a clear description of problem this feature solves
Though good coverage is a great asset in providing accurate results to our end users, our python test suite is currently too large and some of those tests are redundant. This is cumbersome for CI having to go through all these tests before a PR can be merged. An alternative would be split our CI tests from our nightly ones where in he former, a minimal subset of the tests is run whereas in the latter can cover the full suite. In a similar fashion as our C++ tests, we can have flags differentiating the size of the test suite being run (low, medium, high)
Describe your ideal solution
Split the CI tests from the nightly ones
Describe any alternatives you have considered
No response
Additional context
No response
Code of Conduct
Is this a new feature, an improvement, or a change to existing functionality?
Improvement
How would you describe the priority of this feature request
Low (would be nice)
Please provide a clear description of problem this feature solves
Though good coverage is a great asset in providing accurate results to our end users, our python test suite is currently too large and some of those tests are redundant. This is cumbersome for CI having to go through all these tests before a PR can be merged. An alternative would be split our CI tests from our nightly ones where in he former, a minimal subset of the tests is run whereas in the latter can cover the full suite. In a similar fashion as our C++ tests, we can have flags differentiating the size of the test suite being run (low, medium, high)
Describe your ideal solution
Split the CI tests from the nightly ones
Describe any alternatives you have considered
No response
Additional context
No response
Code of Conduct