dogtail-devel [Bug 318531] Support dogtail scripts in GNOME tinderbox

["jhbuild (bugzilla.gnome.org)" <bugzilla-daemon bugzilla gnome org>]

Do not reply to this via email (we are currently unable to handle email
responses and they get discarded).  You can add comments to this bug at
http://bugzilla.gnome.org/show_bug.cgi?id=318531
 jhbuild | module sets | Ver: unspecified

Dave Malcolm changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #53313|accepted-commit_now         |committed
             Status|                            |



------- Additional Comments From Dave Malcolm  2005-12-07 20:01 -------
(i) Re:  attachment 53313:
I've committed it as it's a step in the right direction, and AIUI shouldn't
break anything.

However at the moment I can't build pyspi under jhbuild.  IIRC if I build
without bootstrapping, the module doesn't know where it should be installed
(perhaps we need to transition the project to the GNU autotools?), and if I
build with bootstrapping it fails earlier since it needs Pyrex (perhaps add this
as an explicit dependency in the jhbuild file)

(ii) re including the tests inline in the modules:
IIRC our view at the QA BOF at the 2005 gnome summit was that we wanted to allow
"out-of-band" tests.

There are a few reasons for wanting to allow out-of-band tests:
  (a) not all tests relate to a specific module.  Think of integration tests
such as starting a session and measuring startup time, clicking on every
launcher in the panel and checking that every app starts, that help works in
every app, etc.  Basically anywhere involving more than one app. 
  (b) "inline" tests that require dogtail or LDTP would add a dependency on
dogtail/LDTP to each module as a whole (and hence on e.g. python) and I think
neither of our testing projects are mature enough for the various gnome modules
to want that.
  (c) LDTP is storing its tests in a separate repository anyway, and so I'm
guessing that it's going to be easier for them if jhbuild is set up to allow
out-of-band tests
  (d) putting my Red Hat hat on (I suspect this view is shared by other
distributions packaging GNOME) we'd greatly prefer tests to be in a separate
tarball from the source tarball, since it means we can run tests on a package in
a separate environment from our build environment, without having to continually
do rebuilds, or having to hack the tests into a separate module.

Of course nothing rules out individual module maintainers from adding
dogtail/LDTP test case into their own modules, what I want is an out-of-band
location for them to live 

Does this make more sense?

------- You are receiving this mail because: -------
You are watching someone who is on the CC list.