Skip to main content

Unit testing OpenStack with tox

Testing is and will always be an integral part of any software development. OpenStack is no exception. In OpenStack, unit testing is done using tox.

Installing tox,

[apt-get | yum] install python-pip; pip install tox


Tox has various tests defined in the envlist. One can open tox.ini for a complete list of envs defined.

OpenStack defines, py27 and pep8 test. Former is for unittests and later for style checks.

How to run tox and testr

Tox can use used to list unit tests and execute all of them or any subset of them using regex.

To run all tests,
tox -e py27                        # you can chose any other                                                                           environment like py26 if you like
To run only selected tests, 
tox -e py --
One can get the test_name either from the source code of the project concerned or by asking tox to list them out. For example, the tests defined in nova.tests.compute.test_compute_cells.py are accessible by 'nova.tests.unit.compute.test_compute_cells.*'. Alternatively to list the tests using tox one has to go to tox shell after sourcing the virtual env.
source .tox/py27/bin/activate
testr  list-tests
 With the venv sourced we can run testr directly.
testr help  
testr run --parallel

testr run --parallel
After tests have run you can view the failing tests then run only that list of tests.

Errors and workaround


tox requires some elaborate environment setups which can sometimes be tricky. Here are some errors whcih I came across during my installation. For posterity, I'm documenting them in this blog,


ERROR:
Package libvirt was not found in the pkg-config search path.

 Perhaps you should add the directory containing `libvirt.pc'

 to the PKG_CONFIG_PATH environment variable

Solution:
sudo yum install libvirt-devel


ERROR:
fatal error: my_config.h: No such file or directory


 Solution:
sudo yum install mysql-devel
Labels:
Location: CERN, 1217 Meyrin, Switzerland

Comments

Post a Comment

Popular posts from this blog

Multimaster replication with Symmetric DS

Symmetric DS is an awesome tool for trigger based replication whcih works for all major database vendors, including but not limited to PostgreSQL, MySQL, MSSQL, Oracle and many others. Symmetric-DS is a java application and can execute on any platform on whcih JRE is available including Windows and Linux. Trigger based replication, in constrast to disk based (eg. DRBD ) or transaction log file shipping based or statement based , works by registering triggers on DMLs and sending the data thus generated to remote machines. Another very popular trigger based DB replication tool is Slony . Symmetric-DS in addition to being database agnostic also supports multi-master replication (MMR). MMR usecase involves multiple database nodes, connected in a pool with DML updates coming from any of them. This is different from the normal master-slave replication, where slaves are not expected to generate any data events, and the sole authority of database is the master. MMR requirement causes d...
1 comment
Read more

PC Power supply and hacks

For posterity and myself, I'm leaving some tips and tricks of PC Power Supply Unit (PSU) whcih is an SMPS (Switched Mode Power Supply). There are a variety of uses of a +12V, +5V and +3V DC power supply like lighting up an LED strip or powering a raspberry pi. There are various colored cables in a typical ATX 12V SMPS. I'll list out the various color lines and what they mean, Sr. No Cable color Number of cables in a PSU Use 1 Green exactly one (1) Wake up signal from motherboard. Pressing PC power button makes this signal carry wake up signal to PSU to start. Green needs to be touched with the any ground to make the SMPS start. For self-starting PSUs, green needs to be connected with one black all the time. 2 Blue exactly one (1) -12V 3 Purple exactly one (1) +5V standby. When power supply is on standby mode (not on by signalling green), this line can give 1-2 A current. 4 Gray exactly one (1) Power good signal. When PSU levels has reached specificati...
3 comments
Read more

Cryptographic Primitive III: RSA Asymmetric Keys

RSA cryptosystems involves, a private key (which is kept private) and a public key, which is kept public i.e. known to everyone. The security of RSA hinges on the mathematically difficult problem of finding prime factorization of a very large number. Let's quickly disuss how a public, private key pair can be generated, Let, p and q be two large primes, then $n = q \times q$ $\phi(n) = (p-1) \times (q-1)$ Here, $\phi(n)$ is called euler's totient function Choose a random number $e$ such that, $e \in \left\{0,1,2...\phi(n)-1\right\}$ and $gcd(e,\phi(n)) = 1$ The gcd condition will ensure that we have an inverse of $e$ in $\mathbb{Z}_{26}$. Now, using extended euclidian algorithm one can get the inverse of e as d such that, $d \equiv e \pmod{\phi(n)}$ So, there we have it, the private key is $e$ and the public key is $(n,d)$. Few points to note here are, $p$ and $q$ are both $\geq 2^{512}$, although the recommened size is $2^{1024}$ $n$ is $\geq 2^{1024}$, although the recommended...
Post a Comment
Read more