Does anyone know how to stress test a GUI?
Specifically, how to generate/consume GUI bandwidth in measurable
increments?
Is it possible to create a testing tool/application that would send a stream
of Photon events to be consumed by the GUI under test?
Moving the mouse generates/consumes GUI bandwidth, and would be a viable
method if it could be accomplished measurably, i.e. under program control.
Has anyone done this?
Gordon Freeman <gf@bigfoot.com> wrote:
Does anyone know how to stress test a GUI?
Specifically, how to generate/consume GUI bandwidth in measurable
increments?Is it possible to create a testing tool/application that would send a stream
of Photon events to be consumed by the GUI under test?Moving the mouse generates/consumes GUI bandwidth, and would be a viable
method if it could be accomplished measurably, i.e. under program control.Has anyone done this?
I don’t know if this has been done – but at the region level, you can
both record & emit Photon events.
You can create an transparent sensitive window, and record a whole bunch
of events (from a user doing things), then emit them back later, re-ordered,
faster or slower, to stress-test things.
Or, you can generate your own events from scratch and emit them.
What I don’t know is if such a thing has been written already – but due
to the architecture of Photon, it shouldn’t be too hard to do.
One could even write a regression tester, that uses a pre-recorded stream
of events, and a screen capture of what the result should look like, then
compares that to the newly tested version, and if there are differences,
flags them.
David Gibbs
QNX Training Services
dagibbs@qnx.com
“David Gibbs” <dagibbs@qnx.com> wrote in message
news:cjufpt$gmm$2@inn.qnx.com…
Has anyone done this?
I don’t know if this has been done – but at the region level, you can
both record & emit Photon events.You can create an transparent sensitive window, and record a whole bunch
of events (from a user doing things), then emit them back later,
re-ordered,
faster or slower, to stress-test things.Or, you can generate your own events from scratch and emit them.
What I don’t know is if such a thing has been written already – but due
to the architecture of Photon, it shouldn’t be too hard to do.One could even write a regression tester, that uses a pre-recorded stream
of events, and a screen capture of what the result should look like, then
compares that to the newly tested version, and if there are differences,
flags them.
Thanks for your response David.
I just found an example of this, called “EventWatch”, on Quics:
ftp://quics.qnx.com/usr/free/qnx4/photon/utils/
This would be a good starting point for a stress testing application.