Difference between revisions of "MagnetoDB/QA/Tests on local env workflow"
(→All local environment without CCM and Devstack) |
|||
Line 1: | Line 1: | ||
− | = | + | =Local environment without CCM and Devstack = |
+ | |||
+ | == Create the environment == | ||
1. Download [http://www.apache.org/dyn/closer.cgi?path=/cassandra/2.0.6/apache-cassandra-2.0.6-bin.tar.gz Cassandra 2.0.6] | 1. Download [http://www.apache.org/dyn/closer.cgi?path=/cassandra/2.0.6/apache-cassandra-2.0.6-bin.tar.gz Cassandra 2.0.6] | ||
Line 26: | Line 28: | ||
$ cd magnetodb | $ cd magnetodb | ||
</pre> | </pre> | ||
+ | |||
+ | ==Running Tests== | ||
5. Run tox with necessary parameters: | 5. Run tox with necessary parameters: | ||
Line 54: | Line 58: | ||
</pre> | </pre> | ||
− | Each group of tests run in individual venv and | + | Each group of tests run in individual venv and needs some time for install requirements. |
Revision as of 14:07, 3 April 2014
Local environment without CCM and Devstack
Create the environment
1. Download Cassandra 2.0.6
2. Run Cassandra single node instance
$ cd apache-cassandra-2.0.6/bin $ sudo ./cassandra -f
3. Run CQLSH
$ cd apache-cassandra-2.0.6/bin $ ./cqlsh
create service keyspaces and table
cqlsh> CREATE KEYSPACE magnetodb WITH REPLICATION = { 'class' : 'SimpleStrategy', 'replication_factor' : 1 }; cqlsh> CREATE TABLE magnetodb.table_info(tenant text, name text, exists int, "schema" text, status text, internal_name text, PRIMARY KEY(tenant, name)); cqlsh> CREATE KEYSPACE user_default_tenant WITH REPLICATION = { 'class' : 'SimpleStrategy', 'replication_factor' : 1 };
4. Clone MagnetoDB repo
$ git clone https://github.com/stackforge/magnetodb.git $ cd magnetodb
Running Tests
5. Run tox with necessary parameters:
- to start unit tests
$ tox
- to start Cassandra implementation tests
$ tox -e cassandra-impl
- to start stable tempest tests (contains scenarios that verify already implemented functionality)
$ tox -e tempest-stable
- to start in_progress tempest tests (keeps scenarios that are in progress (i.e. is being worked on) or the functionality that is a subject of changes (minor additions, refactoring, debugging))
$ tox -e tempest-in-progress
- to start not_ready tempest tests (is dedicated for the test scenarios that were created, but the appropriate functionality is not ready yet (not implemented or partially implemented))
$ tox -e tempest-not-ready
Each group of tests run in individual venv and needs some time for install requirements.