acceptance-tests job from cf/242
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:
bd6fa28b
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. Route service tests require this flag to be set to diego in order to run.
- Default
""
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
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.
- Default
true
include_backend_compatibility
¶Flag to inlude whether we check DEA/Diego interoperability
- Default
false
include_detect
¶Flag to run tests in the detect suite
- Default
true
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.
- Default
false
include_diego_ssh
¶Flag to include the diego ssh suite
- Default
false
include_internet_dependent
¶Flag to include the internet dependent test suite.
- Default
false
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.
- Default
false
include_routing
¶Flag to include the routing tests. Diego must be deployed for these tests to pass.
- Default
true
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_tasks
¶Flag to include the v3 task tests dependent on the CC task_creation feature flag.
- 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
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
- Default
false
staticfile_buildpack_name
¶The name of the staticfile buildpack to use in acceptance tests that specify a buildpack.
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
(fromconfig.json.erb
)bin/run
(fromrun.erb
)
Packages¶
Packages are compiled and placed onto corresponding
instances during the deployment process. Packages will be
placed into /var/vcap/packages/
directory.