Skip to content

Running SCF tests

Andreas Kupries edited this page Apr 8, 2020 · 7 revisions

Running Tests

You can also run smoke and cats tests against an already running cluster with SCF deployed (specify with CLUSTER_NAME):

Running in a Kube pod

SCF smokes

$> [..] make tests-smoke-scf

Cats

$> [..] make tests-kubecats

Smokes

$> [..] make tests-smoke-kube

BRATs

$> [..] BRATS_BUILDPACK=nodejs \
        BRATS_BUILDPACK_URL=https://...zip \
        BRATS_BUILDPACK_VERSION=1.11 \
        make tests-brats

Locally

Smoke

$> [..] make tests-smoke

CATs

$> [..] make tests-cats

If what you really want is just running tests, you can also chain the make target ( e.g. make all tests-smoke tests-cats).

Note: You need go installed to run smoke and cats tests

KubeCF

There is a target to run tests from the instance groups deployed within the chart:

$> [..] make tests-kubecf

Additional parameters:

  • KUBECF_NAMESPACE: Kubecf namespace (Defaults to scf).

  • KUBECF_TEST_SUITE: Test suite to trigger (Can be either smokes, cats, brain, or sits).

  • KUBECF_CHECKOUT: Absolute path pointing to a kubecf checkout.

  • BRAIN_INORDER: true/false (default). True forces deterministic sequential execution.

  • BRAIN_VERBOSE: true/false (default). True forces full logging even for passing test cases.

  • BRAIN_EXCLUDE: Regexp pattern to select test cases to skip. Default _test.rb.

  • BRAIN_INCLUDE: Regexp pattern to select test cases to run. Default empty.

Note: It needs Kubecf deployed with the instance test groups enabled. Specify SCF_TESTGROUP=true while doing the scf deployment.

Attention: ⚠️ The BRAIN_... parameters must be known/set at the time of deployment to have an effect. Setting them just when invoking the brain tests is too late.

See KubeCF-testing for a step-by-step guide