TDD practioners, do you really start that simply?

[Wendy Gibbons]

I have seen the bowling TDD example, and I want to ask do you really start writing the 1st line of not test code with the getter just returning the result 2, then change it to store and return the passed in value. etc.

Or do you start with some remotely intelligent code, as you know that is where you have to go.
Even if you have never understood how to score bowling (myself a prime example), you can tell you are going to have to add up the scores passed in at some stage.

[Jeanne Boyarsky]

When doing true TDD< I do start with a simple base case. Like what happens when I pass in null or one value. When cheating, I don't .

[Wendy Gibbons]

here is a little example, your new task is to write a login window. what would your first test be?

[Jeanne Boyarsky]

@Test(expected=LoginException.class)
public void nulls() {
  object.login(null, null);

[Jeanne Boyarsky]

Which would force me to write:

public class Login {
  public boolean login(String username, String password) throws ValidationException {
    throw new ValidationException();
  }
}

I'd probably write more validation cases. Then I'd write a happier case.

@Test
public void invalidPassword() {
  boolean actual = object.login("test", "bad");
  assertFalse("bad login", actual);
}

Then I'd finally get to the case where login works.