Case Study

Cigna – (Performance Testing)

Benefits

  • Instituted an effective knowledge management methodology to reduce training time.

  • Business Process approach for easily defining the key business flows.

  • Thorough understanding of application flows enabling testers for faster execution.

  • Quick turnaround in executing the test scenarios.

  • Clearly defined roles and responsibilities:

    • Subject Matter Experts (SME's).

    • Create Business Process test cases.

    • Execute and analyze.

      • Clear demarcation of every test artifact, for easy maintenance.

      • Smoke.

      • Regression.

      • Acceptance.

      • Low cost solution with total (low) cost of ownership.

      • Comprehensive test reports.

      • Logs for easy debugging.

Fast Facts

  • Project Duration: 11 weeks

  • Technology: Performance Testing

About client

Client is a global health service company, dedicated to helping the people it serves improve their health, well-being and sense of security. They help their employers and organizations around the world protect their workforces. Its integrated plans and services combine with proven health and well-being programs to help employees stay healthy and on the job. They had partnership with brokers and consultants to develop programs to fit their unique needs of their employer and individual clients. It also provides individuals and families with the coverage and tools they need to improve their health, well-being and sense of security-and lower their medical costs.

Challenges

  • To many applications for testing in limited time period.

  • Manage multiple vendors and teams across time zones.

  • Non availability of applications on time for testing.

  • Non availability of defect tracking tool.

  • Incomplete deployment of applications leading to waste of time in time in testing.

  • Incorrect configuration of the products and master data.

  • Lack of clarity in the business processes.

  • Insufficient time to execute approx 8000 test case estimated during the requirement analysis phase.

  • Lack of complete test coverage and incomplete execution and analysis of the regression test bed caused risks to the quality of the data.

  • Financial impact because of too many products and many more variations to certify from a QA perspective.

  • Complexity in handling Functionalities, Products, Transactions, various other product categories.

  • Complexity in using test data to validate different product lines.

  • Co-ordination issues between SMEs, SIT and UAT teams.

  • Too many combinations, limited time to test.

  • Delayed Testing schedules and product releases.

  • Dependency on few critical resources.

  • End to end integration testing of a complex business application environment.

  • Test planning, strategy and execution and coordination with other vendors.

  • Defect reporting on a daily basis.

Solution

  • Breaking the testing requirements in multiple phases.

  • Defining the approach of “Positive Testing” to achieve the defined time lines.

  • On the fly features to test and understand the impacted transaction.

  • Smoke testing to identify potential issues in navigational, user related and security issues.

  • Intuitive handling of various functionalities: New Business, Underwriting, DMS, Sales, Collection.

  • Blended approach of Module & Integration testing recommended to meet the deadlines.

  • Suggesting the correct setup of Products and Masters in place.

  • Testing team and client SME’s to work cohesively to achieve the quality and time to market.

  • A mix of user acceptance testing and functional testing.

  • User acceptance support.

  • Test cases based on business scenario.

  • We integrated various business processes and channels, leveraged reusable frameworks and components for better response to business requirements and improved financial predictability.

  • Developed enhanced status reporting on daily/monthly metrics dashboard to track progress.

  • Meeting higher management on weekly basis on progress update and way forward.

  • Interaction with vendors for discussing the defects and work around till final fix is provided.

  • Usage of “Quality Gates” mechanism to clear passage from module level to integration level.

Methodology

Key stages for ATT

Stage 1 – Study of Existing state & Establish Quality Gates for Modules

In this stage quality assessment of the module is done in terms of and arrive at defining “Fit for Purpose” before proceeding ahead

  • Test case coverage.

  • Build Stability & Ease of Integration.

Stage 2 - Test Case Assessment & Preparation

  • Test cases required for the Acceptance stage are built up.

  • Usage of existing cases is key to saving overall effort.

Stage 3 - Test Execution

  • Multiple cycles of execution are done to get the systems into “Fit for Purpose” stage and achieve Go-Live.