steve/databricks-cli
steve
/
databricks-cli
mirror of https://github.com/databricks/cli.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
databricks-cli/acceptance
History
Denis Bilenko d53a78e926
Introduce $DATABRICKS_URL replacement in tests (#2158) 
## Changes
It covers both https://$DATABRICKS_HOST and http://$DATABRICKS_HOST so
the test output does not change between local and the cloud.

## Tests
Existing tests using golden files (acceptance and integration) catch
this and were updated.
 		2025-01-15 17:24:12 +01:00
..
bin Migrate bundle/tests/undefined_resources_test.go to acceptance test (#2106) 2025-01-09 15:21:24 +00:00
build Add acceptance tests (#2081) 2025-01-08 12:41:08 +00:00
bundle Introduce $DATABRICKS_URL replacement in tests (#2158) 2025-01-15 17:24:12 +01:00
help Add acceptance tests (#2081) 2025-01-08 12:41:08 +00:00
README.md Use -update instead of TESTS_OUTPUT=OVERWRITE (#2097) 2025-01-09 09:00:05 +00:00
acceptance_test.go Use regular expressions for testdiff replacements (#2151) 2025-01-15 12:15:23 +01:00
script.cleanup Add acceptance tests (#2081) 2025-01-08 12:41:08 +00:00
script.prepare Add test about using variable in bundle.git.branch (#2118) 2025-01-15 10:34:51 +01:00
server_test.go Add acceptance tests for builtin templates (#2135) 2025-01-14 18:23:34 +00:00

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 of script.

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 appends Exit 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.