Added by Eric GROISE, last edited by Eric GROISE on Oct 05, 2007  (view change)

Labels:

Enter labels to add to this page:
Wait Image 
Looking for a label? Just start typing.

We do A LOT of tests during Octopus development and we have 2 levels of automated tests :

  • Unit testing
  • Fitnesse testing

We also have deployement tests done using Vistual Machines in order to ensure that Octopus works fine on all supported configurations (MSDE, SQL Express...)

NUnit tests

We use NUnit as unit testing framework. These tests are automatically run by the Cruise Control build factory every time a developer commits source code to the subversion repository.

If you take a look to the last build report you can view all run Unit tests in the Nunit Details report.

During development we also run locally these NUnit tests in order to make sure we do not commit source code that raises regression.

At 24/09/2007 each build runs 1146 unit tests.

Fitnesse tests

We also run functionnal tests every time we release a new version of Octopus.

Fitnesse wiki is here : http://octopusfit.octo.com/FitNesse.OctoPus

If you want to learn about Fitnesse take a look to : http://fitnesse.org/FitNesse.TwoMinuteExample

At 24/09/2007 fitnesse runs 122 functional scenarios wich represents 19891 assertions.