acceptance-tests job from cf/258

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.

Github source: 719ba4c5 or master branch

Properties¶

`acceptance_tests`¶

admin_password¶

The Elastic Runtime API admin user’s password

admin_user¶

The Elastic Runtime API admin user

api¶

The Elastic Runtime API endpoint URL

apps_domain¶

The Elastic Runtime Application Domain

async_service_operation_timeout¶

Timeout for asynchronous service operations

backend¶

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.

binary_buildpack_name¶

The name of the binary buildpack to use in acceptance tests that specify a buildpack.

broker_start_timeout¶

Timeout for broker starts

cf_dial_timeout_in_seconds¶

Sets the cli timeout (CF_DIAL_TIMEOUT).

cf_push_timeout¶

Timeout for cf push

default_timeout¶

Default Timeout

detect_timeout¶

Timeout for buildpack detection.

enable_color¶

Enable colorized output on ginkgo.
Default
true
existing_user¶

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.

existing_user_password¶

The password of the existing user. Only required if the existing user property is also being set.

go_buildpack_name¶

The name of the go buildpack to use in acceptance tests that specify a buildpack.

include_apps¶

Flag to include the apps test suite.

include_backend_compatibility¶

Flag to inlude whether we check DEA/Diego interoperability

include_container_networking¶

Flag for running tests that depend on container networking support being enabled in your Cloud Foundry.

include_detect¶

Flag to run tests in the detect suite

include_diego_docker¶

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.

include_diego_ssh¶

Flag to include the diego ssh suite

include_internet_dependent¶

Flag to include the internet dependent test suite.

include_isolation_segments¶

Flag for running tests that depend on having isolation segments in your Cloud Foundry.

include_privileged_container_support¶

Flag for running tests that depend on privileged container support being enabled in your Cloud Foundry.

include_route_services¶

Flag to include the route services tests. Diego must be deployed for these tests to pass.

include_routing¶

Flag to include the routing tests. Diego must be deployed for these tests to pass.

include_security_groups¶

Flag to include the security groups test suite.

include_services¶

Flag to include the services API test suite.

include_sso¶

Flag to include the services tests that integrate with SSO.

include_tasks¶

Flag to include the v3 task tests dependent on the CC task_creation feature flag.

include_v3¶

Flag to include the v3 API test suite.

include_zipkin¶

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.

isolation_segment_name¶

The name of the isolation segment to use for running isolation segment tests.

java_buildpack_name¶

The name of the java buildpack to use in acceptance tests that specify a buildpack.

long_curl_timeout¶

Timeout for long curls

nodejs_buildpack_name¶

The name of the nodejs buildpack to use in acceptance tests that specify a buildpack.

nodes¶

The number of parallel test executors to spawn. The larger the number the higher the stress on the system.
Default
2
persistent_app_host¶

The default name for the persistent app host.

persistent_app_org¶

The default name for the persistent app org.

persistent_app_quota_name¶

The default name for the persistent app quota name.

persistent_app_space¶

The default name for the persistent app space.

php_buildpack_name¶

The name of the php buildpack to use in acceptance tests that specify a buildpack.

python_buildpack_name¶

The name of the python buildpack to use in acceptance tests that specify a buildpack.

ruby_buildpack_name¶

The name of the ruby buildpack to use in acceptance tests that specify a buildpack.

skip_regex¶

Regex for tests that should be skipped

skip_ssl_validation¶

Toggles cli verification of the Elastic Runtime API SSL certificate

sleep_timeout¶

Configures SleepTimeout variable used by some tests that wait for some actions to happen.

staticfile_buildpack_name¶

The name of the staticfile buildpack to use in acceptance tests that specify a buildpack.

test_password¶

Password to use for temporary user created during tests.

timeout_scale¶

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).

use_http¶

Flag for using HTTP when making api and application requests rather than the default HTTPS

verbose¶

Whether to pass the -v flag to cf-acceptance-tests
Default
false

Templates¶

Templates are rendered and placed onto corresponding instances during the deployment process. This job's templates will be placed into /var/vcap/jobs/acceptance-tests/ directory (learn more).

bin/config.json (from config.json.erb)
bin/run (from run.erb)

Packages¶

Packages are compiled and placed onto corresponding instances during the deployment process. Packages will be placed into /var/vcap/packages/ directory.

acceptance-tests job from cf/258

Properties¶