I'm in your cluster, testing your riaks
Go to file
2012-08-21 10:14:21 -07:00
bin Moved rtdev*.sh to bin/. 2012-08-21 10:14:21 -07:00
doc Initial release 2012-01-10 17:21:39 -07:00
src Bumped Lager to 1.2.0 2012-08-16 13:07:01 -07:00
tests Add rt:slow_upgrade for leave/upgrade/join approach 2012-08-08 18:48:40 -07:00
.gitignore Add .gitignore 2012-04-05 17:23:09 -04:00
Makefile Initial release 2012-01-10 17:21:39 -07:00
README.md Added the capacity for a ~/.riak_test.config file 2012-08-15 12:48:50 -07:00
rebar Initial release 2012-01-10 17:21:39 -07:00
rebar.config Bumped Lager to 1.2.0 2012-08-16 13:07:01 -07:00
riak_test.config.sample Added the capacity for a ~/.riak_test.config file 2012-08-15 12:48:50 -07:00
rtbe.config Minor config changes, add rt:async_start 2012-04-02 13:42:46 -07:00
rtdev-mixed.config Add rolling_capabilities test, update verify_capabilities test 2012-08-02 21:52:56 -07:00
rtdev-setup.sh Update rtdev-setup.sh to work with recent path changes 2012-07-19 20:15:53 -07:00
rtdev.config run mapred_verify via mapred_verify_rt tests 2012-07-16 12:14:44 -04:00

Riak Test

Quick Start

Assumes riak_test and riak and/or riak-ee are all checked out in the same parent folder

  1. Edit your cp riak_test.config.sample to ~/.riak_test.config
  2. Update your new ~/.riak_test.config file's rt_deps url
  3. cd ../riak[-ee]
  4. make devrel
  5. . ../riak_test/rtdev-setup.sh
  6. cd back to riak_test
  7. riak_test rtdev verify_build_cluster

~/.riak_test.config stores multiple configurations, and you can pass them by name as the first argument to riak_test. First it looks for a file with that name in your local directory, if it doesn't find it, it looks for something with that name in ~/.riak_test.config