Book contents
- Frontmatter
- Contents
- Foreword by Bob Bartlett
- Acknowledgments
- 1 Introduction
- PART 1 REVIEW OF OLD-SCHOOL AND AGILE APPROACHES
- PART 2 EVERYONE IS DIFFERENT: AGILE CASE STUDIES
- 4 From Waterfall to Evolutionary Development and Test
- 5 How to Test a System That Is Never Finished
- 6 Implementing an Agile Testing Approach
- 7 Agile Testing in a Remote or Virtual Desktop Environment
- 8 Testing a Derivatives Trading System in an Uncooperative Environment
- 9 A Mixed Approach to System Development and Testing: Parallel Agile and Waterfall Approach Streams within a Single Project
- 10 Agile Migration and Testing of a Large-Scale Financial System
- 11 Agile Testing with Mock Objects: A CAST-Based Approach
- 12 Agile Testing – Learning from Your Own Mistakes
- 13 Agile: The Emperor's New Test Plan?
- 14 The Power of Continuous Integration Builds and Agile Development
- 15 The Payoffs and Perils of Offshored Agile Projects
- 16 The Basic Rules of Quality and Management Still Apply to Agile
- 17 Test-Infecting a Development Team
- 18 Agile Success Through Test Automation: An eXtreme Approach
- 19 Talking, Saying, and Listening: Communication in Agile Teams
- 20 Very-Small-Scale Agile Development and Testing of a Wiki
- 21 Agile Special Tactics: SOA Projects
- 22 The Agile Test-Driven Methodology Experiment
- 23 When Is a Scrum Not a Scrum?
- PART 3 AGILE MY WAY: A PROPOSAL FOR YOUR OWN AGILE TEST PROCESS
- APPENDIX A The Principles of Rapid Application Development
- APPENDIX B The Rules and Practices of Extreme Programming
- Appendix C The Principles of the Dynamic Systems Development Method
- Appendix D The Practices of Scrum
- APPENDIX E Agile Test Script Template
- Appendix F Agile Test Result Record Form Template
- Appendix G Agile Test Summary Report Template
- Appendix H My Agile Process Checklist
- References
- Index
10 - Agile Migration and Testing of a Large-Scale Financial System
Published online by Cambridge University Press: 26 October 2009
- Frontmatter
- Contents
- Foreword by Bob Bartlett
- Acknowledgments
- 1 Introduction
- PART 1 REVIEW OF OLD-SCHOOL AND AGILE APPROACHES
- PART 2 EVERYONE IS DIFFERENT: AGILE CASE STUDIES
- 4 From Waterfall to Evolutionary Development and Test
- 5 How to Test a System That Is Never Finished
- 6 Implementing an Agile Testing Approach
- 7 Agile Testing in a Remote or Virtual Desktop Environment
- 8 Testing a Derivatives Trading System in an Uncooperative Environment
- 9 A Mixed Approach to System Development and Testing: Parallel Agile and Waterfall Approach Streams within a Single Project
- 10 Agile Migration and Testing of a Large-Scale Financial System
- 11 Agile Testing with Mock Objects: A CAST-Based Approach
- 12 Agile Testing – Learning from Your Own Mistakes
- 13 Agile: The Emperor's New Test Plan?
- 14 The Power of Continuous Integration Builds and Agile Development
- 15 The Payoffs and Perils of Offshored Agile Projects
- 16 The Basic Rules of Quality and Management Still Apply to Agile
- 17 Test-Infecting a Development Team
- 18 Agile Success Through Test Automation: An eXtreme Approach
- 19 Talking, Saying, and Listening: Communication in Agile Teams
- 20 Very-Small-Scale Agile Development and Testing of a Wiki
- 21 Agile Special Tactics: SOA Projects
- 22 The Agile Test-Driven Methodology Experiment
- 23 When Is a Scrum Not a Scrum?
- PART 3 AGILE MY WAY: A PROPOSAL FOR YOUR OWN AGILE TEST PROCESS
- APPENDIX A The Principles of Rapid Application Development
- APPENDIX B The Rules and Practices of Extreme Programming
- Appendix C The Principles of the Dynamic Systems Development Method
- Appendix D The Practices of Scrum
- APPENDIX E Agile Test Script Template
- Appendix F Agile Test Result Record Form Template
- Appendix G Agile Test Summary Report Template
- Appendix H My Agile Process Checklist
- References
- Index
Summary
SYNOPSIS
This project describes the migration and testing of a large-scale complex business-critical financial software system from MS VB6 to VB.NET.
Since the project involved the direct conversion of the existing functionality of the system into VB.NET with no other enhancements planned, all the cost and effort involved were seen as overhead by the users.
Because of the need to reduce cost and timescales, an agile approach was selected for the project.
Introduction
My name is Howard Knowles and I am the MD of IT consultancy Improvix Ltd. With thirty-one years' experience in the IT arena covering the full software development life cycle, I have been involved in process adoption and improvement for the past fifteen years.
This case study describes a project in which I was engaged as the test manager by a leading international financial company to migrate their business-critical system from Microsoft VB6 to VB.NET. The project arose due to Microsoft's ending of support for VB6 and the difficulty in hiring (and keeping) VB6 developers to continue maintenance and enhancement of the system.
Overview of the Testing Challenge
Two factors defined the testing challenge facing the conversion project:
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.
Development of the software would continue during the conversion because a change freeze was unacceptable to the users.
- Type
- Chapter
- Information
- Agile TestingHow to Succeed in an Extreme Testing Environment, pp. 66 - 71Publisher: Cambridge University PressPrint publication year: 2009