QA Reports is a web based test result reporting application originally developed for MeeGo. For basic features demonstration see trailer at YouTube. User guide and other detailed documentation is available in wiki.
QA Reports is built with Ruby on Rails.
- Clone the repository
cap production deploy:setup
cap production deploy:migrations
For very thorough documentation see the instructions in wiki.
- 13 Aug 2013: Added support for grouped serial measurements. If you have been using serial measurements, and the
serieselements, you may see unexpected behavior. From now on if two or more
casehave the same
groupattribute the series are grouped together.
- 06 May 2013: Added Gerrit integration (link by change ID the same way as Bugzilla)
- 29 April 2013: Not compatible with old installations of QA Dashboard. If you have been using QA Dashboard you will need to update it as well.
- 02 April 2013: New external configuration and service support taken in use. This will replace the old
bugzilla.ymlconfiguration file. Upgrading is not mandatory,
bugzilla.ymlwill still work if it exist. See wiki for more information.
- 26 March 2013: Asset Pipeline taken in use.
- 11 March 2013: Ruby 2.0 compatible.
- 11 September 2012: Added application configuration file
config/config.yml. You will need to run
cap deploy:setupagain, or create a copy of the file to your servers
qa-reports/shared/configfolder before deploying.
- 10 September 2012: QA Reports was updated to use Ruby 1.9.3 and Rails 3.2.
config/config.yml: General application configuration
- Application configuration is aimed for enabling customization while keeping your fork compatible with the upstream version.
config/external.services.yml: External services integration configuration
- QA Reports can showinformation from Bugzilla and Gerrit, and create links to other services. Settings are defined in this file. See wiki for more information.
config/deploy/production.rb: Deployment settings
config/environments/production.rb: Environment specific configuration, e.g. email settings
cap production deploy:setup you will be prompted for the most important settings. There are a bunch of Ruby files in the
config folder that can be adjusted as well if you wish. Notice however that no local changes apart from the ones
deploy:setup asks are effective on the server since Capistrano loads the software from Github upon deployment.
QA Reports is licensed under the terms of the LGPL version 2.1