This is a list of things that the community can work with to contribute to the Linaro Automated Validation Architecture (LAVA) project. It is not intended to include every possibility, so feel free to talk to us, look at blueprints and session notes, or be creative.

How to contribute

LAVA management is distributed across

= Recommended Reading =






Test and Verification Guidelines

minimal pre-review "smoke-tests"

Prior to submitting code, the developer should setup a local LAVA installation and have the ability to verify that the following targets pass before and after testing

Comprehensive Pre-deployment verification

When your code has passed the initial smoke tests, you should submit changes using gerrit (see LAVA Code Review System above). The code will be reviewed and if accepted, be passed through our comprehensive functional verification test suite that will verify that your code changes do not break any existing device, device type or functionality within LAVA. This process may require rework and re-submission.

Areas to contribute to LAVA

Skills that may be useful if you are working on any part of LAVA, or that you may develop while working on it include things like:

  • Python
  • Django
  • Test automation
  • Continuous Integration Testing
  • Ubuntu
  • Android
  • Devops


Easy Tasks

  • Test deployment using lava-deployment-tool, fix issues found
  • Add lava-deployment-tool support on maverick,natty, there are bugs and we have worked on it.
  • Work on known bugs

Harder Tasks

Platform/LAB/Contribute (last modified 2014-04-23 15:28:16)