SA1 Release Testing

Procedures and tests used to validate a new release on the test infrastructure.

  • Install the Testbench (take the DB backups and restore them in the DBs).

  • Build gLite
    • Locally with the python client
    • Remotely with the Webapp

  • Build Etics
    • Locally with the python client
    • Remotely with the Webapp
    • Build locked
    • Build unlocked

  • Verify the produced reports
    • possibility of downloading produced packages

  • Review all bugs
    • Reproduce the bugs and check they are fixed
    • Report non fixed bugs

  • Run consistency tests on the DBs

  • Repeat the builds above if necessary

Open Questions

  • Do we need some tests to check:
    • NMI?
    • Several platforms?
    • Test the deployment of all components?
    • Run all tests (unit, etc) on the installation?
Edit | Attach | Watch | Print version | History: r2 < r1 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r2 - 2008-03-06 - MarianZUREK
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    ETICS 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