Perhaps StoryText may be of use ??
http://texttest.carmen.se/index.php?page=ui_testing
http://texttest.carmen.se
Formerly "PyUseCase". Domain-language GUI testing for PyGTK,
Tkinter, wxPython, Swing and SWT/Eclipse RCP
*Breaking the coupling with a UI map*
Business people and users generally work in /use cases/. These are
high-level descriptions of a sequence of actions in a language they
understand: i.e. that of the domain. StoryText (formerly
"PyUseCase") is a tool that can record and replay such sequences and
thereby capture the /intent/ of the user. This will then allow
increased understanding, less dependence on the exact form of the
GUI and easier adjustment of existing tests without resorting to
clicking all the buttons again.
The basic mechanism is that we maintain a mapping between the
actions that can currently be performed with our GUI and statements
in this domain language. GUI changes then mean that this single
mapping needs to be updated, but the tests can remain untouched,
continuing to describe what needs to be done on the conceptual
level. This mapping takes the form of an external file in StoryText,
administered via a small GUI which prompts you to enter new names
for any actions that have not been seen before whenever appropriate.
*Checking the behaviour via logs and TextTest*
So StoryText can record and replay usecases for us. But how can we
check that what we see on the screen is correct? Most GUI tools do
this by allowing the test script to contain "assertions", which look
up some widget and check that some property of it is equal to a
hardcoded value. This creates yet more dependence on the current GUI
layout and cannot be "recorded" in any natural way, but has to be
programmed in after the fact. No "usecase" would naturally contain
this information : if it did it would turn into a test script.
This discussion isn't on the TextTest site for nothing. If we can
only get our application to produce a log of what the GUI looks like
we can check what it does by monitoring the contents of that log
using TextTest. StoryText does this for you: it generates an
ASCII-art type log of the current GUI appearance and monitors
changes to it. The application can supplement it with its own
logging as it wishes.
On 2/12/11 3:09 AM, staf-users-requ...@lists.sourceforge.net wrote:
> From: "Yashaswi S. Kumar" <yashaswi.ku...@sanovi.com>
> _____
>
> Hi All,
> I have a query. Usually STAF is used for CLI based testing. But I want to
> know if we can use any plug-in for UI automation using STAF/STAX.
> Kindly reply
>
> Yashaswi S Kumar
> Software Engineer
> Sanovi Technologies Pvt. Ltd.
> * yashaswi.ku...@sanovi.com
>
> ? <http://www.sanovi.com/> www.sanovi.com
> sanovi_logo_green_reverse
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure
contains a definitive record of customers, application performance,
security threats, fraudulent activity, and more. Splunk takes this
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
_______________________________________________
staf-users mailing list
staf-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/staf-users
