The CS riak tests live in the riak_cs repo in riak_test/tests. The test modules are:
cs296_regression_test.erl
cs347_regression_test.erl
cs436_regression_test.erl
cs512_regression_test.erl
external_client_tests.erl
list_objects_test.erl
mp_upload_test.erl
object_get_conditional_test.erl
object_get_test.erl
repl_test.erl
stats_test.erl
too_large_entity_test.erl
All of the tests rely on some common code that is in the rtcs module in riak_test/src. The repl test also uses the repl_helpers module in riak_test/src.
The only ee specific test is the repl_test, but all of the tests can be run with an ee build. An ee build for riak_cs can be generated by setting RIAK_CS_EE_DEPS in the environment prior to building.
A normal command-line execution of all of the tests looks like this:
The CS riak tests live in the
riak_csrepo inriak_test/tests. The test modules are:All of the tests rely on some common code that is in the
rtcsmodule inriak_test/src. The repl test also uses therepl_helpersmodule inriak_test/src.The only ee specific test is the
repl_test, but all of the tests can be run with an ee build. An ee build for riak_cs can be generated by settingRIAK_CS_EE_DEPSin the environment prior to building.A normal command-line execution of all of the tests looks like this:
Some people report not needing the second
-dto load the riak_cs top-level beams into the code path, but I use it just in case.