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
Bugs are located under: LAVA Project bugs on launchpad
LAVA Source code: http://staging.git.linaro.org/?a=project_list;pf=lava.
LAVA Code Review System: https://staging.review.linaro.org/#/
How to use /Git for contributing to LAVA
LAVA Planning: https://cards.linaro.org/browse/LAVA
= 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
- Fast Model (Foundation)
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.
All functional tests: http://staging.git.linaro.org/lava-team/lava-functional-tests.git/tree
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:
- Test automation
- Continuous Integration Testing
- 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
Platform/LAB/Contribute (last modified 2014-04-23 15:28:16)