TestingDashboardHowTo

Differences between revisions 1 and 2
⇤ ← Revision 1 as of 2012-05-30 11:20:29 →
Size: 526
Editor: 94-192-45-141
Comment:
← Revision 2 as of 2012-05-30 11:24:46 → ⇥
Size: 649
Editor: 94-192-45-141
Comment:
Deletions are marked like this. Additions are marked like this.
Line 6: Line 6:
  * Bugs: The bugs will be referenced by a string of the format: LP:#111111   * Bugs: The bugs will be referenced by a string of the format:
    {{{#!python
      LP:#111111
     }}}
Line 8: Line 11:
If there is a build, it is always at the beginning of the description. Followed by as many bugs as required, all comma separated. If there is a build, it is always at the beginning of the description. Followed by as many bugs as required, all comma separated. No white spaces no trailing spaces, just a nice parsable comma separated values string.

To be able to keep track of bugs raised as a result of automated testing, whenever a bug is added to launchpad, it needs to be reflected in the Jenkins description for that particular job run.

There are two bits of information that are part of the description:

  • Build Number: usual format, i.e. 20120512
  • Bugs: The bugs will be referenced by a string of the format: 
    •    1       LP:#111111

If there is a build, it is always at the beginning of the description. Followed by as many bugs as required, all comma separated. No white spaces no trailing spaces, just a nice parsable comma separated values string.

QATeam/AutomatedTesting/TestingDashboardHowTo (last edited 2012-06-29 15:37:47 by 94-192-45-141)