Skip to content

acceptance-tests job from cf/223

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: f8f63fd8 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

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_push_timeout

Timeout for cf push

client_secret

The client secret for the uaa gorouter client

default_timeout

Default Timeout

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_internet_dependent

Flag to include the internet dependent test suite.

Default
false

include_logging

Flag to include the logging test suite.

Default
false

include_operator

Flag to include the operator tests which may modify the global state of an Elastic Runtime deployment.

Default
false

include_routing

Flag to include the routing test suite.

Default
false

include_security_groups

Flag to include the security groups test suite.

Default
false

include_services

Flag to include the services API test suite.

Default
false

include_sso

Flag to include the services tests that integrate with SSO.

Default
false

include_v3

Flag to include the v3 API test suite.

Default
false

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

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_diego_unsupported_tests

Skip tests that are known to not be supported by Diego. Set to true if your deployment defaults to Diego as its runtime.

Default
false

skip_regex

Regex for tests that should be skipped

skip_ssl_validation

Toggles cli verification of the Elastic Runtime API SSL certificate

Default
false

staticfile_buildpack_name

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

system_domain

The system domain for your CF release

use_diego

App tests push their apps using diego if enabled. Route service tests require this flag to run.

Default
false

use_http

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

Default
false

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.