[GUSDEV] GUS 3.5 Testing

[Michael S. <msa...@pc...>]

Once 3.5 is frozen and the repository changes have been made, (i.e. Starting
tomorrow morning), we'll be ready to conduct final testing. All Supported
plugins will need to be tested in Oracle and Postgres.  This should
indirectly give the object layer a thorough testing as well.

The plugdev Oracle database will be wiped clean this evening and available
for testing, as will "gus", a Postgres database on hera.  Please let me know
if you need access to these.

When testing plugins, the following general parameters should be followed:

* No data should be loaded into the database except through the use of a
Supported plugin.  Supported plugins should not rely on data being loaded
with a Community plugin.

* No plugin should rely on software (including CPAN modules) that is not
included in the GUS distribution _or_ that is not documented in the
installation documents.  At present, that is limited to:  DBI, Parse::Yapp,
XML::Simple, XML::Parser, XML::SAX.

* Plugins should conform to the plugin development standards, especially in
areas visible to the end-user (i.e. Command line arguments or documentation)

* All plugins should be tested in commit mode.

* Plugins may be tested against a subset of a datafile for time issues, but
this subset should be representative of the datafile.  (i.e. the subset
should contain at least one record from the datafile in each format
represented by the datafile).

* All bugs/issues should be entered in the tracker unless they are
immediately fixed.  As gus_commit emails are sent, you should make sure your
working copy of the repository stays updated by doing a svn update.

To track our progress testing plugins, I propose that we use subversions
properties system.  Thus, when you have finished testing a plugin and are
satisfied with the results, you should do:

svn propset tested 'true' plugin_name.pm  (replace plugin_name with the name
of your plugin.  This example assumes you're in the plugin directory-
otherwise use the full path).

You must commit after using propset.

Please let me know if you have any comments or suggestions.

--Mike