| Scenario |
Test Description |
Comments |
Test Result (Pass/Fail) |
Test Results of 1.0 |
Test Results of 1.5 |
Test Results of 1.6
|
Test Results of 1.7 |
| 1 |
Create a new registry entry /create a new folder and add a new registry entry
|
|
N/A |
N/A |
Pass |
Pass
|
Pass
|
| 2 |
Remove a registry entry
|
|
N/A |
N/A |
Pass
|
Pass
|
Pass
|
| 3 |
Edit an existing registry entry
|
|
N/A |
N/A |
Pass
|
Pass
|
Pass
|
| 4 |
Access a registry entry through sequences, Proxy services to check if the entry is properly picked up
|
|
N/A |
N/A |
Pass
|
Pass
|
Pass
|
| 5 |
Access a registry entry which has been removed through sequences, Proxy services to see how it is handled
|
|
N/A |
N/A |
Pass
|
Pass
|
ESBJAVA-526 |
| 6 |
Try creating registry entries which are not XML to see how they are handled |
|
N/A |
N/A |
Pass
|
Pass
|
Pass |
| 7 |
Change the cache limit of the registry entry items and see if they are being fetched from the registry once the cache is timed out |
|
N/A |
N/A |
Pass
|
Pass |
Pass
|
| 8 |
Before the cache is timed out of an item, click on the button "Notify" and see if the item is being picked up from the registry and not from the cache |
|
N/A |
N/A |
Pass
|
Pass |
Pass
|
9
|
Try sample 50 -Engage WS-Security to endpoints and retrieve the policy key from the registry (e.g.:-<enableSec policy="Policy/policy_3.xml"/>)
<definitions xmlns="http://ws.apache.org/ns/synapse">
<registry provider="org.apache.synapse.registry.url.SimpleURLRegistry">
<parameter name="root">file:registry/</parameter>
<parameter name="cachableDuration">15000</parameter>
</registry>
<in>
<send>
<endpoint name="secure">
<address uri="http://localhost:9000/soap/SecureStockQuoteService">
<enableSec policy="Policy/policy_3.xml"/>
<enableAddressing/>
</address>
</endpoint>
</send>
</in>
<out>
<header name="wsse:Security" action="remove"
xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"/>
<send/>
</out>
</definitions>
|
|
Fail |
Pass |
Pass
|
Pass
|
Pass
|
10
|
Try sample 103 -Engage WS-Security to endpoints and retrieve the policy key from the registry (e.g.:-<enableSec policy="Policy/policy_3.xml"/>)
<definitions xmlns="http://ws.apache.org/ns/synapse">
<registry provider="org.apache.synapse.registry.url.SimpleURLRegistry">
<parameter name="root">file:registry/</parameter>
<parameter name="cachableDuration">15000</parameter>
</registry>
<proxy name="StockQuoteProxy">
<target>
<inSequence>
<header name="wsse:Security" action="remove"
xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"/>
<send>
<endpoint>
<address uri="http://localhost:9000/soap/SimpleStockQuoteService"/>
</endpoint>
</send>
</inSequence>
<outSequence>
<send/>
</outSequence>
</target>
<publishWSDL uri="file:repository/conf/sample/resources/proxy/sample_proxy_1.wsdl"/>
<enableSec policy="Policy/policy_3.xml"/>
<enableSec/>
</proxy>
</definitions>
|
|
Fail |
Pass |
Pass
|
Pass
|
Pass
|
| 11 |
Change the settings in a file located at the dynamic registry. Check the changes after the specified cachable duration. Now, change the registry file again after some time and check whether the changes are applied.
|
|
N/A |
Pass (Failed for the script -out caching) |
Pass |
Pass
|
Pass
|
