DISQUS

Community Page on DISQUS

what is this?

Thinking inside a bigger box

Jump to original thread »
Author

Testing: Avoid setUp and tearDown

Started by jhannes · 3 months ago

In Let your examples flow, Dan North describes how “Don’t Repeat Yourself” (DRY) isn’t necessarily the most important guideline for tests. While I agree with his conclusions, I think the DRY principle is still extremely important for tests.
% ... Continue reading »

2 comments

  • Anders Norås

    4 months ago

    Agreed! I often find myself refactoring setup methods to factories called by the individual tests whenever I come across tests that need to do some prep work before they can run. Makes things much easier to grasp when you revisit the test fixtures later.
    reply
  • Christian Rørdam

    4 months ago

    Agreed! I think it is important that a test method can be read as a sequence of steps, but the steps can be reusable methods. So I do extract the gory details of actually performing the step, but I usually don't extract a subsequence of steps as a new method. And of course, I try to give the methods as good names as possible, as always.
    reply

Add New Comment

Returning? Login