Ticket #1017 (closed defect: invalid)
No testing strategy
|Reported by:||cjg@…||Owned by:||cjg|
|Priority:||Intend to||Milestone:||EPrints Wishlist|
Description (last modified by cjg) (diff)
We currently do not have a formal testing strategy.
Potential types of test: * individual functions (unit tests) * individual features (eg. sending email) * tasks (eg. creating and depositing an eprint)
Unit tests for every function is a huge task, but they can be added steadily. What we do need is a framework for these tests. It will almost certainly require an install of EPrints or a copy symlinked from CVS.