Reduce the number of passthroughs used for tests related to the query engine

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Query Optimization
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Currently, most of query-related tests run against all or most passthroughs, including many that are entirely irrelevant to the task at hand.

      Just as a simple example, tests in ./core/query/array/ run against clustering-related passthroughs, including those that inject cluster failures.

      While initially running all tests against all passthroughs provided additional coverage, it is difficult to find a point of intersection between MQL array processing and cluster leader election.

       

      Unfortunately, the current passthrough mechanism is mostly geared towards specifying which tests to exclude in a passthrough rather than which tests to include. Therefore, I (Philip) suspect that a large-scale test movement and YAML surgery will be required to properly align tests and passthroughs. Even more so if we want to keep some passthroughs but run them at a lower frequency against query-related tests (and run them with their original frequency against the tests where they would be most useful).

            Assignee:
            Unassigned
            Reporter:
            Philip Stoev
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: