The 72 hour Stability Test for Policy XACML PDP has the goal of introducing a steady flow of transactions initiated from a Test Client server running JMeter. The transactions will be submitted through the PDP REST API. Two tests shall be executed, one for config policies and one for operational policies. The flow for each of these the two test cases case will be as follows:
- Create a policy10 guard policies
- Push the policy
- Update the policy
- Push the updated policy
- Delete the policy from PDP
- Delete the policy from PAP
- 10 policies
- Run two threads that continuously call getDecision, one that should result always result in a "PERMIT" response, and another that should always result in a "DENY" response
The number of times the getDecision threads execute is configurable, they can be set to to Each test case shall be executed in a loop. The loop is configurable to execute a defined number of times or indefinitely. For the purposes of the 72 hour stability test run, the loop shall threads will be set to infinate run indefinitely and the process manually terminated after the 72 hours has elapse.The policies are automatically deleted from PAP and the PDP on termination of the test case.
JMeter records to verifies the response to for each request to the PDP REST API . Additionally, the JMeter Performance Monitor plugin is used to measure the memory and CPU usage of the PDP and PAP processesand records the results. CPU and memory usage for the duration of the 72 hour test run will be recorded using JConsole.