Conversion Approach And Testing Approach in Agile Testing Process Agile Testing

A complete change to the conversion approach and testing approach resulted from the analysis of the first iteration.Fundamental to this approach were the following:

  • Very short iterations –conversion of one form per iteration.This allowed very early feedback on the approach and allowed early demonstration to users that something was happening.
  • Continuous integration –With such a large code base, it was essential to keep all converted code building all the time.Each build also invoked unit tests and automated functional tests.
  • Complete build per iteration –Each iteration produced a build,creating confidence that the build process would deliver the final system and allowing any correction of the build process to happen in very small increments.
  • Test first design and coding–Unit tests using NUnit were built into allcode changes and incorporated into the continuous integration build process.
  • Testing what has changed –Functional tests focused on testing the changes made to correct conversion problems rather than testing the user functions.These focused on testing the user interface behavior of controls/forms that required changes.
  • Identifying generic solutions –This involved the identification of solutions to common classes of problems. An enhanced version of the Microsoft conversion tool from ArtinSoft was used to reduce the number of conversion problems,including automated conversion of a number of popular third-party controls. Also, the adapter pattern was used to wrap .NET controls and provide COMcompatible interfaces to avoid code changes.
  • Automated application of generic solutions –The generic solutions were coded as batch edit commands and applied automatically using scripts.As each occurrence of a problem was addressed, either an existing solution was applied or a new solution was created.
  • Automated conversion from VB6 label–When performing a build, a subset of a label of the VB6 code base was converted to VB.NET by running the ArtinSoft conversion tool and then running the SED batch editor conversion scripts.This allowed development of the VB6 code base to continue in parallel with the VB.NET conversion, as the application of all conversion fixes was automated.
  • Optimization of forms to convert–Through an analysis of the occurrences of conversion problems,an optimal set of forms was chosen that covered all known problems. A milestone in the project was completing the conversion of these forms,because this represented finding a solution to all the known conversion problems. Through the use of generic solutions, once this set of forms was converted, the solutions could be applied to all remaining occurrences of the conversion problems.
  • Sample testing –This involved the sample testing of occurrences of generic solutions;once the initial optimal set of forms was converted and tested,the remaining occurrences of conversion problems would not all be tested.A sample of the occurrences would be tested to ensure the generic solutions worked when applied to different occurrences.

All rights reserved © 2018 Wisdom IT Services India Pvt. Ltd DMCA.com Protection Status

Agile Testing Topics