March 2014

Posted by stylesen

Linaro Automated Validation Architecture popularly called LAVA is composed of different components. One of the core components in the LAVA framework is the lava-server component. LAVA developers in the recent past made sure that lava-server's unit tests are working properly and relevant to current code base. As a developer of LAVA I hit this issue everytime I want to run unit tests for lava-server (when I switch environments), mainly due to postgresql dependency. Following are stuff you need to setup in order to run unit tests in LAVA. (Do not do this production deployment, only recommended for dev mode deployments)

lava-master is the default postgresql user created for administering LAVA related databases. In order to run unit tests, the default postgresql user of LAVA should have permissions to create and drop databases. The test database created by LAVA unit test is called 'test_lava-master'. The 'lava-master' user creates and destroys this 'test_lava-master' database each time the unit tests are run. You must be 'root' user in order to perform the following operations: