UNICORE Test report for EMI-1

According to the Software Verification and Validation Report Template the report should contain a general introduction and a short description for each change being certified.

Deployment Tests_

After creating unicore autoinstalling scripts we have tested them with the unicorex component. The ouput produced is the one above:

  • Author(s): Michele Carpene', m.carpen@cinecaNOSPAMPLEASE.it
  • Change: xxx
  • Component: unicorex
  • Outcome: Certified
  • ..............................
  • Unicorex task active...
  • Log files present into /var/log/unicore
  • Documentation is present into /usr/share/doc/unicore-unicorex
  • platform: Linux zam052v10 #1 SMP 2010-12-13 11:13:53 +0100 x86_64 x86_64 x86_64 GNU/Linux

Report for ChangeId 001

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 packages (rpm or deb) 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.

When tests are automated, a link to the tool-specific report can be attached.

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, and could additionally include a reference to the bug in the bug tracker.

Standard Compliance/Conformance tests
When used, these tests have to be specifically mentioned together with a reference to the standard adopted.

Performance and Scalability tests
The format to report these types of tests is up to the product team. Performance and Scalability tests should be always run on Major release candidates (to be confirmed).

Report for ChangeId 002


Report for ChangeId 003


  • report.log.txt: report log file example for UNICORE deployment tests
Topic attachments
I Attachment History Action Size Date Who Comment
Texttxt report.log.txt r2 r1 manage 3.0 K 2011-02-21 - 14:54 UnknownUser report log file example for UNICORE deployment tests
Edit | Attach | Watch | Print version | History: r4 < r3 < r2 < r1 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r4 - 2011-02-21 - unknown
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    EMI All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2022 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