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
7 - Agile Testing in a Remote or Virtual Desktop Environment
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 case study deals with an agile approach specifically tailored toward the integration and deployment of packaged applications by or on behalf of enterprise customers.
The particular challenges of this case study were that no source code was available to the test team, timescales were very challenging, and the majority of quality issues were nonfunctional in nature.
Introduction
My name is Michael G. Norman. I have been involved with software test and performance for more than ten years, most recently having taken on the role as CEO of Scapa Technologies Ltd, a software tools vendor company. I was formerly involved in forming the Eclipse Test and Performance Tools Project (TPTP, formerly Hyades), which I ran in collaboration with colleagues from IBM and Intel and served on its Project Management Committee and the Board of Eclipse for around five years.
Scapa Technologies is involved with a range of testing engagements with its several hundred enterprise customers and tries to be methodologically neutral in the way it develops its tooling, making it applicable in both traditional and agile environments. In cases where it performs its own services, Scapa adopts a variation on the agile approach, which is tailored toward its predominant customer profile: integration and deployment of packaged applications by or on behalf of enterprise customers.
This case study describes a project where Scapa was engaged to test and produce very fast feedback on a set of applications that were being deployed by a telecommunications vendor via a remote desktop technology.
- Type
- Chapter
- Information
- Agile TestingHow to Succeed in an Extreme Testing Environment, pp. 49 - 52Publisher: Cambridge University PressPrint publication year: 2009