Jeff Mitchell
c63529e020
Fixing the session passing around its key ID (which had previously been blank) exposed another issue which was caught during bats tests: WithKeyId statements using the wrong key, which prior to now had been ignored because the argument was empty, resulting in an ineffective option. This fixes those situations. It also updates a bats test that didn't get updated in the CLI return status PR.
Boundary CLI Tests
This directory contains bats tests for testing the Boundary CLI against arbitrary Boundary deployments.
The tests are meant to mimic common workflows such as creating resources, and connecting to targets. Currently, the tests rely heavily on
generated resources when running Boundary in dev mode. In the future, we hope to remove this dependency and generate all resources through
the Boundary CLI from the outset.
The tests are designed to be idempotent.
Getting Started
Dependencies
Running Tests
- Start boundary in dev mode
boundary dev
or direct the tests towards an existing install by setting
export BOUNDARY_ADDR=<your_install>
- Run the tests
bats -p boundary/
Running Tests Against Other Deployments
You can run this suite against an arbitrary cluster by overriding the following env vars:
DEFAULT_LOGIN=<my_login> \
DEFAULT_PASSWORD=<my_password> \
BOUNDARY_ADDR=http://boundary-test-controller-salmon-b70f2710539143b4.elb.us-east-1.amazonaws.com:9200 \
bats boundary/
~> Note that these tests currently expect generated resources to exist. Failure to run against a Boundary deployment that does not have generated resources will result in a lot of test failures. Future work includes breaking thses tests out in a way that makes them not dependant on generated resources.