Skip to content

smoke_tests job from cf-smoke-tests/40.0.9

The smoke tests errand can be configured to run quick set of tests against a specific Cloud Foundry API endpoint to determine is basic push-application functionality works. Consider running the acceptance tests errand for a more extensive set of tests.

Github source: d8bcebe or master branch

Properties

smoke_tests

api

The Elastic Runtime API endpoint URL

apps_domain

The Elastic Runtime Application Domain

artifacts_directory

The directory in which to store test CF_TRACE output

backend

Defines the backend to be used. (‘dea’, ‘diego’, “ (default))

Default
""

cf_dial_timeout_in_seconds

Sets the cli timeout (CF_DIAL_TIMEOUT)

enable_isolation_segment_tests

Flag to true if you wish to run routing isolation segment tests

Default
false

enable_windows_tests

Toggles a portion of the suite that exercises Windows platform support

Default
false

ginkgo_opts

Ginkgo options for the smoke tests

Default
""

isolation_segment_domain

The domain of your routing isolation segment

Default
""

isolation_segment_name

The name of isolation segment that you deployed

Default
""

logging_app

The Elastic Runtime app name to use when running logging tests

Default
""

org

The Elastic Runtime organization name to use when running tests

password

The Elastic Runtime API user’s password

runtime_app

The Elastic Runtime app name to use when running runtime tests

Default
""

skip_ssl_validation

Toggles cli verification of the Elastic Runtime API SSL certificate

Default
false

space

The Elastic Runtime space name to use when running tests

suite_name

A token used by the tests when creating Apps / Spaces

Default
CF_SMOKE_TESTS

use_existing_org

Toggles setup and cleanup of the Elastic Runtime organization

Default
false

use_existing_space

Toggles setup and cleanup of the Elastic Runtime space

Default
false

user

The Elastic Runtime API user

Templates

Templates are rendered and placed onto corresponding instances during the deployment process. This job's templates will be placed into /var/vcap/jobs/smoke_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.