Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Cloud Foundry - the open platform as a service project
Ruby

Fetching latest commit…

Cannot retrieve the latest commit at this time

Failed to load latest commit information.
assets @ 82a7ca5
config
docs
lib
services_spec
spec
tools
vendor/cache
.gitignore
.gitmodules
.rspec
Gemfile
Gemfile.lock
LICENSE.TXT
NOTICE.TXT
README.md
Rakefile
orc.yml
update
update_env

README.md

Yeti

Yeti stands for "Yet Extraordinary Test Infrastructure" and is a collection of integration tests for the CloudFoundry platform.

Running Tests

Don't forget to pull in all submodules.

Non-parallel

Tests require several environment variables to be set:

export VCAP_BVT_TARGET="http://api.example.com"

export VCAP_BVT_USER="non-admin-user@example.com"
export VCAP_BVT_USER_PASSWD="non-admin-password"

After setting up your environment you can use regular rspec to run tests:

bundle exec rspec
bundle exec rspec spec/apps/ruby_spec.rb

Tip: If you do not want to set VCAP_BVT_USER and VCAP_BVT_USER_PASSWD you can run rake prepare (task used with parallel set up) once and after that tests will just use first parallel user.

Parallel

Tests require several environment variables to be set:

export VCAP_BVT_TARGET="http://api.example.com"
export VCAP_BVT_UAA_CC_SECRET="some-secret"

export VCAP_BVT_ADMIN_USER="admin-user@example.com"
export VCAP_BVT_ADMIN_USER_PASSWD="admin-password"

(Admin credentials are only used for creating other users.)

Run rake prepare to create 16 users to be used in parallel specs. (User credentials will be stored in ~/.bvt/config.yml)

After setting up your environment here is how to run tests in parallel:

parallel_rspec spec
parallel_rspec spec -o '--tag=some-tag'

See parallel_tests gem for more information.

Assets

Binary assets are stored in http://blobs.cloudfoundry.com which is a simple Sinatra application with blob service backend hosted on CloudFoundry. These assets are then synchronized via rake assets:sync into the .assets-binaries directory.

Refer to asset docs for more information.

Something went wrong with that request. Please try again.