< Quality(Difference between revisions)
|
|
| Line 1: |
Line 1: |
| | = Development = | | = 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'''
| |
| − | * Packages that are shared between Mer:Tools and Project:MINT should be 'mastered' in Mer:Tools
| |
| − |
| |
| − | As a developer:
| |
| − | # Search the tool's version control location [[:Category:About|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 == |
Revision as of 06:11, 29 June 2012
Development
Tests
OBS
Tests are divided to 2 groups:
- Architecture domains (Communications, Graphics, etc. )
- UX (for GUI testing)
Development
As a developer:
- Search the test version control location (no info yet)
- Pull the test'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, Note: Only passing test cases are accepted!
- Push your changes to the version control
- Inform QA team about the changes with changes diff (URL to gitorious/gerrit/github diff)
- The QA team will review, retest and update the tool to OBS
