The Mer Wiki now uses your Mer user account and password (create account on https://bugs.merproject.org/)
Quality/Development
From Mer Wiki
< Quality(Difference between revisions)
(→QA Development) |
|||
Line 31: | Line 31: | ||
* Architecture domains (Communications, Graphics, etc. ) | * Architecture domains (Communications, Graphics, etc. ) | ||
* UX (for GUI testing) | * UX (for GUI testing) | ||
+ | |||
+ | [[Category:QA]] |
Revision as of 12:34, 27 June 2012
Development
Tools
OBS
The Mer Tools are divided to two groups:
- Host (SDK) and device side tools (Mer:Tools)
- Server side tools (Project:MINT)
Host and device side tools are compiled only against the Mer repositories. By this we try to keep the tools version's stable and avoid conflicts with the host distribution's packages (eg. Ubuntu/OpenSuse/Fedora). In addition, the Mer SDK can be used for testing.
The server side tools are provided for the most common Linux distributions. These are the tools that don't work in the Mer SDK, like OTS (Test automation system).
Development
- Host (SDK) and device side tools are submitted to Mer:Tools:Testing
- Server side tools are submitted to Project:MINT:Testing
As a developer:
- Copy the original package to your home project
- Make changes/fixes/updates
- Test your changes
- Create a submit request to the respective OBS project (Mer:Tools:Testing or Project:MINT:Testing)
- If the request is declined, there is usually a reason for that. Go back to step 2 (avoid infinite loop!).
Tests
Tests are divided to 2 groups:
- Architecture domains (Communications, Graphics, etc. )
- UX (for GUI testing)