Widespread Fallacies of Load and Performance Testing in Agile

Widespread Fallacies of Load and Performance Testing in Agile
August 16 07:11 2016 Print This Article

The Agile methodology is all about speed and velocity. Therefore, it is surprising that load testing and performance testing are often executed only at the end of development process.

In fact, if load testing is deeply rooted in the testing process, then a software testing company is on the right track. Unfortunately, the execution of performance testing in Agile environment is often followed by numerous misconceptions.

2521cid_6bfa52a0bb43456fb976df92243c7bc72540ronpc

What Statements about Load and Performance Testing in Agile Are Incorrect?

  • Load testing is not iterative enough to be executed in Agile. It is incorrect because load testing, as well as functional testing, can be applied even to the smallest feature.
  • Performance testing in not quick enough to be executed in Agile. It is incorrect because performance testing can be narrowly targeted and automated.
  • There’s no point to perform load testing if the program code is in development. It is incorrect because performance issues are easier to fix at the early stages of development process.
  • Performance testing is a one-man job, while the Agile methodology is all about teamwork. It is incorrect because in Agile environment everyone is responsible for quality, so performance testing should be concern of every team member.
  • Manual load testing inhibits the overall test automation It is incorrect because some aspects of load testing can be successfully automated. Besides, not a single testing activity can be successful without a human perspective.

Taking all things together, the more integrated load and performance testing are, the more benefits they bring.

Related Posts:

About Article Author

view more articles
Nataliia Vasylyna
Nataliia Vasylyna

View More Articles