Testing for Agile Software Development

　　Testing for Agile Software Development  软件测试

　　In this tutorial you will learn about Testing for Agile Software Development - Background, Understanding Agile Software Development, How is Testing approach different in an Agile Development Scenario? What to test? Typical bugs found when doing agile testing? Steps Taken to Effectively Test in Agile Development Methodology, Ensuring software test coverage and Summary

　　Sponsored Links

　　Background:

　　To understand the Testing Process in an Agile Development Methodology, it is important to understand the Agile Development paradigm.

　　Agile Development paradigm is not very new. Although the Agile Software Development Manifesto came into existence in February 2001, the concepts existed long before that and were expressed in different ways. Spiral Development Methodology is one such example.

　　Understanding Agile Software Development:

　　The Agile Software Development primarily focuses on an iterative method of development and delivery.

　　The developers and end users communicate closely and the software is built. A working piece of software is delivered in a short span of time and based on the feedback more features and capabilities are added.

　　The focus is on satisfying the customer by delivering working software quickly with minimum features and then improvising on it based on the feedback. The customer is thus closely involved in the Software Design and Development Process.

　　The delivery timelines are short and the new code is built on the previous one.

　　Despite this, high quality of the product cannot be comprised.

　　This creates a different set of challenges for Software Testing.

　　How is Testing approach different in an Agile Development Scenario?

　　The Testing Strategy and Approach in Agile Development could be very different from traditional bureaucratic methods. In fact it could vary with project needs and the project team.

　　In many scenarios, it may make sense to not have a separate testing team.

　　The above statement should be understood carefully. By not having a testing team we do not consider testing to be any less important. In fact testing can done more effectively in short turn around times, by people who know the system and its objectives very well.

　　For example in certain teams Business Analysts could be doing a few rounds of testing each time the software version is released. Business Analysts understand the Business Requirements of the Software and test it to verify if it meets the requirements.

　　Developers may test the software. They tend to understand the system better and can verify the test results in a better way. Testing for AGILE Software Development requires innovative thinking and the right mix of people should be chosen for doing the testing.

　　What to test?

　　Given the relatively short turn around times in this methodology it is important that the team is clear on what needs to be tested. Even though close interaction and innovation is advocated rather than processes, sufficient emphasis is given to the testing effort.

　　While each team may have its own group dynamics based on the context, each code has to be unit tested. The developers do the unit testing to ensure that the software unit is functioning correctly.

　　Since the development itself is iterative it is possible that the next release of code was built by modifying the previous one. Hence Regression Testing gains significant importance in these situations.

原文转自：http://www.ltesting.net