Understanding project goals - page two
A little over a year ago I met with another tester in town to provide advice on performance testing. I recently found the notes from the meeting in an old notebook. In the five pages of handwritten notes, I documented my understanding of the problem and how I would approach the project. Take these notes for what they are - sketches over the course of an hour or two as I asked questions and clarified the project. However, I thought they would be interesting to share.
The second page was an attempt to understand the goals of the performance testing.
They wanted to better understand their calls-per-hour capacity. They were also trying to determine how many licenses they needed of third-party software to support their anticipated load. As I took notes, I jotted down a couple of constraints and some additional details of a couple of key components/transactions.
The second page was an attempt to understand the goals of the performance testing.
They wanted to better understand their calls-per-hour capacity. They were also trying to determine how many licenses they needed of third-party software to support their anticipated load. As I took notes, I jotted down a couple of constraints and some additional details of a couple of key components/transactions.