Service Test Management::Service Test Conducting

Service Test Conducting Aggregate Function provides the necessary functionalities to manage the end-to-end execution of a test for a service (test of a service use case getting through all concerned resources, local loop, DSLAM, Service Platform, …), either for manual or automatic testing in order to ensure that this service is working properly.<br/>This function is used in the following processes:<br/>• fulfillment for ensuring that the assigned service works as designed by testing the end-to-end service implementation. <br/>• problem management which can trigger automatic tests during service problem isolation. <br/>• service supervision, performance & quality management to acquire data necessary to analyze the running services.<br/>Service Test Conducting functionalities include:<br/>• Verifying test authorization and quota management: checks depending on the initiator of the test request if it is authorized and if limitation applies in terms of test quota (linked to resources limitation or other technical constraints)<br/>• Carrying out test priority: the priority of a test for customer care directly in front of a user is higher than for scheduled bulk test campaign<br/>• Managing test scheduling:<br/>  - can be triggered to schedule test (unitary, bulk) regularly (every week, every month…)<br/>  - should take into account the impact of the test on the services in order to limit it. For example, a test on a TV service can be programmed at 2 am in order to not disturb the usage of the user.<br/>• Managing bulk test: as well as unitary test with flexibility concerning the criteria (category of service, geographical area, type of customer…)<br/>• and setting up the test context and configuration<br/>• Test execution with access to the various data required to perform service testing<br/>  - During the execution of a service test, resource tests can be executed to recover information (like inventory data)  needed to calculate the service test result<br/>  - Data collected during service test can be inventory data (for example in IS inventory) or data related to services coming from service platform and equipment like network equipment or user devices.<br/>  - Test execution produces a test result that may contain a raw result and an enrichment of this result depending on the service test definition and associated rules.<br/>   For example: for a internet test the raw result can be the associated bandwidth and an enrichment can be done depending on the user access type (fiber, xdsl…) to evaluate if the result is suitable or not.<br/>• Managing service test scenario: service test management must manage service test scenario with the capacity to trigger additional service tests depending on the results of previous executed tests of the test scenario.<br/>  - In addition to rules, test scenario can be designed to use signature templates data to identify the existence of disruptive events on services that usually correspond to an aggregation of disruptions on resources like water on cable, electrical interferences with other equipment…<br/>