Ensure ucacct tests are marked as integration tests #934
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What changes are proposed in this pull request?
Integration tests for the Python SDK are run once for each environment (a grid covering cloud, account/workspace, and with or without UC). All tests are executed by the test runner in each environment, even though most tests only work in a specific context (e.g. you can't run a test that depends on a catalog in a workspace with no catalog).
Each test uses pytest fixtures to express its dependencies. One of these is the Databricks client to use for the test. There are four options, depending on whether the test is meant to be run at the workspace/account level and with or without UC:
wfor workspace-level without UC,ucwsfor workspace-level with UC,afor account-level without UC, anducacctfor account-level with UC. Any test that uses these clients in thetests/integrationdirectory will have a marker calledintegrationautomatically added to it.make integrationruns these tests.However, currently, tests using the
ucacctclient are skipped. In this case, this is happening by pytest itself because these tests are not annotated with theintegrationmarker. This is fixed by addingucacctto the list of fixtures whose presence indicates that they are integration tests.How is this tested?
NO_CHANGELOG=true