mirror of https://github.com/databricks/cli.git
This is a follow up to #2471 where incorrect config was used in interactive_cluster test. ## Changes - Fixed interactive_cluster to use proper config, it was accidentally referring to config from ../base - Add $NODE_TYPE_ID env var and replacement to acceptance tests, this is necessary for interactive_cluster test. - Disable acceptance/bundle/override on cloud. This started failing because it has real node type that gets replaced with NODE_TYPE_ID but only in AWS env. Since the test is focussed on config merging, there is no need to run it against real workspaces. - Modify all tests in integration_whl to print rendered databricks.yml, to prevent this kind of error. |
||
---|---|---|
.. | ||
auth | ||
bin | ||
bundle | ||
cmd | ||
help | ||
panic | ||
selftest | ||
telemetry | ||
terraform | ||
workspace/jobs | ||
.gitignore | ||
README.md | ||
acceptance_test.go | ||
cmd_server_test.go | ||
config_test.go | ||
install_terraform.py | ||
script.cleanup | ||
script.prepare | ||
server_test.go | ||
test.toml |
README.md
Acceptance tests are blackbox tests that are run against compiled binary.
Currently these tests are run against "fake" HTTP server pretending to be Databricks API. However, they will be extended to run against real environment as regular integration tests.
To author a test,
- Add a new directory under
acceptance
. Any level of nesting is supported. - Add
databricks.yml
there. - Add
script
with commands to run, e.g.$CLI bundle validate
. The test case is recognized by presence ofscript
.
The test runner will run script and capture output and compare it with output.txt
file in the same directory.
In order to write output.txt
for the first time or overwrite it with the current output pass -update flag to go test.
The scripts are run with bash -e
so any errors will be propagated. They are captured in output.txt
by appending Exit code: N
line at the end.
For more complex tests one can also use:
errcode
helper: if the command fails with non-zero code, it appendsExit code: N
to the output but returns success to caller (bash), allowing continuation of script.trace
helper: prints the arguments before executing the command.- custom output files: redirect output to custom file (it must start with
out
), e.g.$CLI bundle validate > out.txt 2> out.error.txt
.
See selftest for a toy test.