You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 28 Next »

Table of Contents

The test plan covers all sub-tasks, bugs, improvements and new features of the 3.8.0 release.

Assigned items end with (Name of Tester). All other items need help ! 

See Fedora Release Process for more information.

Release-Candidate Installer

https://github.com/fcrepo3/fcrepo/releases/tag/v3.8.0-RC1

General system tests that need to be done for any release

Github commits pertaining to this release:  https://github.com/fcrepo3/fcrepo/compare/3.8.0-SNAPSHOT

All tests will be run with Java 7.

  • Installation and integration tests with Windows (7/8) + Derby (Scott Prater)
  • Installation and integration tests with Windows (7/8) + Oracle (Scott Prater)
  • Installation and integration tests with Windows (7/8) + MySql (Scott Prater)
  • Installation and integration tests with OSX + Derby (??)
  • Installation and integration tests with OSX + PostgreSQL (??)
  • Installation and integration tests with Linux + Derby (Scott Prater)
    RHEL6.5 + Fedora embedded Derby
  • Installation and integration tests with Linux + PostgreSQL (Scott Prater)
    RHEL6.5 + Postgres 9.2.3
  • Installation and integration tests with Linux + PostgreSQL + MPTStore ()
  • Installation and integration tests with Linux + MySql ()
  • Installation and integration tests on Debian in local directory (Ralf Claussnitzer??)
  • Rebuild RI and SQL with Mulgara + Derby (??)
  • Rebuild RI and SQL with MPTStore + PostgreSQL7 (??)

  • Swing Administrator tests - manual ()
  • Web Administrator tests - manual () 
  • RMI receiver tests - manual ()
  • GSearch sanity test w/messaging - manual ()
  • OAIProvider sanity test - manual ()
  • No longer builds nor runs with Java 6 (any platform) ()
  • fcrepo-1212: allow parameterized object status in REST create ()
  • Datastream range requests ()
  • Start with legacy-fs storage profile

Issue specific tests

Bugs

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Improvements

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Wiki updates

Put large warning in wiki that fedora.fcfg is deprecated, settings now in WEB-INF/classes/applicationContext.xml

#trackbackRdf ($trackbackUtils.getContentIdentifier($page) $page.title $trackbackUtils.getPingUrl($page))
  • No labels