The adoption of Agile practices during the development of a web application can deliver significant benefits, both in terms of an application’s quality and the enhanced productivity that generally results from the Agile development process.
One of the key purposes of Agile is to ensure that the current version of software functions as
expected, no matter what stage the development is at. To this end, every iteration of an Agile
project includes functional testing in the form of unit and acceptance testing. The early discovery and resolution of defects written into the code can help to guard against major unforeseen problems arising near project completion. After all, who wants to find a fault with the application weeks or even days before launch? This could severely compromise an application’s launch date (and delivery budget) and could cost a company dearly, in terms of overspend, lost revenue or business opportunities. There is even potential reputational damage to consider...
So, with a firm case in mind for functional testing during every iteration of an Agile project, together with an acknowledgement that this approach has become industry best practice, why do most developers apply a different logic when it comes to performance testing? In the latest issue of The Tester Graham Parsons discusses the risks and barriers surrounding performance testing in an Agile environment.
No comments:
Post a Comment