Yeti stands for "Yet Extraordinary Test Infrastructure".
It is rspec-based basic validation test
Under development
This repository contains tests for vcap.
RVM (Ruby Version Manager) is used to manage different ruby version on unix-based box
please follow the guideline, https://rvm.io/ to install RVM on your box.
- Mac OS X 64bit, 10.6 and above
- Ubuntu 10.04 LTS 64bit
gerrit-clone ssh://<YOUR-NAME>@reviews.cloudfoundry.org:29418/vcap-yeticd vcap-yeti./update.sh ## if run admin cases, this step can be skippedbundle exec rake tests- At first time, yeti will ask you several questions about
- target
- test user/test passwd
- admin user/admin passwd
on Terminal interactively.
And save those information into ~/.bvt/config.yml file.
Therefore, when running again, yeit will never ask those questions again.
- And to be compatible with BVT, environment variables are still available in yeti.
||Environment Variables ||Function ||Example ||
|VCAP_BVT_TARGET |Declare target environment |VCAP_BVT_TARGET=cloudfoundry.com |
|VCAP_BVT_USER |Declare test user |VCAP_BVT_USER=pxie@vmware.com |
|VCAP_BVT_USER_PASSWD |Declare test user password |VCAP_BVT_USER_PASSWD=<MY-PASSWORD> |
|VCAP_BVT_ADMIN_USER |Declare admin user |VCAP_BVT_ADMIN_USER=admin@admin.com |
|VCAP_BVT_ADMIN_USER_PASSWD|Declare admin user password|VCAP_BVT_ADMIN_USER_PASSWD=<ADMIN-PASSWD>|
- In order to support administrative test case, yeti will ask admin user/admin passwd information.
However, yeti will not abuse administrative privilege for every operation,
just list users, create normal user, delete normal user which created in test script. - Currently yeti run in serial, you could
tail -f ~/.bvt/bvt.logto get what is going on
-
what does "pending" mean and what is the correct number of pending cases that i should see?
A: "pending" means your target environment misses some preconditions, usually a service, framework or runtime.
The number of pending cases denpends on your target environment and environment variables.- For example, postgreSQL service is not available on dev_setup environment. Therefore, user run yeti against dev_setup environment, there should be some pending cases related to PostgreSQL service, and prompt message like "postgresql service is not available on target environment, #{url}"
- On the other hand, mysql service should be available on dev_setup environment. When user run yeti against dev_setup, and get some pending message like "mysql service is not available on target environment, #{url}". That should be a problem.
-
What is done in "./update.sh"?
A: Yeti has uploaded all precompiled java apps onto one blobs server. Therefore,
Yeti users do not need maven, and build java-based apps locally, just need to sync precompiled JAR/WAR files from blobs.cloudfoundry.com.
This action has been done by ./update.sh script automatically, so Yeti users need to run./update.shscript before running Yeti tests -
What is example?
A: Example is the conception in RSpec. It is entire test unit, and it will has one result, Pass/Failure/Pending. -
Where are binary assets stored?
A: Binary assets are stored in blobs.cloudfoundry.com, which is simple Ruby/Sinatra application with Mongodb service -
How do I submit binary assets?
A: There are two roles in Yeti project, one is Yeti User, the other is Yeti DEV.- Yeti user just run yeti scripts against any target environment.
- Yeti DEV develop yeti scripts
Currently only Yeti DEV can submit binary assets
-
Where is the log file stored?
A: There two level logs, runtime logs and error logs- Runtime log is stored in /.bvt/bvt.log
- Error log is stored in /.bvt/error.log