Ayende @ Rahien

My name is Oren Eini
Founder of Hibernating Rhinos LTD and RavenDB.
You can reach me by phone or email:


+972 52-548-6969

, @ Q c

Posts: 5,971 | Comments: 44,508

filter by tags archive

Reusable tests

It is generally accepted that reusability is not something that you should strive for in your tests. However, I have found that reusing tests is an interesting way to save time when you are testing a full process. Take for instance this piece of code:


public void SuccessfullySavingTemplateWillShowConfirmation()



    Type("TemplateName", "Template1");



    AssertTextPresent("Template saved successfully", "Should have gotten a confirmation message");



public void CannotAddTemplateWithDuplicateName()


    //Create a template called "Template1"




    Type("TemplateName", "Template1");



    AssertTextPresent("There is already a template called 'Template1', please choose another name.",

            "Should warn when trying to create template with duplicate name");


Some of the methods are utility methods, but on the second test, the first line of code actually calls to another tests to do the initialization of the test. I can see this kind of stacking useful in cases where I would usually want to have orderred tests.


Shane Courtrille

While I understand where you're coming from I definitely disagree strongly with how you got there. I personally would be worried about the fact that my one test is now dependent on another test for certain behavior. This of course creates the restriction on the first test that it needs to keep doing what it's doing. Now this is a fairly simple example and you are most likely going to be safe. But if you make a habit of this I'd be amazed if it didn't bite you in the ass over time.

Love the blog btw :)

Ayende Rahien


That is a good argument against it that I have no considered.

I'll give it some more thought.

Comment preview

Comments have been closed on this topic.


  1. Paying the rent online - 2 days from now

There are posts all the way to Aug 03, 2015


  1. Production postmortem (5):
    29 Jul 2015 - The evil licensing code
  2. Career planning (6):
    24 Jul 2015 - The immortal choices aren't
  3. API Design (7):
    20 Jul 2015 - We’ll let the users sort it out
  4. What is new in RavenDB 3.5 (3):
    15 Jul 2015 - Exploring data in the dark
  5. The RavenDB Comic Strip (3):
    28 May 2015 - Part III – High availability & sleeping soundly
View all series


Main feed Feed Stats
Comments feed   Comments Feed Stats