Resource Test Management::Resource Test Conducting

Resource Test Conducting provides the necessary functionalities to manage the end-to-end execution of a test for a resource, either for manual or automatic testing in order to ensure that this resource is working properly.<br/><br/>The Resource Test Conducting function is used in the following processes:<br/>• fulfillment, usually triggered within the framework of a test of service, for ensuring that the assigned resource works as designed.<br/>• fault management, which can trigger automatic tests during resource fault isolation.<br/>• resource supervision, performance & quality management to acquire data necessary to analyze the running resources.<br/><br/>Resource Test Conducting functionalities include:<br/>• Verifying test authorization and quota management: resource test 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 technician intervening at the user home is higher than for scheduled bulk test campaign<br/>• Managing test scheduling:<br/>  - Resource Test Conducting can be triggered to schedule test (unitary, bulk) regularly (every week, every month…)<br/>  - Resource Test Conducting should take into account the impact of the test on the resources in order to limit it. For example, a remote test on a user STB can be programmed at 2 am in order to not disturb the usage of the user.<br/>• Managing bulk test: resource test management must be able to execute unitary test as bulk test with flexibility concerning the criteria (for a category of resource, geographical area, type of customer…)<br/>• Retrieval of appropriate inventory data and setting up the test context and configuration<br/>• Test execution with access to the various resources required to perform resource testing. The test execution produces a test result that may contain a raw result and an enrichment of this result depending on the resource test definition and associated rules.<br/>  - For example: for a copper line test the raw result can be the conductivity of the line  and an enrichment can be done depending on conductivity templates calculated previously to evaluate if the result is suitable or not.<br/>• Managing resource test scenario: resource test management must manage resource test scenario with the capacity to trigger additional resource 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 resources like water on cable, electrical interferences with other equipment…<br/>• Test results restitution: the restitution of the raw test results may depends on the test execution context data.<br/>  - For the same test, depending on the initiator, the result restitution can be more or less detailed. Customer care or technician (ex: during a turn on test) needs more and more details with higher care level. <br/>  - However test result restitution levels must always be mutually consistent through all  the execution context<br/>• Test results long term logging for offline data analyses. These analyses are done outside of Resource Test Management.<br/>• Possible reporting of test results back to the initiator of the test.<br/>