Trecx:QualityPlan

From Bodington Wiki

Jump to: navigation, search

Back to TReCX

Contents

Statement from bid document

We will adopt an extreme programming (XP) approach to development and use Eclipse 3.1 for the IDE which will enforce good practice (ie, indentation / Javadoc). We will use JUnit test harnesses for both the service and client code. Where appropriate we will also use HTTPunit and XMLunit.

SourceForge will be used to host the software; project documentation will either be held there or on the CETIS ELF site as appropriate. The forum, logging, RSS (news) and bug tracking facilities of these sites will be also used. We may also use the email list facilities of SourceForge if the forum appears not to be effective.

Notes from Warwick Bailey's OSMM talk

JISC expects:

  • functionality driven by requirements
  • low failure rates - they expect us to do load testing
  • robustness - they expect Junit tests
  • easy admin interface
  • support - good documentation and blogging from day 1

Commentary

We should follow the above as they represent good practise, in addition we should develop a quick-start version of the toolkit as this will help us attract more developers. As we are using the Exist XML database, this should not present any problems.

Methodology

Java classes

We will use the JUnit test harness when deveoping the Java classes

Web Service API

We will use HTTPClient to generate test cases of the messages. This should also be used for third parties to test that instances have installed cortrectly




Back to TReCX