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)
(→Tools) |
(→Tools) |
||
| Line 27: | Line 27: | ||
# Push your changes to the version control | # Push your changes to the version control | ||
# Inform tools team about the changes with changes diff (URL to gitorious/gerrit/github diff) | # Inform tools team about the changes with changes diff (URL to gitorious/gerrit/github diff) | ||
| − | # The tools team will update the tool to | + | # The tools team will review, retest and update the tool to OBS |
== Tests == | == Tests == | ||
Revision as of 13:00, 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
- Unstable host (SDK) and device side tools are updated to Mer:Tools:Testing
- Unstable server side tools are updated to Project:MINT:Testing
As a developer:
- Search the tool's version control location About
- Pull the tool's source code and make changes
- Copy the original package to your home project in OBS
- Update your changes to the OBS
- Test your changes
- Push your changes to the version control
- Inform tools team about the changes with changes diff (URL to gitorious/gerrit/github diff)
- The tools team will review, retest and update the tool to OBS
Tests
Tests are divided to 2 groups:
- Architecture domains (Communications, Graphics, etc. )
- UX (for GUI testing)
