TWiki> EMI Web>EmiSa1>TSA13>EMIBetaAcceptanceTesting (revision 3)EditAttachPDF

EMI Beta & Acceptance Testing

In order to improve the quality of its products and services and to increase the users confidence, EMI is providing access to interested parties to earlier stages/phases of the software development:

  • beta phase - through participation in EMI Beta Testing activity
  • release candidate phase- through participation in EMI Acceptance Testing activity

EMI Beta Testing

Access to beta versions of EMI products is provided to beta testers through access to EMI testing repository:

  • beta version
    • bug fixes and/or new features/improvemets are already implemented
    • basic testing was done by the PT, enough to be confident it can be reccomended to beta testers
    • performance and/or stability tests have still to be done
  • beta testers
    • experienced sites interested in having an early access, a technical preview to future releases
  • EMI testing repository:
    • dist/EMI/testing/{1|2|3}/<platform\>/<basearch\>
    • not-signed packages that will become part of the next stable distribution; in the certification stage, available for technical preview
    • emi-1-testing.repo
  • notification
    • beta testers are notified of the availability of packages in the testing repository through a GGUS tkt opened by the EMi RM - see GGUS template for more info
    • beta testing duration is of 5 days
    • eventual problems should be recorded in the ticket
    • developers are involved to provide workaround or eventual bug fixes
    • at the end of this period beta testers fill a small report, see report template for details, and reccomend or not the versions tested

EMI Acceptance Testing

Access to release candidate versions of EMI products is provided to acceptance testers through access to EMI deployment repository:

  • release candidate version
    • version with potential to be a final product, ready to release unless fatal bugs emerge
    • Certified by the PT and by eventual beta testers
    • available during an EMI Update Cycle - uner EMi QC verification and testbed deployment
  • acceptance testers
    • sites interested in having an early access to the stable version fo future updates
  • EMI deployment repository:
    • dist/EMI/deployment/{1|2|3}/<platform\>/<basearch\>
    • signed, tested, certified packages
    • emi-1-updates.repo
  • notification
    • acceptance testers are notified of the availability of packages in the deployment repository through a GGUS tkt opened by the EMi RM - see GGUS template for more info
    • acceptance testing duration is of 5 days
    • eventual problems should be recorded in the ticket
    • developers are involved to provide workaround or eventual bug fixes
    • at the end of this period acceptance testers fill a small report, see report \template for details, and reccomend or not the versions tested

GGUS Template

Subject: 	EMI XXXX beta/acceptance testing
Notification Mode: on every change
CC to:  or 
Describe your problem providing the information listed here: 
Please assign to EMI Release Management SU

Dear Beta/Acceptance Testers,

The EMI   beta version is available in the testing/deployment repository:
_link_to_repository_
YUM .repo file:
_link_to_repo_file_

Please use the information provided in the task:
_link_to_task_in_emi_release_tracker_

Please let me know if you need something else.

Type of problem: Middlewaew
Priority: Less Urgent

Final Report template


*********************************
EMI Staged-Rollout Report Template 
*********************************

Product: 
Release Task:
Date 
===========================================
 Site Name:XXX-XXXXX 
 Site Admin: 

===========================================
Comment on the release notes:

===========================================
Comment on the installation/upgrading of the service
(Missing dependencies, services which should be restarted, etc.)

===========================================
Comment on the (re)-configuration (with YAIM)
(Issues/errors found when configuring) 

===========================================
Comment about the functionality of the service (info in service reference card)
(Have the daemons started/restarted OK, does it pass the Nagios tests, if a test is not iimplemented in Nagios do it yourself)

===========================================
Any other comment

-- DoinaCristinaAiftimiei - 18-Nov-2011

Edit | Attach | Watch | Print version | History: r12 | r5 < r4 < r3 < r2 | Backlinks | Raw View | Raw edit | More topic actions...
Topic revision: r3 - 2011-11-22 - DoinaCristinaAiftimiei
 
    • 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-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