Testing Solutions Case Study

Initially only ad-hoc testing was done for migration projects which resulted in more customer-reported defects in many areas. The test results were not tracked or compared with the existing applications. The Test Architect introduced a testing process by which more defects were identified during the testing phases and this resulted in good customer feedbacks.

Testing eDEN (ASP to .NET Porting Application)
eDEN (Electronic Data Enhancement Network) is an interface that helps pre-billers process insurance and payment claims. The goal was to test the functionality on the ASP.NET version and the new version of the product to be released without new errors and without affecting the existing functionality of the ASP version.

The Scope
Since there was no new functionality added during the upgrade of eDEN from ASP to ASP.NET, the system was tested against the baseline ASP production application.

Analysis
The defined acceptance criteria were “The converted application with ASP.NET pages and business logic converted to c# code must have the same performance and usability as that of the original system.”
Our dependency was on the existing application for generating test scripts and test cases. The initial constraint was that there was no clear requirement specification. Complete functionality of application was not known and the client did not supply functional test cases.

Solution
Unit Testing
We were involved in the unit testing process to identify the Test Parameters. They were identified by considering the technologies that have changed or been introduced with the .NET platform and ASP.NET. The actual changes made to the code were categories like API and Structural, Visual Basic, COM related, application configuration, security, state and database access related issues.

System Integration Testing
We defined an internal excel sheet to report the test status. This contained different scenarios, which covered areas of testing like GUI, Events and Functionality. The status of the complete system is measured using the excel sheet using the Pass/Fail status. This contains the status of each page with respect to the old system. Test Parameters were identified in the following manner:

Test Parameters	Pass definition	Fail definition
Features and functionality	The migrated .NET application has all the features and functionality available in the ASP environment.	The migrated application fails to provide similar features and functionality
Interoperability	The migrated application can access existing data or project files with minimum or no conversion	The migrated application fails to gain access to existing data or project files, and the conversion process is highly complicated
Performance	The migrated application meets the performance numbers defined in the scope of the project for the .NET platform	The migrated application does not meet the performance goal
Navigation	Links, Buttons, Lookup etc. shows no error and as in existing application.	Missing Links, error pages etc.
Events	Select, Save, Submit and Search options works as in the old system and fetches and stores the same set of data accurately.	Select, Save, Submit and Search options shows errors or data display not as in old system.

Improvements were made to the test report template so that it could be used across different projects.

Defect Prevention
Most of the areas which are likely to show errors were identified during unit testing.
Following categories of defects were identified during Unit Testing and thus prevented from going into the next phase of testing.

The bug count reduced dramatically during the system integration testing phase.

Most importantly, there were no customer reported bugs. Test Efficiency was 100%.

Test Defects for eDEN - (ASP to .NET Porting Application)