Comments on: Naming your test methods

By: joeyDotNet

joeyDotNet — Mon, 11 Feb 2008 18:19:38 +0000

The only thing you don’t get with F2 is the ability to easily create a sentence like test name by actually writing a sentence. At least not as easily.

One of my R# live templates (nt) is for creating a new test which looks like this:

[Test]
public void “TESTNAME”()
{
}

With the TESTNAME part highlighted so I can just start typing a sentence including spaces. Then a short Alt-S + Alt-U later (spaces to underscores) I’m in business…using a tweaked version of the BDD macro that JP, Scott, Joe and others have showed.

Might seem like a small thing, but I’ve found it speeds me up. And of course you can always F2 it later if you need to change it.

By: Christopher Bennage

Christopher Bennage — Mon, 11 Feb 2008 14:10:28 +0000

I pretty much do the same thing as you Jason. I care a lot about names, but I was wasting a lot of time naming things up front.
Now, I either ‘X’ or best guess and take solace in the fact that I can easily F2 it as soon as I know more.

By: Chris Patterson

Chris Patterson — Sun, 10 Feb 2008 16:14:46 +0000

A good way to break the log jam in naming your tests is to look at the acceptance criteria of the story you are developing.

- When the passenger is traveling to another country, they must have a passport.

public class When_the_passenger_is_traveling_to_another_country()
{
[Test]
public void They_must_have_a_passport()
{
}
}

Just an example I know, but it makes sense if you start from a well defined story with solid acceptance criteria.