Can Agile Testing Succeed in Complex Application Environments?
AlWagner 120000DGH6 Visits (3898)
In an ideal world, Agile teams are collocated. A collaborative world with open dialog where everybody is on the same page working to achieve a common goal of quickly delivering quality software with conf
In this real world, developers write and test their code sending their latest greatest code contribution off for testing. As the more common approach to testing is typically done through the UI, QA teams then wait for all the application components to be made available. Only then can they deploy the complete application and test the functionality end to end. Usually much later in the sprint. And as they have not been testing throughout the process, a large number of defects will be discovered. Defects which need to be fixed and could have been discovered earlier. This world really doesn't sound like one where continuous development and testing is the norm or where quality is shared by all team members. Sound more like a mini water fall hidden within the sprint. This is not Agile.
Now, there is lots of talk about ways to improve testing throughout the sprint and perhaps even more opinions as to what is the best approach or solution to help you. Bottom line is that you need to get to "Done" which includes testing the deliverable end to end prior to release. But with all of today's complex application environments and application dependencies resulting in development and test bottlenecks, how is this possible?
Join Monica Luke, Lifecycle Solutions Architect, IBM and Priya Raju, Senior QA Manager, Sandhata during this IBM webcast to learn how to drain the water from your development sprints. Take advantage of service virtualization to remove the software dependencies and continuously test application integrations throughout the development life cycle. Be able to declare you are Done and say it with confidence.