Service Test Specification Development

Service Test Specification Development Aggregate Function functions provide the necessary functionalities to manage the service test catalog containing the service test specifications, the rules that define the test configuration setting up based on the context, the rules that define the strategies for executing the test as well as how the test results should be restituted.<br/>Test strategies can range from simple to complex and encompass the definition of test scenario.<br/>The definition of the test (with specification and rules) is very important because it defines the question that is asked and thus shapes the result that is reported back.<br/>The functionalities include providing:<br/>• Service Test Specification and test scenario management<br/>  - Test scenario management: for example, a home equipment self-test can trigger a test scenario that verifies the functioning of all the services associated, depending on the installed products of the user. Thus, the Box could test its internal configuration and functioning and its capacity to connect to internet and VoIP services.<br/>  - Managing service test capabilities: some resources used to implement services have limited capabilities for executing tests, especially for multiple parallel testing. All the constraints linked to limited resources test capabilities and depending on the execution context must be aggregated and managed at service test level.<br/>  - Managing initiator authorization: some tests are restricted to some user roles (internal or external) so the authorization are defined at the Service Test Strategy and Policy Management<br/>• Test rules defining the strategies for setting up test configuration<br/>• Test rules defining how to carrying out the service test<br/>  - For example: to choose the next test in a scenario depending on the results of the previous tests<br/>• Test rules defining the enrichment of test results. <br/>  - For example: enrichment of internet bandwidth measure based on installed product<br/>• Test rules defining the restitution of the result depending on test execution context<br/>   - For example: a test result of ok/not ok can be enough for a user whereas customer care requires more details in the result of the test.<br/>