by Justin Lankes
27. August 2010 18:36
We are currently QA (Quality and Assurance) and testing processes for our new PI version of SCOUT and an implementation for a new Carrier client. It's a somewhat complicated process and absolutely crucial for the success and adoption of the software. I just came across an article that does a pretty good job of explaining what it takes to implement new software in an insurance environment.
Highlights:
Step 1: Establish priorities. Identify the critical, most used, end-to-end business transaction pathways within the enterprise portfolio for the application.
Step 2: Develop the Architecture. Create an automation test architecture using the appropriate functional test tools. Make sure that the architecture supports the automated test script processing, while minimizing test script coding.
Step 3: Develop Test Case Templates. The templates are used for automating the application. Identify the key fields to vary in using data parameterization.
Step 4: Move the Data. Identify a full data migration solution from the legacy system, based on the necessary elements of the new application..
Step 5: Execute. Build and automate as many of the end-to-end test transactions for the application as possible, within the iteration’s user acceptance testing (UAT) schedules. Then, execute the test scripts (automated test cases) during UAT, report defects, and maintain a testing status dashboard for project status results.
This is a pretty good road map, but there are always exceptions depending on the environment. We strive to set expectations with every customer and make the transition as smooth as possible.
Subscribe