Contributing to QA Reports

QA Reports is developed for the MeeGo community. One of the main goals is to maintain simplicity and good user experience. To avoid clutter, new features need to be selected and crafted with care.

Getting new features to QA Reports

1. Create a ticket for QA Reports
2. Promote the feature at meego-qa mailing list
3. If the feature rises the common interest, QA Reports team can help with UX design or other tasks
4. Propose and agree on UX and implementation principles with QA Reports team by commenting the Bugzilla ticket

In case the feature is not feasible from the MeeGo community point of view, but needed by the requester, one can naturally fork a new branch and implement the feature there.

Contributing the feature

1. Set up the development environment
2. Run the unit tests and integration tests as shown below. If the environment is properly set, all the tests should pass
   1. rake spec
   2. rake cucumber
3. Implement the feature and write at least the integration tests (cucumber)
4. Make sure that your branch is up-to-date with QA Reports master
5. Make sure that all unit test and integration tests pass
   1. rake spec
   2. rake cucumber
6. Send merge request to QA Reports
7. Document the feature to QA Reports wiki pages

If you are unfamiliar with Git workflow, please check out this gist before making the merge request.

QA Reports team is glad to help you out, in case you bump into any problems. The easiest way to get in touch with us is to join qa-tools irc channel at freenode/#meego-qa-tools or to send email to meego-qa mailing list.

Happy hacking!