Re: dogtail-devel Proposal: splitting out the app wrappers into a separate tarball/repo, and how to organize dogtail-tests

[David Malcolm <dmalcolm redhat com>]

On Tue, 2006-09-12 at 13:04 -0400, Zack Cerza wrote: 
> David Malcolm wrote:
> > [cross-posting to build-brigade-list as I'd like feedback on how best to
> > structure this with jhbuild etc: see near the end of this post]
> >   
> [keeping this short and sweet because thunderbird blew up on my last 
> attempt to reply. yay for kwality!]
> > As Dogtail development moves on, I think we're going to want to
> > stabilize the core APIs, and eventually touch these as little as
> > possible.  
> >
> > However, one problem with this is the dogtail/apps/wrappers
> > subdirectory.  These are full of little workarounds for dealing with
> > specific apps (capturing these workarounds and distro-specific
> > differences in one place, rather than forcing them to be cut and pasted
> > throughout the tests) and I suspect we're going to want to continually
> > make changes to this part of the code, even when the rest of the
> > codebase is done.
> >   
> While the app wrappers can be a good idea in some situations, I've 
> always thought they belonged in a separate place (module or otherwise) 
> from the core of dogtail.
> 
> > So I think we should move this out of the main dogtail module and into
> > somewhere else.  Doing so will break much of the existing example code,
> > unfortunately.
> >   
> If we're moving the wrappers, we're going to need to move the examples 
> that use them.
> > What do we have here?  (lengthy, so skip this list to get to the
> > proposal)
> > - dogtail/apps/categories.py:  my feeling is that this was an
> > experiment, and can be moved elsewhere or got rid of
Removed: serves no good purpose

> > - dogtail/apps/wrappers/epiphany.py: short and somewhat hackish
Moved to dogtail-tests/appwrappers, removing categories references

> > - dogtail/apps/wrappers/evolution.py: quite a lot here, useful
Moved to dogtail-tests/appwrappers, removing categories references

> > - dogtail/apps/wrappers/gcalctool.py: not particularly useful
Moved to dogtail-tests/appwrappers, removing categories references (used
by one examples)

> > - dogtail/apps/wrappers/gnomepanel.py: appears to contain some
> > Fedora-specific code
Moved to dogtail-tests/appwrappers, removing categories references

> 
> > - dogtail/apps/wrappers/kicker.py: just a stub
> > - dogtail/apps/wrappers/konqueror.py: just a stub
> > - dogtail/apps/wrappers/mozilla.py: just a stub
I removed these

> > - dogtail/apps/wrappers/nautilus.py: short and somewhat hackish
Moved to dogtail-tests/appwrappers, removing categories references

> > - dogtail/apps/wrappers/yelp.py: short and somewhat hackish
Moved to dogtail-tests/appwrappers

For the examples subdirectory:
2006-09-13  David Malcolm  <dmalcolm redhat com>

	* examples/rhythmbox-test.py: removed

	* examples/nautilus-test-icon-view-collage.py: removed (moved to 
	dogtail-tests/nautilus)

	* examples/google-search.py: removed (moved to dogtail-tests/epiphany)

	* examples/gnome-panel-test-starting-every-app.py: removed (moved to 
	dogtail-tests/gnome-panel)

	* examples/gcalctool-test-fibonacci.py: removed (moved to 
	dogtail-tests/gcalctool)

	* examples/firefox-test-browsing-local-html-file.py: removed
	
	* examples/evolution-test-switching-components.py: 
	* examples/data/CAN-2005-0806.mbox: 
	* examples/evolution-test-survives-email-CAN-2005-0806.py: 
	* examples/evolution-test-sending-email.py: 
	* examples/evolution-test-first-time-wizard.py: 
	* examples/evolution-test-configuring-imap-smtp.py: 
	* examples/evolution-test-configuring-exchange.py: 
	* examples/evolution-test-composing-html.py: removed (moved to 
	dogtail-tests/evolution)

	* examples/crack.py: removed (never worked)

	* examples/abiword-test.py: removed (moved to dogtail-tests/abiword)

So we now have a few more subdirectories of dogtail-tests.  See:
http://cvs.gnome.org/viewcvs/dogtail-tests/

Only some of the tests within it are good to be run in a
jhbuild/autotest environment.  So I'll try to write the jhbuild modules
to wrap this up nicely.   Maybe we'll have to create some XML glue to
cover test suites?

[snip]

> 
> > We probably should store desktop-wide integration tests in another
> > subdirectory of dogtail-tests too.
> >   
> Agreed. We could just call it 'integration'. Maybe capitalize the 'I' to 
> make it stand out from the apps, also ;)
Not done yet.

Hope this helps
Dave