Introduce manual SEA test scripts for Exec Phase

[varun-edachali-dbx]

What type of PR is this?

• Other - test scripts for eventual feature

Description

For the SEA implementation, before we introduce e2e tests, we introduce manual testing scripts which allow us to execute queries against a real warehouse as an implementation sanity check.

The tests are structured as follows:

sea_connector_test.py
│
├─ test_sea_session.py - tests basic session opening and closure 
│
├─ test_sea_sync_query.py - tests synchronous query execution 
│  ├─ test_sea_sync_query_with_cloud_fetch()    [use_cloud_fetch=True]
│  └─ test_sea_sync_query_without_cloud_fetch() [use_cloud_fetch=False]
│
├─ test_sea_async_query.py - tests async query execution 
│  ├─ test_sea_async_query_with_cloud_fetch()    [use_cloud_fetch=True]
│  └─ test_sea_async_query_without_cloud_fetch() [use_cloud_fetch=False]
│
└─ test_sea_metadata.py - tests metadata commands

This allows us to experiment with metadata queries, session opening and closure, synchronous queries (INLINE as well as EXTERNAL_LINKS) and async queries (INLINE as well as EXTERNAL_LINKS).

How is this tested?

• Unit tests
• E2E Tests
• Manually
• N/A

Related Tickets & Documents

https://docs.google.com/document/d/1Y-eXLhNqqhrMVGnOlG8sdFrCxBTN1GdQvuKG4IfHmo0/edit?usp=sharing

[samikshya-db]

Just to confirm : these tests will be replaced by the E2E tests in the future, right?

[varun-edachali-dbx]

Just to confirm : these tests will be replaced by the E2E tests in the future, right?

Yes, that's right. These scripts allow me to test the functionality against an actual warehouse before the e2e tests, which we will introduce after implementing the functionality completely.

[jayantsing-db]

hey, why are e2e tests failing on this PR?

[varun-edachali-dbx]

hey, why are e2e tests failing on this PR?

Likely flaky tests since this PR doesn't affect any code paths that the integration tests should be running. I'll let them run once again before merging.

Edit: the tests are passing