Overview The Agile Test-driven Methodology Experiment Agile Testing

Two factors defined the testing challenge facing the conversion project:

  1. A regression test suite did not exist for the system to verify the migrated software.As part of gaining user buy-in to the conversion project,development of an automated regression test suite had been promised as a deliverable.
  2. Development of the software would continue during the conversion because a change freeze was unacceptable to the users.

The system in question has been continually maintained and enhanced for over eight years in small increments,relying on informal developer and user acceptance testing.Whereas this approach has been successful in delivering a quality system,there has been no use of automated testing,and no formal regression test suite has been produced.

This presents a challenge when considering conversion from VB6 to VB.NET. It was clear that this would involve wholesale change to a high percentage of the code base. The existing testing approach was not designed to cope with this type of change. The business need is to ensure that the converted system functions properly and can be cut over with no business interruption. However, because no direct business benefit exists in terms of new features, all costs involved in the conversion are seen as an overhead.

The application is organized as a fat client/fat server system.The server accounts for around 80,000 lines of code.It abstracts the underlying database and includes business logic. The client code, around 120,000 lines, includes around 200 forms and also includes business logic.The behavior of the system is highly data-dependent.


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

Agile Testing Topics