Loading EN-304-621.md +8 −3 Original line number Diff line number Diff line Loading @@ -1225,17 +1225,22 @@ Verify that: 1. Have the product initialised and available with the default configuration and required credentials. 2. Have the managed element initialised and available with the default configuration and required credentials. 3. Study the deployment instrcutions about sizing of the operative environment. **Activities:** <br/> 1. Send a correct API request towards each system API endpoint. 2. Send an incorrect API request towards each system API endpoint. 3. Send a momentary spike of request that exceeds the reasonable and expected load of incoming requests. **Verdict:** <br/> 1. Pass if all API endpoints responds as expected 1. and the response latency is recorded in defined accuracy 1. and tracks the number of successfull requests. 1. Fail otherwise. 2. and the response latency is recorded in defined accuracy 3. and tracks the number of successfull requests 4. and the incorrect API requests are identified and logged 5. and the spike of high volume requests is handled gracefully. 6. Fail otherwise. **Supporting Evidence:** Loading Loading
EN-304-621.md +8 −3 Original line number Diff line number Diff line Loading @@ -1225,17 +1225,22 @@ Verify that: 1. Have the product initialised and available with the default configuration and required credentials. 2. Have the managed element initialised and available with the default configuration and required credentials. 3. Study the deployment instrcutions about sizing of the operative environment. **Activities:** <br/> 1. Send a correct API request towards each system API endpoint. 2. Send an incorrect API request towards each system API endpoint. 3. Send a momentary spike of request that exceeds the reasonable and expected load of incoming requests. **Verdict:** <br/> 1. Pass if all API endpoints responds as expected 1. and the response latency is recorded in defined accuracy 1. and tracks the number of successfull requests. 1. Fail otherwise. 2. and the response latency is recorded in defined accuracy 3. and tracks the number of successfull requests 4. and the incorrect API requests are identified and logged 5. and the spike of high volume requests is handled gracefully. 6. Fail otherwise. **Supporting Evidence:** Loading