Common use of Software Component Testing Clause in Contracts

Software Component Testing. (a) Amdocs shall design, develop and execute the Unit Testing, Sub System Testing, Amdocs Integration Testing, System Testing, Conversion Testing, of the Customized Product, all components thereof and any other software to be provided hereunder in connection with each Release. The Parties shall conduct the Testing Activities (as defined below) in accordance with the process set forth below in order to verify compliance of the Customized Product with the applicable Impact Assessment Document and Amdocs shall provide such assistance and cooperation to Clearwire as is reasonably requested by Clearwire in connection with Interconnectivity Testing, Performance Testing, and Acceptance Testing in accordance with this Agreement, including Schedule B (collectively, the “Amdocs Testing Activities”). With the reasonable assistance of Amdocs, Clearwire shall conduct Interconnectivity Testing, Performance Testing, Conversion Testing and Acceptance Testing and assist Amdocs with System Testing of the Customized Product (collectively, the “Clearwire Testing Activities,” and collectively with the Amdocs Testing Activities, the “Testing Activities”). [*****]. For Amdocs’ System Testing activities, Clearwire shall provide Amdocs, at least [*****] prior to the commencement of the Acceptance Testing referred to herein below, with all of the test cases to be used by Clearwire for the Clearwire Testing Activities. For all Testing Activities, Amdocs will provide Clearwire, upon prior request, with access to any test case databases, test cases executed, test data used, defect logs, test entrance and exit criteria, and data from Amdocs’ data extraction tool, and any relevant test result documentation. Clearwire will also provide access to its defect management tool to all relevant Amdocs personnel for the purposes of fixing defects opened by Clearwire. In addition, and as a prerequisite for Amdocs’ ability to meet its respective undertakings including but not limited to the System Test exit criteria, Clearwire will provide Amdocs access to a mini RTB environment (i.e., access to Clearwire environments that includes non Amdocs applications (e.g. XXX-XX) and Third Party interfaces with real time connectivity. or any future system interfacing with the Customized Product) for Amdocs to conduct end to end testing as part of the System Test.

Software Component Testing. (a) Amdocs shall design, develop and execute the Unit Testing, Sub System Testing, Amdocs Integration Testing, System Testing, Conversion Testing, and Performance Testing of the Customized Product, all components thereof and any other software to be provided hereunder in connection with each ReleaseRelease of the Customized Product. The Parties shall conduct the Testing Activities (as defined below) in accordance with the process set forth below in order to verify compliance of the Customized Product with the applicable Impact Assessment Document Detailed Functional Specification and Amdocs shall provide such assistance and cooperation to Clearwire Nextel as is reasonably requested by Clearwire Nextel in connection with Interconnectivity Testing, Performance Testing, Interface Testing and User Acceptance Testing in accordance with this Agreement, including Schedule B (Roles and Responsibilities) (collectively, the “"Amdocs Testing Activities”"). With the reasonable assistance of Amdocs, Clearwire Nextel shall conduct Interconnectivity Testing, Performance Testing, Conversion Interface Testing and User Acceptance Testing and assist Amdocs with System Testing, Conversion Testing, and Performance Testing of the Customized Product (collectively, the “Clearwire "Nextel Testing Activities,” " and collectively with the Amdocs Testing Activities, the “"Testing Activities”"). [*****]. For Amdocs’ System Amdocs Testing activitiesActivities, Clearwire Nextel shall provide Amdocs, at least [*****] prior to the commencement of the User Acceptance Testing referred to herein below, with all of the test cases to be used by Clearwire Nextel for the Clearwire Nextel Testing Activities. For all Testing Activities, Amdocs will provide ClearwireNextel, upon prior request, with access to any test case databases, test cases executed, test data used, defect logs, test entrance and exit criteria, and data from access to Amdocs’ ' data extraction tool, and any relevant test result documentation. Clearwire will also provide access to its defect management tool to all relevant Amdocs personnel for the purposes of fixing defects opened by Clearwire. In addition, and as a prerequisite for Amdocs’ ability to meet its respective undertakings including but not limited to the System Test exit criteria, Clearwire will provide Amdocs access to a mini RTB environment (i.e., access to Clearwire environments that includes non Amdocs applications (e.g. XXX-XX) and Third Party interfaces with real time connectivity. or any future system interfacing with the Customized Product) for Amdocs to conduct end to end testing as part of the System Test.

