Version 2 (modified by cotto, 4 years ago)

reorganize a bit, add another test case

The GitHub Trac plugin doesn't come with any test suite, so the purpose of this page is to create a list of manual tests. This will give us some level of QA that the plugin conforms to a minimal level of quality in addition to serving as a list of features which have been successfully implemented.

Setup

<Insert setup instructions here. Postgres is preferable since that's what trac.parrot.org is running on.>

Test Results

test status at  25c365
clean install PASS

Test Cases

When running these test cases, use the below generic configuration options unless otherwise specified.

[github]
apitoken = <your token here> #get this from https://github.com/account
autofetch = 0
browser = http://github.com/parrot/parrot/commit/
closestatus = "closed"
enable_revmap = 1
long_tooltips = 1
svn_revmap = revmap

clean install (enabled)

The plugin can be installed onto a db which doesn't have an existing svn_revmap table.

Procedure:

  1. Start with the generic config options.
  2. Delete the svn_revmap db table, if it exists.
  3. Enable the plugin via Trac's config file (or via trac,ini).
  4. Verify that Trac shows the need for an upgrade.
  5. Upgrade Trac.
  6. Verify that Trac no longer needs to be upgraded.

clean install (disabled)

The plugin doesn't require the extra db table if revmaps are disabled.

Procedure:

  1. Start with the generic config options, but with enable_revmap = 0.
  2. Delete the svn_revmap db table, if it exists.
  3. Enable the plugin via Trac's config file (or via trac,ini).
  4. Verify that Trac does not need to be upgraded

TODO

  • import of an incorrect revmap fails gracefully
  • tooltips work (shortened and unshortened)
  • wiki syntax works
    • svn rev (valid, invalid)
    • git id (valid, invalid)
  • changeset url works
    • svn rev (valid, invalid)
    • git id (valid, invalid)
  • browser url works
  • github hooks insert correct data into the db