-
Notifications
You must be signed in to change notification settings - Fork 2
Streamline Automatic Tests #604
Copy link
Copy link
Labels
Priority/1-MediumTo do after P0To do after P0Size/DaysSome days of workSome days of workStatus/ReadyForDevThe issue is ready to be developed or to be investigated deeplyThe issue is ready to be developed or to be investigated deeply
Description
Activity
Metadata
Metadata
Assignees
Labels
Priority/1-MediumTo do after P0To do after P0Size/DaysSome days of workSome days of workStatus/ReadyForDevThe issue is ready to be developed or to be investigated deeplyThe issue is ready to be developed or to be investigated deeply
Discard parallel tests, no longer relevant after the resource manager has been removed.
Group integration tests and remote-access tests into a separate, "integration-tests.yml", workflow that can only be launched manually.
Limit the number of Python versions to test: keep only the oldest (currently 3.10) and the newest (currently 3.14).
Consider what to do with the samples tests:
If the last solution is chosen, then discard the "expensive tests" distinction (workflow input, Python decorator).
For this to work, also group all integration tests in a separate Python module, in separate
unittest.TestCaseclasses. Thus, the Python library-only tests should be better separable from integration tests through adequatepython -m unittestinvocations.The goal of this is to only test the Python library in "tests.yml", using fixtures and Khiops core mocks. All other tests, that do not do so, should be moved to the "integration-tests.yml" workflow.