Skip to content

acceptance-tests job from cf/211

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: 48c88357 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

broker_start_timeout

Timeout for broker starts

cf_push_timeout

Timeout for cf push

default_timeout

Default Timeout

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_api

Flag to include the routing API 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

long_curl_timeout

Timeout for long curls

nodes

The number of parallel test executors to spawn. The larger the number the higher the stress on the system.

Default
2

oauth_password

The password for the uaa gorouter client

skip_regex

Regex for tests that should be skipped

skip_ssl_validation

Toggles cli verification of the Elastic Runtime API SSL certificate

Default
false

system_domain

The system domain for your CF release

use_diego

Services tests push their apps using diego if enabled

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.