Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Work to be done by mid-term evaluation
  • Work to be done by end of GSOC
  • Documentation to be generated

Draft

The following draft outlines a proposal for the project plan. It has to be approved in a meeting with the community:

  • 24th May - 30th May: decide project plan.
  • 31th May - 20th June: test scaffolding for Maven that runs JUnit, JMock, HyperSQL, and Jetty for the tests. Create the 3 base classes: an Abstract Functional Test, an Abstract Integration Test, and an Abstract Unit Tests. Optionally there might be integration with Hudson/SONAR.
  • 14th June - 11th July: Add Contiperf to the set for performance testing. Start generating unit tests for DSpace API.
  • 12th July (Mid Term Evaluation): By this day a number of selected packages from DSpace API should have tests
  • 12th July - 8th August: Integrate Selenium into the scaffolding. Prepare tests for selected XMLUI functionalities.
  • 9th August: By this day we should have functional tests on the UI on selected functionalities
  • 9th August - 16th August (Final Evaluation): code fixes and documentation related to the project

Tools

  • The Continuous Integration server will be Hudson.
    • Wiki Markup
      SONAR 		\[[http://www.sonarsource.org/|http://www.sonarsource.org/] \] will be the code quality management 		tool
  • All tests will be run automatically by Maven
    • Embedded webserver will be Jetty
    • Wiki Markup
      Embedded database will be 		HyperSQL \[[http://hsqldb.org/|http://hsqldb.org/] \]
  • Functional Tests will use Selenium
  • Unit Tests and Integration Tests will use Junit
    • JMock will be used as mocking framework
    • HTMLUnit may be used if required
  • Performance Tests will use ContiPerf

...