github.com/liamawhite/cli-with-i18n@v6.32.1-0.20171122084555-dede0a5c3448+incompatible/integration/README.md (about)

     1  # CLI Integration Tests
     2  These are high-level tests for the CLI that make assertions about the behavior of the `cf` binary.
     3  
     4  These tests require that a `cf` binary built from the latest source is available in your `PATH`.
     5  
     6  ## How to run:
     7  These tests rely on [ginkgo](https://github.com/onsi/ginkgo) to be installed. Currently there are three suites of functionality, `isolated`, `global`, and `plugin`. The `isolated` suite can run it's tests in parallel, while the `global` and `plugin` suites cannot.
     8  
     9  Run command for the `isolated` suite:
    10  ```
    11  ginkgo -p -r -randomizeAllSpecs -slowSpecThreshold=120 integration/isolated
    12  ```
    13  
    14  Run command for the `global` and `plugin` suites:
    15  ```
    16  ginkgo -r -randomizeAllSpecs -slowSpecThreshold=120 integration/isolated integration/plugin
    17  ```
    18  
    19  ### Customizations (based on environment variables):
    20  
    21  - `CF_API` - Sets the CF API URL these tests will be using. Will default to `api.bosh-lite.com` if not set.
    22  - `SKIP_SSL_VALIDATION` - If true, will skip SSL Validation. Will default `--skip-ssl-validation` if not set.
    23  - `CF_USERNAME` - The CF Administrator username. Will default to `admin` if not set.
    24  - `CF_PASSWORD` - The CF Administrator password. Will default to `admin` if not set.
    25  - `CF_INT_DOCKER_IMAGE` - A private docker image used for the docker authentication tests.
    26  - `CF_INT_DOCKER_USERNAME` - The username for the private docker registry for `CF_INT_DOCKER_IMAGE`.
    27  - `CF_INT_DOCKER_PASSWORD` - The password for `CF_INT_DOCKER_USERNAME`.
    28  - `CF_CLI_EXPERIMENTAL` - Will enable both experimental functionality of the CF CLI and tests for that functionality. Will default to `false` if not set.
    29  
    30  ### The test suite does not cleanup after itself!
    31  In order to focus on clean test code and performance of each test, we have decided to not cleanup after each test. However, in order to facilitate [clean up scripts](https://github.com/cloudfoundry/cli/blob/master/bin/cleanup-integration), we are trying to keep consistent naming across organizations, spaces, etc.