Software Component Testing. (a) Amdocs shall will design, develop and execute the Unit Testing, Sub System Testing, Amdocs Integration Testing, and System Testing, Conversion Testing, of the Customized Product, all components thereof and any other software to be provided hereunder in connection with each Release. The Parties shall will conduct the Testing Activities (as defined below) in accordance with the process set forth below in order to verify compliance of the Customized Product with the applicable Impact Assessment Document and Amdocs shall will provide such assistance and cooperation to Clearwire Sprint as is reasonably requested by Clearwire Sprint in connection with Interconnectivity Integrated System Testing, Performance Testing, and Acceptance Testing in accordance with this Agreement, including Schedule B (Roles and Responsibilities) (collectively, the “Amdocs Testing Activities”). With the reasonable assistance of Amdocs, Clearwire shall Sprint will conduct Interconnectivity Integrated System Testing, Performance Testing, Conversion Testing and Acceptance Testing and assist Amdocs with System Testing of the Customized Product (collectively, the “Clearwire Sprint Testing Activities,” and collectively with the Amdocs Testing Activities, the “Testing Activities”). [*****]Amdocs must meet the System Testing exit criteria prior to Acceptance Test or as agreed between the two parties. The Parties will commence good faith discussions to set a System Testing exit criteria as well as the decisive factors that needs to be met by the Parties prior to the System Testing exit date. For Amdocs’ System Testing activities, Clearwire shall Sprint will provide Amdocs, at least [*****] prior days, or other timeframe as agreed upon by the Parties, to the commencement of the Acceptance Testing referred to herein below, with all of the test cases to be used by Clearwire Sprint for the Clearwire Sprint Testing Activities. For all Testing Activities, Amdocs will provide ClearwireSprint, upon prior request, with access to any test case databases, test cases executed, test data used, defect logs, test entrance and exit criteria, and data from Amdocs’ data extraction tool, and any relevant test result documentation. Clearwire Sprint will also provide access to its defect management tool to all relevant Amdocs personnel for the purposes of fixing defects opened by ClearwireSprint. In addition, and as a prerequisite for Amdocs’ ability to meet its respective undertakings including but not limited to the System Test exit criteria, Clearwire Sprint will provide Amdocs with reasonable access to a mini RTB the Sprint break-fix environment providing interfaces to, NMS, NPS, SMG (i.e.WLNP), access to Clearwire environments Paymentech, and EAI so that includes non Amdocs applications (e.g. XXXcan conduct end-XX) and Third Party interfaces with real time connectivity. or any future system interfacing with the Customized Product) for Amdocs to conduct end to to-end testing as part of production fixes or next build or release testing hereunder. Amdocs may not access or use any other or future systems interfacing with the System TestCustomized Product unless the Parties mutually agree to provide such access. In the event that Amdocs’s lack of access or use of any other or future systems interfacing with the Customized Product results in Amdocs’ inability to verify compliance of the Customized Product, Amdocs will identify the resulting risks to Sprint in the applicable Impact Assessment Document.

Software Component Testing. (a) Amdocs shall design, develop and execute the Unit Testing, Sub System Testing, Amdocs Integration Testing, System Testing, Conversion Testing, of the Customized Product, all components thereof and any other software to be provided hereunder in connection with each Release. The Parties shall conduct the Testing Activities (as defined below) in accordance with the process set forth below in order to verify compliance of the Customized Product with the applicable Impact Assessment Document and Amdocs shall provide such assistance and cooperation to Clearwire Sprint as is reasonably requested by Clearwire Sprint in connection with Interconnectivity Testing, Performance Testing, and Acceptance Testing in accordance with this Agreement, including Schedule B (Roles and Responsibilities) (collectively, the “"Amdocs Testing Activities”"). With the reasonable assistance of Amdocs, Clearwire Sprint shall conduct Interconnectivity Testing, Performance Testing, Conversion Testing and Acceptance Testing and assist Amdocs with System Testing of the Customized Product (collectively, the “Clearwire "Sprint Testing Activities,” " and collectively with the Amdocs Testing Activities, the “"Testing Activities”"). Amdocs must meet the System Test exit criteria prior to Acceptance Test or as agreed between the two parties. The Parties will commence good faith discussions to set a System Test exit criteria as well as the decisive factors that needs to be met by the Parties prior to the System Test exit date. The System Test exit criteria, inclusive of any applicable CPSs (as will be defined in Schedule C) will be agreed to no later than [*****]] days prior to the start of System Testing of the initial post-conversion Release, and will be implemented after the Final Conversion Milestone. For Amdocs’ ' System Testing activities, Clearwire Sprint shall provide Amdocs, at least [*****] days prior to the commencement of the Acceptance Testing referred to herein below, with all of the test cases to be used by Clearwire Sprint for the Clearwire Sprint Testing Activities. For all Testing Activities, Amdocs will provide ClearwireSprint, upon prior request, with access to any test case databases, test cases executed, test data used, defect logs, test entrance and exit criteria, and data from Amdocs’ ' data extraction tool, and any relevant test result documentation. Clearwire Sprint will also provide access to its defect management tool to all relevant Amdocs personnel for the purposes of fixing defects opened by ClearwireSprint. In addition, and as a prerequisite for Amdocs’ ability to meet its respective undertakings including but not limited to the System Test exit criteria, Clearwire Sprint will provide Amdocs access to a mini RTB environment (i.e., access to Clearwire environments that includes non Amdocs applications (e.g. XXX-XX) and Third Party interfaces with real time connectivity. EAI/EI, ASI, ePort, NMS, NPS, ServicePro, SMG, SPM, BCGI or any future system interfacing with the Customized Product) for Amdocs to conduct end to end testing as part of the System Test.