Difference between revisions of "MagnetoDB/QA/Tests on local env workflow"
(→All local environment without CCM and Devstack) |
(→All local environment without CCM and Devstack) |
||
Line 39: | Line 39: | ||
</pre> | </pre> | ||
− | * to start stable tempest tests | + | * to start stable tempest tests (contains scenarios that verify already implemented functionality) |
<pre> | <pre> | ||
$ tox -e tempest-stable | $ tox -e tempest-stable | ||
</pre> | </pre> | ||
− | * to start in_progress tempest tests | + | * 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)) |
<pre> | <pre> | ||
$ tox -e tempest-in-progress | $ tox -e tempest-in-progress | ||
</pre> | </pre> | ||
− | * to start not_ready tempest tests | + | * 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)) |
<pre> | <pre> | ||
$ tox -e tempest-not-ready | $ tox -e tempest-not-ready |
Revision as of 10:14, 3 April 2014
All local environment without CCM and Devstack
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
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 need some time for install requirements.