Lessons from agile testing approach Agile Testing

Overall,the results of the use of an agile testing approach were good, and the agile approach was seen to have worked well.

In particular,the co-location of the customer integration team and testers worked very well, with the customer able to resolve environmental issues (availability of applications, logins, user profiles, security issues,etc.) that emerged during the testing.A useful side effect of this has been an increase in the awareness of the integration team of the role and need for effective and efficient testing of the applications they were deploying into their infrastructure (rather than assuming the vendors would resolve any issues) and a greater respect for the testing role.

The agile approach was applied tactically and coexisted with a much larger traditional approach and was able to provide effective results to specific concerns in a timely manner.

The approach of using architectural analysis rather than business analysis to define test cases was understood by all technical staff on the project and led quickly to detailed proposals for intervention in the system to increase capacity,to limit the impact of running over capacity and to improve long-running stability.

Template-based test plans, test cases, reports and so forth and reuse of test cases worked well, both in simplifying the testing process and in articulating the approach to senior management. They also allow for significant reuse when new versions of the applications are to be deployed onto the platform.

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

Agile Testing Topics