Product Test Management::End to End Product Test Execution

End to End Product Test Execution Aggregate Function provides the necessary functionalities to manage the end-to-end execution of a test for an atomic product, either for manual or automatic testing, in order to ensure that this atomic product is working properly.

The end-to-end Product Test process will also rely on the Service Test Management and Resource Test Management functions depending on the association between the atomic product and the underlying service or resource.

The Product Test Execution is used by fulfillment and the assurance processes.
In the fulfillment process, the product test management can be triggered to launch acceptance tests to ensure that the product is working properly from the customer/user perspective and thus validate the end of the delivery process.

On the assurance side the product testing function is used during product problem isolation.

Product Test Execution functionalities include:

• Verifying test authorization and quota management: product test execution checks, depending on the initiator of the test request , if it is authorized and if limitation applies in terms of test quota (linked to underlying services/resources limitation or additional marketing constraints.) This applies especially for self-care test from users.
• Carrying out test priority : the priority of a self-care test for a user is higher than a back-office test.
• Retrieval of appropriate inventory data and setting up the test context and configuration.
• Test execution with access to the various data required to perform product testing.

  - A product test main actions will be to trigger service or resource tests depending on the product composition
  - Data collected during product test can be inventory data (for example in IS inventory) or data coming from service or resource tests.
  - Test execution produces a test result that may contain a raw result and an enrichment of this result depending on the product test definition and associated rules.
     For example: for an access product 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.

• Test results restitution: the restitution of the raw test results may depends on the test execution context data.

  - For the same test, depending on the initiator, the result restitution can be more or less detailed. The user/customer needs less technical details in self-care whereas customer care needs more and more details with higher care level.
  - However test result restitution levels must always be mutually consistent through all  the execution context

• Test results long term logging for offline data analyses. These analyses are done outside of Product Test Management.

• Possible reporting of test results back to the initiator of the test.