...
A work plan has been decided in an IRC meeting on May 26th, 2010. The work has been divided in 3 parts:
- Single class Unit Tests. Ideal candidates would be classes such a DCDate. These can be easily tested in isolation. This sort of test, along with an appropriate way for maven to execute them will give the project, and DSpace, and early win. Hopefully it will encourage further tests to be created by other developers, and we could move towards an expectation of new code requiring tests like this before they are committed.
- Integration Testing, which requires a database to be present. This would ideally work with an embedded database such as hqsql or derby. We need to think about this a little more to decide how best to do this, and how it would interact with the new services architecture.
- Functional Testing using a tool such as selenium.
- Unit Testing (package org.dspace.content.*)
- Integration Testing
- Functional Testing
It's been decided they will be done in the same order. The aim is not to do tests for all the existing classes, but to create an infraestructure infrastructure the community can benefit from and can expand with its own tests.
...
- 26th May: 1st meeting in IRC, decide the tasks for the following weeks
- 26th May - 9th June: Unit testing for package org.dspace.content.* . Weekly status reports sent to the DSpace GSoC lists, and the dspace-devel list.
- 9th June: 2nd meeting in IRC (21:00 UTC, #duraspace channel) to assert status of unit testing integrations and to discuss where there project should head next
- 12th July (Mid Term Evaluation)
- 9th August (End of Term)
- 9th August - 16th August (Final Evaluation): code fixes and documentation related to the project
...