mirror of https://github.com/databricks/cli.git
edf37e7d0d
## Changes - New library to patch existing whl with dynamic version. The version is based on mtime of original wheel. - New hidden command "selftest patchwhl" (for acceptance test). ## Why Part of the project to deprecate dynamic version in setup.py template (#1034). This would enable switching default-python to pyproject.toml without dependency on setuptools-specific sections. The dynamic version is needed to ensure that wheels are picked up by the users code when doing development. ## Tests - New unit tests that use uv to create envs on various versions and install (and re-install) patched wheels there. - New acceptance test that patches prebuilt whl and records the result fully unzipped. - New acceptance test helper setmtime.py to set mtime with nanosecond precision cross-platform. |
||
|---|---|---|
| .. | ||
| auth | ||
| bin | ||
| bundle | ||
| cmd | ||
| help | ||
| panic | ||
| selftest | ||
| 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.ymlthere. - Add
scriptwith 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:
errcodehelper: if the command fails with non-zero code, it appendsExit code: Nto the output but returns success to caller (bash), allowing continuation of script.tracehelper: 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.