Registry Verification and Validation Plan

Service/Component Description

[TO BE DONE]

Deployment scenarios

Describe the main deployment scenarios that will be used to deploy the service/component [TO BE DONE]

Unit/Regression/Functionality tests

[TO BE ADDED]

Integration tests

[TO BE ADDED]

Standard Compliance/Conformance tests

[TO BE ADDED]

Features/Scenarios to be tested

'Feature Summary' (implemented/not implemented)

Description of the feature, what it does (not how). If a script is available to test this feature, this must be stated in the title as '(implemented)'.

Normal workflow - correct input Testing the feature as it should work, with correct input. Describe different inputs combinations that can be used to test this feature.

Pass/Fail Criteria When this test should pass or fail

Error workflow - erroneous input Testing the error codes: providing wrong input the service should return the proper error messages.

Pass/Fail Criteria When this test should pass or fail

Features not to be tested

'Feature Summary'

Description and explanation for not being included in the current test plan

Performance tests

Describe the strategy to implement performance tests, then main system variables to control and the values to use. [TO BE DONE]

Scalability tests

Describe the strategy to implement scalability tests, what are the variables that should be studied and the values to use. [TO BE DONE]

Deployment tests

1. Install from the binary package unicore-registry.
2. Prepare a JKS keystore with one certificate (may be self-signed).
3. Configure the service by setting values of the properties in /etc/unicore/registry/uas.config:
   • uas.targetsystem.sitename=SERVICENAME-REGISTRY

1. Start service using system init script by root /etc/init.d/unicore-registry.
2. There should be no errors/warnings in the log files.
3. Server's process uid should be 'unicore'.
4. Perform the right modifications in =/etc/unicore/registry/wsrflite.xml
   • change registry service name:
   • property name="unicore.wsrflite.baseurl" value="https://localhost:port/SERVICENAME-REGISTRY/services"/
5. There should be no errors/warnings in the registry's log file.
6. It's possible also to do a test connecting to the registry, for example with the gateway, adding the registry uri to the connection.properties file
7. Check also service status with =/etc/init.d/unicore-registry status.
8. Eventually check for PID files.

-- ClaudioCacciari - 07-Feb-2011