From: Sami Wagiaalla <swagiaal@redhat.com>
To: frysk <frysk@sources.redhat.com>
Subject: UI testing
Date: Thu, 08 Feb 2007 21:50:00 -0000 [thread overview]
Message-ID: <45CB9B24.8050400@redhat.com> (raw)
For the last little while I have been working on revamping the dogtail
tests.
They are now compatible with dogtail-0.6.1 found on fc6.
There is a new base class fryskTestCase, which contains code common
between all tests.
The tests survive the new druid modifications.
Mike will be writing a small test case for the modifications made to the
druid.
I have also been working on reducing the amount of output to the
terminal from the tests and from dogtail, so that it can be incorporated
into make check.
Although the dogtail tests are not part of make check i strongly
recommend that they be run whenever changes to the gui are made to
ensure that they always pass.
I also strongly recommend that from here forth we follow a test driven
development model with the gui. ie all new features should be backed up
with tests which prove that they work. Although this model feels a lot
slower the tests have a lot of benefit when we go through refactoring
and just general regression prevention.
reply other threads:[~2007-02-08 21:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=45CB9B24.8050400@redhat.com \
--to=swagiaal@redhat.com \
--cc=frysk@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).