Performance Tester Diary - Episode 2
This is Chapter 2 of our journey of non-functional testing with Otto Perf. You can read Chapter 1 if you have missed it.
Authors note
The article is in the OctoPerf Blog pages
Otto had previously got to the point where he had defined a set of non-functional requirements and risk assessed these with the programme team. Otto had also had the opportunity to be involved in the design process which had allowed him to encourage the architects, and development leads to consider application performance as part of their architectural design principles. In this chapter we will follow Otto’s progress as he starts to consider how he is going to write his performance tests and how he will incrementally write tests in line with the development activity. Otto will also consider how he can make sense of the performance tests results he will gather and how he will ensure that the infrastructure is fit for purpose.