The customer had developed a best-in-class image asset management software, which enabled users to store, query, and share a large number of images and data. It could improve efficiency and collaboration both within and outside the organization while protecting and storing valuable images. The software could implement image search and comparisons using complex algorithms.

However, due to continuous enhancements, the software had grown complex and its regression testing had become a challenge. Despite this, extensive regression testing was a must to ensure stability of the software for multiple customers. All these posed unique challenges to the customer.

Following a complete review of the software, Tavant decided to automate the process of its regression testing.

Since there was no documentation on the software, Tavant began with daily conference calls with the customer to understand the software. It had detailed discussions with and sought clarifications from the customer teams. Thereafter, it documented its understanding, converted the documents into requirements and placed them in TestLink -- a tool for documenting requirements and managing the testing lifecycle.

Tavant used its proprietary framework developed on HP Quick Test Professional (QTP) and followed the Functional Decomposition approach for automation of regression testing. It delivered an Automation Test Plan, detailing out the scope, approach, effort, schedules/milestones and deliverables to the customer.

Tavant prioritized critical modules that needed to be automated in phase 1 of the project and identified team members (lead/engineers) skilled in TestLink. Subsequently, the Tavant team developed test cases based on the documented requirements.

Tavant also created the infrastructure and configuration required for executing automated scripts. It provided an interface to users that allowed them to choose a module, sub-component, or a set of tests to execute.

Automation of regression testing by Tavant helped the customer reduce test cycle time as well as significant costs incurred on regression testing. The end result was clean, stable software.