<< Sequential Consecutive Database Updates | Test project-level managers >>

Response Time Trends for Key Pages

Exemplar

Figure 16.7 Response Time Trends for Key Pages

Additional Considerations

Points to consider when reporting trends include:
·

Trends typically do not add value until there are at least three measurements.
Sometimes trends cannot be effectively detected until there are more than three
measurements. Start creating your trend charts with the first set of data, but be
cautious about including them in formal reports until you have collected enough data
for there to be an actual trend to report.

Share trends with the technical team before including them in formal reports.
This is another generally good practice, but it is particularly relevant to trends
because developers, architects, administrators, and DBAs often will have already
backed out a change that caused the trend to move in the wrong direction before they
are able to compile their report. In this case, you can decide that the trend report is not
worth including, or you can simply make an annotation describing the cause and
stating that the issue has already been resolved.

Questions to Be Answered By Reporting

Almost every team member has unique wants, needs, and expectations when it comes to
reporting data and results obtained through performance testing. While this makes
sharing information obtained through performance testing challenging, knowing what
various team members expect and value in advance makes providing valuable
information to the right people, at the right level of detail and at the right time, much
easier

All Roles

Some questions that are commonly posed by team members include:
·

Is performance getting better or worse?

Have we met the requirements/service level agreements (SLAs)?

What reports are available?

How frequently can I get reports?