I was reading this blog post: http://www.shakie.co.uk/ramblings/feature-driven-development-riding-the-waves-of-change/ and came across the part about TestDox:
Direct quote (hence PHP):
Take the following test case as an example
class InvoiceTest extends PHPUnit_Framework_TestCase
{
public function testValueIsInitiallyZero() {
$invoice = new Invoice();
$this->assertEquals(0.00, $invoice->getValue());
}
public function testWillCloseAutomaticallyIfWholeValueIsPaid() {
$invoice = Invoice::getInvoiceById(1);
$invoice->payAmount(100.00);
$this->assertEquals(true, $invoice->isClosed());
}
}
In the TestDox format this would translate to:
Invoice
[x] Value is initially zero
[x] Will close automatically if whole value is paid
This would be great on some of the more agile projects I'm working on. I've been looking at TestDox and trying to track down NTestDox as I'm a .NET guy.
3 questions in one here:
Anyone find a copy of NTestDox? (I'm seeing page does not exist on the only useful results in google)
- http://www.emxtechnologies.com/ntestdox
- http://www.projectdistributor.net/projects/Project.aspx?projectId=87
Is generating documentation from your Unit tests a good plan?
Does anyone know of any other frameworks for .NET?