1a0ea82c34
* remove operationIds from WebBackendConnectionUpdate, just use operations * refactor connection updates to patch-style update, where null fields remain unchanged * better comment and arg name * format * make sure we are still 'dual-writing' to the old schedule column, even when the patch doesn't specify anything for it * update acceptance test to update with new schedule syntax * add catalog sorting to preserve stream order during patch, and more tests * format * add description, throw runtime exception for impossible branches, move streamReset to private helper * PR suggestions * add nested test classes and write a test for the catalog sorting method * format * add comment clarifying that the catalog sort is for UX, and isn't critical * format * format * update acceptance tests to send proper catalog patches instead of whole new catalog * format * format * simplify catalog patching - now, if a catalog is present on the request, replace the entire catalog with it. Otherwise, if catalog on the request is null, leave the catalog unchanged * format * format * Revert "update acceptance tests to send proper catalog patches instead of whole new catalog" This reverts commit 71922648b4e070f46ff6c468813b7ab8dd9d6651. * adjust description
airbyte-tests
This module contains two major test suites:
- Acceptance Tests - These are feature-level tests that run as part of the build. They spin up Airbyte and test functionality by executing commands against the Airbyte Configuration API. It is possible to run them both on
docker-composeandkuberenetes. We do both in the build. These tests are designed to verify that large features work in broad strokes. More detailed testing should happen in unit tests. - Auto Migration Acceptance Tests - These tests verify that it is possible to upgrade from older version of Airbyte (as far back as 0.17.0) all the way up to the current version.