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)
Jump to: navigation, search
(Tools)
Line 31: Line 31:
  
 
== Tests ==
 
== Tests ==
 +
 +
'''OBS'''
  
 
Tests are divided to 2 groups:
 
Tests are divided to 2 groups:
 
* Architecture domains (Communications, Graphics, etc. )
 
* Architecture domains (Communications, Graphics, etc. )
 
* UX (for GUI testing)
 
* 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
 +
  
 
[[Category:QA]]
 
[[Category:QA]]

Revision as of 13:06, 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
  • Packages that are shared between Mer:Tools and Project:MINT should be 'mastered' in Mer:Tools

As a developer:

  1. Search the tool's version control location About
  2. Pull the tool's source code and make changes
  3. Copy the original package to your home project in OBS
  4. Update your changes to the OBS
  5. Test your changes
  6. Push your changes to the version control
  7. Inform tools team about the changes with changes diff (URL to gitorious/gerrit/github diff)
  8. The tools team will review, retest and update the tool to OBS

Tests

OBS

Tests are divided to 2 groups:

  • Architecture domains (Communications, Graphics, etc. )
  • UX (for GUI testing)


Development

As a developer:

  1. Search the test version control location (no info yet)
  2. Pull the test's source code and make changes
  3. Copy the original package to your home project in OBS
  4. Update your changes to the OBS
  5. Test your changes, Note: Only passing test cases are accepted!
  6. Push your changes to the version control
  7. Inform QA team about the changes with changes diff (URL to gitorious/gerrit/github diff)
  8. The QA team will review, retest and update the tool to OBS
Personal tools