UNICORE Software Verification and Validation Plan


As stated in the Software Verification and Validation Plan Template a SVVP per service/component should be provided.

The functionality tests, the unit tests and the regression tests are automated and are run during each build. Therefore they are provided through the same tool for automatic building and testing execution, even if by different plugins. Also this means that if there is a successful build then all listed test succeeded.


after Y2 refactoring

Component Name Release Detail Status
UVOS Server v1.4.2 Report HOLD

From Y1 (old components factorization)

Component Name Release Detail Status
TSI v6.4.0 Report HOLD
XNJS v1.4.0 Report HOLD
UAS-C v1.4.0 Report HOLD
UAS-D v1.4.0 Report HOLD
BES v1.4.0 Report HOLD
REGISTRY v1.4.0 Report HOLD
CIP v1.4.0 Report HOLD
UCC v1.4.0 Report HOLD
Client Libraries v1.0 Report HOLD
HILA v2.2 Report HOLD
WSRFlite v2.0.0 Report HOLD
UNICORE/X v1.4.0 Report HOLD
Gateway v6.4.0 Report OK
XUUDB v6.4.0 Report OK
UVOS v1.4.1 Report OK
XACML Entity v2.0.0 Report OK
AuthZ Data Providers v2.0.0 Report OK
Security libraries v2.0.0 Report OK

Report examples

-- ClaudioCacciari - 17-Dec-2010

Edit | Attach | Watch | Print version | History: r23 < r22 < r21 < r20 < r19 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r23 - 2012-01-05 - 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-2023 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