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)
(New page: = QA 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...) |
|||
| Line 9: | Line 9: | ||
* Server side tools (Project:MINT) | * 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 | + | 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). | 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). | ||
| Line 25: | Line 25: | ||
# Ceate submit request to a respective OBS project (Mer:Tools:Testing or Project:MINT:Testing) | # Ceate submit request to a 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!). | # 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 3 groups: | ||
| + | * Core (for packages like bluez, connman, ofono, alsa) | ||
| + | * Middleware (for packages like telepathy) | ||
| + | * UX (for GUI testing) | ||
Revision as of 05:38, 25 May 2012
QA 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
- Ceate submit request to a 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 3 groups:
- Core (for packages like bluez, connman, ofono, alsa)
- Middleware (for packages like telepathy)
- UX (for GUI testing)
