Back to SPI Workbook

How to produce QA Savannah report

SPI/QA web page:

Please go to the SPI/QA web page to have more information about QA activites. Click here.

If a link for your project is not present, please go to the next section.

QA reports through the Web Form:

Savannah QA reports may be produced simply through a Web Form.

  • Go to the Savannah QA report generation web form.
  • Fill in the options required, see the Option List in this page.
  • Submit the query
  • To reach the QA report produced, click on the upcoming link (in Info section).

Options list

Several options are available to the user:

  1. Tracker:
    States the Savannah tracker to be queried. Four choices are possible: bugs, patch, support and task.
  2. Project:
    States the project name which is in the Savannah system. View the list of all projects (groups) available in Savannah.
  3. Start Date:
    States the beginning date for analysis period DATE=DD/MM/YYYY.
    If not given, then period is taken from beginning of the project history.
  4. End date:
    States the end date for analysis period DATE=DD/MM/YYYY.
    If not given, then the period is taken until the end of the project history.
  5. Project configuration file:
    Enable parameter customization: header file and dependencies, title,architecture, project, label, value.
    By default, SPI settings are applied.
  6. Savannah Field:
    To be used only if no configuration. Indicates a Savannah field name for which the QA Report will be produced, empty by default. Possible values are:
    • Assigned To
    • Category
    • Component Version
    • Fixed Release
    • Item Group
    • Percent Complete
    • Planned Release
    • Platform Version
    • Priority
    • Privacy
    • Release
    • Reproducibility
    • Severity
    • Submitted By
    • Status

    Configuration file specificities

    Default settings

    Savannah QA report users have SPI default settings applied. They can thus use a configuration file which would store their own settings.

    Project configuration file

    "Use project configuration file" quote allows the usage of formely customized header and style sheet files stored in configuration files in the directory:


    If no default configuration file is defined while using the feature for a given project, the following error message will be prompted.

    Default file for project "My_Project" does not exist! 

    Details about configuration files:

    • The extension must be .ini
    • Stylesheet files can be specified in the configuration file. Indicate the full path to the directory where the stylesheet, header or css files are stored after "extra-files="

    Sample: config_file.ini:


    #HEADER FILE: the user may provide a customized header file.
    #Note that the full path is required here
    header-file: full_path/My_header.html

    #TITLE: the title of the report might be customized
    #with the following field
    title: Savannah QA report for

    #STYLESHEET: if the report requires external dependencies
    #such as images and/or stylesheets, they have to be in a specific
    #folder specified in the following field:
    extra-files: path/dependencies

    #SAVANNAH FIELDS: these correspond to the actual fields in each project defined on Savannah.
  7. -- Main.aimar - 13 Jan 2005 -- Main.jbenard - 18 Jan 2005

Edit | Attach | Watch | Print version | History: r7 < r6 < r5 < r4 < r3 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r7 - 2005-06-17 - unknown
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    SPI All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2020 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback