http://johannesbrodwall.com/2008/07/02/testing-avoid-setup-and-teardown/ Johannes Brodwall's Musings on Software Architecture and Programming Fri, 27 Jan 2012 09:40:00 +0000 hourly 1 http://wordpress.org/?v=3.3.1 http://johannesbrodwall.com/2008/07/02/testing-avoid-setup-and-teardown/comment-page-1/#comment-62491 Christian Rørdam Thu, 03 Jul 2008 08:35:51 +0000 http://www.brodwall.com/johannes/blog/2008/07/02/testing-avoid-setup-and-teardown/#comment-62491 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. 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.

]]> http://johannesbrodwall.com/2008/07/02/testing-avoid-setup-and-teardown/comment-page-1/#comment-62483 Anders Norås Thu, 03 Jul 2008 07:31:34 +0000 http://www.brodwall.com/johannes/blog/2008/07/02/testing-avoid-setup-and-teardown/#comment-62483 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. 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.

]]> http://johannesbrodwall.com/2008/07/02/testing-avoid-setup-and-teardown/comment-page-1/#comment-84584 Christian Rørdam Thu, 03 Jul 2008 06:35:51 +0000 http://www.brodwall.com/johannes/blog/2008/07/02/testing-avoid-setup-and-teardown/#comment-84584 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. 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.

]]> http://johannesbrodwall.com/2008/07/02/testing-avoid-setup-and-teardown/comment-page-1/#comment-84583 Anders Norås Thu, 03 Jul 2008 05:31:34 +0000 http://www.brodwall.com/johannes/blog/2008/07/02/testing-avoid-setup-and-teardown/#comment-84583 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. 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.

]]>