Continuous Integration

The peregrine project makes use of continuous integration (CI, Jenkins). All unit tests and performance tests are run after every commit to the svn system, and at least once per day.

Unit Tests

Unit tests in the system must cover at least 85% of all new code that is checked in to svn.

Performance requirements

The CI system measures

  • Time needed to load a test ontology and serve the first indexing result
  • Memory use before the first indexing
  • The time needed to index a subset of pubmed abstracts
  • The precision and recall on an old challenge set

These performance measures should not fail preset limits.

Last modified 11 years ago Last modified on Sep 2, 2011, 3:00:25 PM