The following is a proposal for a Certification Report Template for the EMI project. It is intentionally general to be applicable to all the 4 middlewares: ARC, dCache, gLite and UNICORE. Please provide any feedback to the SA2 list: emi-sa2@eu-emiNOSPAMPLEASE.eu

Certification report for ChangeId

Author(s): author name(s), email contact(s)

Change: a unique identifier for the change being certified and a short description of it

Component: the EMI component where the change will be applied

Outcome: Certified/Rejected/In Progress

Clean installation

Describe the installation procedure for a clean installation, that is an installation of the service/component including the change on a clean machine.

Don't forget to:

  • include the output from installation stages,
  • include configuration details.

Verify that the RPMs included in the change have been correctly installed.

Test report

Show which tests have been run (with the revision number in case of tests maintained on a VCS), how you run the tests, and the tests output. The tests output should include:
  • a short description of the tests run (1-2 lines should be enough)
  • the outcome of the tests, that is either PASSED or FAILED.

Regression tests
With regression tests here we mean tests that are specifically associated to bugs, that have the goal of verifying that a specific bug (problem) has been fixed with the change under certification. Regression tests should follow the same format of the test report, but should also include a reference to the bug in the bug tracker.

Upgrade from production

When meaningful, describe the upgrade of the service/component by installing the change on a working production version of the service/component.

Don't forget to:

  • include the output from upgrade stages,
  • include configuration details if a new configuration was needed.

Verify that the RPMs listed in the change have been correctly installed.

Test report

Show which tests have been run (with the revision number in case of tests maintained on a VCS), how you run the tests, and the tests output. The tests output should be formed by:
  • a short description of the test run (1-2 lines should be enough)
  • the outcome of the tests, that is either PASSED or FAILED.

Regression tests
With regression tests here we mean tests that are specifically associated to bugs, that have the goal of verifying that a specific bug (problem) has been fixed with the change under certification. Regression tests should follow the same format of the test report, but should also include a reference to the bug in the bug tracker.

-- GianniPucciani - 27-Aug-2010

Edit | Attach | Watch | Print version | History: r2 < r1 | Backlinks | Raw View | Raw edit | More topic actions...
Topic revision: r1 - 2010-08-27 - GianniPucciani
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    Main 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.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback