smoke_tests_windows job from cf-smoke-tests/42.0.50
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:
ee28622
or
master branch
Properties¶
smoke_tests
¶
api
¶The Cloud Foundry API endpoint URL
apps_domain
¶The Cloud Foundry Application Domain
artifacts_directory
¶The directory in which to store test CF_TRACE output
cf_dial_timeout_in_seconds
¶Sets the cli timeout (CF_DIAL_TIMEOUT)
client
¶The Cloud Foundry API client. Cannot be used with ‘user’ or ‘password’.
client_secret
¶The Cloud Foundry API client’s secret. Cannot be used with ‘user’ or ‘password’.
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
true
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 Cloud Foundry app name to use when running logging tests
- Default
""
org
¶The Cloud Foundry organization name to use when running tests
password
¶The Cloud Foundry API user’s password. Cannot be used with ‘client’ or ‘client_secret’.
runtime_app
¶The Cloud Foundry app name to use when running runtime tests
- Default
""
skip_ssl_validation
¶Toggles cli verification of the Cloud Foundry API SSL certificate
- Default
false
space
¶The Cloud Foundry 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 Cloud Foundry organization
- Default
false
use_existing_space
¶Toggles setup and cleanup of the Cloud Foundry space
- Default
false
user
¶The Cloud Foundry API user. Cannot be used with ‘client’ or ‘client_secret’.
windows_stack
¶Specifies the Windows stack on which the Windows tests will run if enable_windows_tests is true
- Default
windows
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_windows/
directory
(learn more).
bin/config.json
(fromconfig.json.erb
)bin/run.ps1
(fromrun.ps1.erb
)
Packages¶
Packages are compiled and placed onto corresponding
instances during the deployment process. Packages will be
placed into /var/vcap/packages/
directory.