Telecommunications

Project overview:

One of our major partners requested us to spearhead their test automation efforts. They already bought HP QTP, and would like dedicated resources to create a framework.

Challenge:

This is the first time that our client will fully invest in developing and implementing an automation framework. The proponents were challenged by management to ensure that the solution can cater to a significant number of ongoing development projects, which means compatibility with different platforms and a process that can accommodate different business units.

Solution:

Our automation engineers developed a hybrid framework (data-driven, keyword-driven). A methodology for development was also strictly followed, which starts with a request, followed by requirements gathering (a demo on the manual testing process for the system) and a readiness assessment (how ready is the system for automated checks; a checklist survey is filled-up), scoping (test cases feasible for automation), and then creation of the automation test plan. If the plan and timeline is accepted, scripting will commence. The scripting effort is considered the same as a standalone development project, with coding conventions and best practices, testing and debugging.

A user acceptance test will follow, and if passed, the test libraries will be deployed for execution. Requests to execute will come from the originating project team, and reports on the results are sent per iteration of test.

Maintenance and optimization of the scripts is also done regularly, following a change-management procedure.

This process has been continuously applied in the last 4 years, undergoing refinements and improvements to the framework and to the automation process.