Software performance testing: There is no 'I' in 'team'

"When everyone on the team does his job and works together to support one another the net result is almost always dramatically more desirable"

It makes more sense to think about performance testing and tuning as a team sport in which the following takes place:

• The team works together collaboratively
• The team is informed and involved in the decision-making process about what to test next
• The team generates ideas about how the performance tester can help isolate performance issues using the tools that are exclusively available to him
• The team finds out about performance issues in real time
• The team gets to work together to help find functional errors under load
• The members of the team who best understand the various components of the system under test get to participate in analyzing the results data in real time
• The performance tester gets to sit next to the developer during the tune-retest-retune-retest cycle (frequently shortening that cycle from days or weeks to hours)
  Maybe I should rethink my conference

When everyone on the team does his job and works together to support one another the net result is almost always dramatically more desirable.

Like the guide, then subscribe by entering you mail id to get updates daily
Don't miss any article:Get it by E-mail