Scenario Driven Tests

home
unit testing
view story

2 Kicks

submitted by alexandrul.ct(475) 2 years, 7 months ago

I originally titled this blog post: Separate the scenario under test from the asserts. I intentionally use the terminology scenario under test, instead of calling it class or method under test. One of the main problem with unit testing is that we are torn between competing forces. One is the usual drive for abstraction and eradication of duplication, the second is clarity of the test itself. Karl Seguin does a good job covering that conflict. I am dealing with the issue by the simple expedient of forbidding anything but asserts in the test method. And no, I don’t mean something like BDD, where the code under test is being setup in the constructor or the context initialization method. I tend to divide my tests code into four distinct parts: * Scenario under test * Scenario executer * Test model, represent the state of the application * Test code itself, asserting the result of a specific scenario on the test model ...

add a comment |category: Unit Testing |Views: 6
Tweet