acceptance-tests job from cf/257
The acceptance tests errand can be configured to run full acceptance test suite against a specific Cloud Foundry API endpoint. Consider running smoke tests errand for a smaller set of tests.
The Elastic Runtime API admin user’s password
The Elastic Runtime API admin user
The Elastic Runtime API endpoint URL
The Elastic Runtime Application Domain
Timeout for asynchronous service operations
App tests push their apps using the backend specified. If not set, tests that require a specific backend will not be run. Route service tests require this flag to be set to diego in order to run.
The name of the binary buildpack to use in acceptance tests that specify a buildpack.
Timeout for broker starts
Sets the cli timeout (CF_DIAL_TIMEOUT).
Timeout for cf push
Timeout for buildpack detection.
Enable colorized output on ginkgo.
The username of an existing user. If set, the acceptance-tests will push apps and perform other actions as this user, otherwise its default behaviour is to create a temporary user for such actions.
The password of the existing user. Only required if the existing user property is also being set.
The name of the go buildpack to use in acceptance tests that specify a buildpack.
Flag to include the apps test suite.
Flag to inlude whether we check DEA/Diego interoperability
Flag for running tests that depend on container networking support being enabled in your Cloud Foundry.
Flag to run tests in the detect suite
Flag to include tests related to running Docker apps on Diego. Diego must be deployed and the CC API docker_diego feature flag must be enabled for these tests to pass.
Flag to include the diego ssh suite
Flag to include the internet dependent test suite.
Flag for running tests that depend on having isolation segments in your Cloud Foundry.
Flag for running tests that depend on privileged container support being enabled in your Cloud Foundry.
Flag to include the route services tests. Diego must be deployed for these tests to pass.
Flag to include the routing tests. Diego must be deployed for these tests to pass.
Flag to include the security groups test suite.
Flag to include the services API test suite.
Flag to include the services tests that integrate with SSO.
Flag to include the v3 task tests dependent on the CC task_creation feature flag.
Flag to include the v3 API test suite.
Flag to include the zipkin test suite. include_routing must be set as well for these tests to run. For the tests to pass router.tracing.enable_zipkin must also be set to true.
The name of the isolation segment to use for running isolation segment tests.
The name of the java buildpack to use in acceptance tests that specify a buildpack.
Timeout for long curls
The name of the nodejs buildpack to use in acceptance tests that specify a buildpack.
The number of parallel test executors to spawn. The larger the number the higher the stress on the system.
The default name for the persistent app host.
The default name for the persistent app org.
The default name for the persistent app quota name.
The default name for the persistent app space.
The name of the php buildpack to use in acceptance tests that specify a buildpack.
The name of the python buildpack to use in acceptance tests that specify a buildpack.
The name of the ruby buildpack to use in acceptance tests that specify a buildpack.
Regex for tests that should be skipped
Toggles cli verification of the Elastic Runtime API SSL certificate
Configures SleepTimeout variable used by some tests that wait for some actions to happen.
The name of the staticfile buildpack to use in acceptance tests that specify a buildpack.
Password to use for temporary user created during tests.
Used primarily to scale default timeouts for test setup and teardown actions (e.g. creating an org) as opposed to main test actions (e.g. pushing an app).
Flag for using HTTP when making api and application requests rather than the default HTTPS
Whether to pass the -v flag to cf-acceptance-tests
Templates are rendered and placed onto corresponding
instances during the deployment process. This job's templates
will be placed into
Packages are compiled and placed onto corresponding
instances during the deployment process. Packages will be