Story

As a developer I find it far more efficient writing stories and utilizing Behaviour Driven Development & Living documentation to make sure the code is tested rather than individual JUnit tests. Utilising frameworks like JBehave, Cucumber etc allow developers to write Stories (like this one), add them to the test suite and write tests against the individual sections, this also aids reusability.

Details

Scenario

Why should BDD be used?

Given

OODT's procedural and workflow based design and utilization

When

Tests are written

Then

They could be described in stories and used to create living documentation and tests, this would also provide specifications for various components.

 

Scenario

We decided to use JBehave alongside JUnit

Given

OODT's existing test framework

When

JBehave would be implemented alongside existing JUnit tests

Then

It would provide an alternative method of end to end testing and segmenting tests into individual stories, these can also often be easier to imagine and write when adding new blocks of code.

  • No labels