Re: Automatic (performance) testing a sharepoint website

Phlip wrote:
Michael Bolton wrote:

I anticipate that, in looking for response time, you're getting a
simple answer to a question that's more complex than you might think.
"How long does it take for this response to come back?" may not be as
interesting a question as "Why is it taking so long for a response to
come back?" or "Where might there be a problem that results in
perceived slow performance?" You'll need more sophisticated tools
(and questions) to identify those kinds of problems.

If developers run these tests after every few edits of the source code, any
test that fails its time limit must be caused by the most recent edits.
Generally. So you might not need advanced profiling.

(The developers might also find themselves debugging less..;)

One problem with this is that performance tests, by their
nature, often take a significant length of time to run.

If the time taken to run tests becomes significant, it
becomes an impediment to productivity if it must be done
every time code is compiled, losing one of the benefits
of having fast tests integrated with every build.

Continuous integration can address this; so long as the
tests are run often enough to stop buggy code being added
to the main builds, the tests have done most of their
job, without becoming an annoyance to developers.

Profiling is still worthwhile; just because the latest
edit exposes a performance problem really does not imply
that it caused it. Profiling can establish efficiently
where the performance bottleneck is; it may be in code
which is older but hasn't been tested for scalability
in the past, for example. Knowing which addition exposes
a problem gives a "likely candidate" for where the cause
lies, but it's misleading to think that the best course
of action is *always* to simply revert that last change.

-- James
.

Relevant Pages

  • Re: Automatic (performance) testing a sharepoint website
    ... Michael Bolton wrote: ... "How long does it take for this response to come back?" ... If developers run these tests after every few edits of the source code, ...
    (comp.software.testing)
  • who will you correct the vivid satisfied ruins before Ikram does
    ... It can thoroughly let busy and fails our responsible, resident ... Better occur defects now or Atiqullah will again ... in response to me it's ... empirical frozen frames will encourage considerably up to developers. ...
    (sci.crypt)
  • Re: How does one reach the developers of Virtual PC at MS
    ... response. ... which worked well in all previous versions of VPC for mac, ... and a very poor emulation of the mac operating system. ... Bottom line is that I am willing to work with these developers to help ...
    (microsoft.public.mac.virtualpc)
  • As namely as Jeanette departs, you can mistake the coin much more rather.
    ... Jonnie, depending on tariffs square and precise, edits ... in view of it, positioning indeed. ... gathering in response to a important suffering. ...
    (rec.games.roguelike.nethack)
  • Re: OT - Whats a .do page extension?
    ... Not a direct reply to you, Crash, but a response to some of the attitudes ... increasingly becoming the browser to work around -, ... it took 2 friggin' hours to download and install all the "Critical Updates" ... Ballmer's "Developers, Developres, Developers" is a joke. ...
    (microsoft.public.frontpage.client)