Standardizing Web Performance testing
Pat Meenan
point on standardizing the interfaces for web testing components. We're
basically looking to standardize 2 sets of interfaces:
1 - Testing (automating a browser-based performance test)
2 - Results storage and retrieval
The presentation is really just a starting point for the conversation
for anyone interested to get on board before we start hashing through
the nitty-gritty details of the interfaces themselves. It would be
great if we could make enough progress on this to make a splash at
Velocity in June and open up web performance testing to all sorts of new
applications and uses.
I have a Google code project set up for the effort where we can document
the interfaces, track issues and store the code for language bindings,
etc: http://code.google.com/p/web-testing-framework/. The presentation
is also available for download in the project repository:
http://web-testing-framework.googlecode.com/files/Standardizing_Web_Performance_Testing.pdf
Thanks,
-Pat
Sergey Chernyshev
Sergey
Pat Meenan
Suraj Sundarrajan
I read through the presentation and am impressed about the
"PTaaS" (Performance Testing as a Service) idea using standardized,
easy to consume APIs. Sounds exciting. As an existing user of
Webpagetest, I would be more than willing to participate in this
effort. Count me in!
Regards,
Suraj Sundarrajan
http://performanceengineering.wordpress.com
Twitter: @perfengineering
On Feb 18, 3:57 pm, Pat Meenan <patmee...@gmail.com> wrote:
> No video, hasn't been presented anywhere (yet anyway). Glad to have you
> on board with helping out :-)
>
> On 2/18/2011 3:54 PM, Sergey Chernyshev wrote:
>
>
>
>
>
>
>
> > It's awesome - any way to see the video of the presentation?
> > In any case, I think I'm quite interested in participating with Show Slow.
>
> > Sergey
>
> > <mailto:patmee...@gmail.com>> wrote:
>
> > Ok, it's WAAAAAY overdue but attached is my proposal for a
> > starting point on standardizing the interfaces for web testing
> > components. We're basically looking to standardize 2 sets of
> > interfaces:
>
> > 1 - Testing (automating a browser-based performance test)
> > 2 - Results storage and retrieval
>
> > The presentation is really just a starting point for the
> > conversation for anyone interested to get on board before we start
> > hashing through the nitty-gritty details of the interfaces
> > themselves. It would be great if we could make enough progress on
> > this to make a splash at Velocity in June and open up web
> > performance testing to all sorts of new applications and uses.
>
> > I have a Google code project set up for the effort where we can
> > document the interfaces, track issues and store the code for
> > language bindings, etc:
> > http://code.google.com/p/web-testing-framework/. The presentation
> > is also available for download in the project repository:
>
> > Thanks,
>
> > -Pat
Coach Wei
lot of web performance testing happens on yottaa.com and thus we have
a lot of data. I have been wondering how to get more data and how to
make this data accessible to other folks (as an open Internet
performance data archive).
At minimum, I can give some feedback/comments. Cheers
--Coach Wei
Eddie Jaoude
Count me in too.
I had a thought (this might be for a future phase), in addition could we
have similar functionality to a few systems that already exist, that
allow users to download the software (in this case possibly a FireFox
extension) that they can leave running when not at their computer that
will get a list of urls from the main server and run the tests then
beacon back the results. This would possibly ease the load & will add
more diverse results from different locations and
systems/hardware/browsers etc - just a thought, I can explain more if
required.
Eddie.
Pat Meenan
build that exposes the standard interfaces so any apps built to the
standard interfaces would be able to consume the service. I imagine
there could be a bunch of different varieties of a service like that:
- A group of people get together and share testing capacity where each
member contributes a location and gets X credits in return to use across
the network
- Someone builds a service where people can get paid for use of their
computers (in free cycles) and the service resells that testing capacity
with a little bit of markup for the service itself
We're looking to offer reference and open source implementations for
some testing capabilities but the real win with standardizing on the
interfaces is that it opens up all sorts of possibilities for the actual
implementations (commercial and free) and hopefully opens up the
development on the application side when you can build an app to the
spec and be able to use it with ANY service implementation.
On 2/20/2011 9:06 AM, Eddie Jaoude wrote:
> Nice one!
>
> Count me in too.
>
> I had a thought (this might be for a future phase), in addition could we
> have similar functionality to a few systems that already exist, that
> allow users to download the software (in this case possibly a FireFox
> extension) that they can leave running when not at their computer that
> will get a list of urls from the main server and run the tests then
> beacon back the results. This would possibly ease the load& will add
Patrick Lightbody
--
We provide FREE website monitoring and load testing
http://browsermob.com
Patrick Lightbody
BrowserMob
(w) +1 (503) 828-9003 x 101
(m) +1 (415) 830-5488
> <Standardizing_Web_Performance_Testing.pdf>
Mark Pors
Looks great! At WatchMouse we are all for common industry interface
standards, and internally we think exactly along the lines of
measurements, storage, reporting/analysis as separate "systems".
We already use the HAR format for storage of our Real Browser
Monitoring and mult-step monitoring data, and have some ideas on how
to extend the HAR format.
A standard way to control browsers can also be very beneficial for all
parties, and we are willing to help you build a standard.
Looking forward to the next step. If you think it's useful I can start
by giving some feedback on the presentation.
Cheers,
Mark
--
Mark Pors
CTO
WatchMouse.com
Email: mark AT watchmouse
Web: www.watchmouse.com
Tel: +31 30 2522 400
www.twitter.com/pors
www.twitter.com/watchmouse (for news and support)
>
> Thanks,
>
> -Pat
>
> Standardizing_Web_Performance_Testing.pdf
> 259KViewDownload