Guidelines

Test package is a RPM package that includes scripts, binaries and/or libraries for testing a feature or function.

Test package's name must use <packagename>-tests[-*] format
- eg. bluez-tests or bluez-tests-unittests
Doesn't have to depend on testrunner
Test-definition is not required, however recommended
- Test package can have not approved or failing test cases
- Test package's test-definition should be installed to /opt/tests/<packagename>/test-definition/
Test package's files should be installed to /opt/tests/<packagename>/
If test package provides a common test data (audio, video, image) those files should be installed to /opt/tests/<packagename>/{audio, video, image, text etc}/

Process

As a developer:

Search / ask the test version control location
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
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