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

Improve testing harness to separate DB and non-DB tests #35160

Merged
merged 1 commit into from
Oct 31, 2023

Commits on Oct 31, 2023

  1. Improve testing harness to separate DB and non-db test

    This PR marks DB tests as such and allows to split execution
    of the tests in CI to run the DB tests with the various database
    while the non-db tests - without the DB in a separate run.
    
    In order to do that, the code to select which tests to run has been
    moved from `entrypoint_ci.sh` bash to breeze's Python code, which is
    generally much nicer to maintain and common for both "DB" and
    "non-DB" tests.
    
    This will have the nice side effect that it will be easier in the
    future to manage different test types and contain some specific
    flaky test types.
    
    This change also adds possibility to isolate some of the test types
    when parallel DB tests are run and adds new test type
    PythonOperator carved out Operator type. This test is best run in
    isolation becasue creating and destroing virtualenvs in Docker while
    running in parallel to other tests is very slow for some reason and
    leads to flaky tests.
    
    Python operator tests are therefore separated out from Operators and
    treated separately as isolated tests.
    
    This will help not only with speed but also with stability of the
    test suite.
    potiuk committed Oct 31, 2023
    Configuration menu
    Copy the full SHA
    801a808 View commit details
    Browse the repository at this point in the history