tdd

Using C#, I need a class called User that has a username, password, active flag, first name, last name, full name, etc. There should be methods to authenticate and save a user. Do I just write a test for the methods? And do I even need to worry about testing the properties since they are .Net's getter and setters? Rob Cooper Many great responses to this are also on my question: " Beginning TDD - Challenges? Solutions? Recommendations? " May I also recommend taking a look at my blog post (which was partly inspired by my question), I have got some good feedback on that. Namely: I Don’t Know

What do I lose by adopting test driven design? List only negatives; do not list benefits written in a negative form. Adi Several downsides (and I'm not claiming there are no benefits - especially when writing the foundation of a project - it'd save a lot of time at the end): Big time investment. For the simple case you lose about 20% of the actual implementation, but for complicated cases you lose much more. Additional Complexity. For complex cases your test cases are harder to calculate, I'd suggest in cases like that to try and use automatic reference code that will run in parallel in the

OK, I know there have already been questions about getting started with TDD .. However, I guess I kind of know the general concensus is to just do it , However, I seem to have the following problems getting my head into the game: When working with collections, do will still test for obvious add/remove/inserts successful, even when based on Generics etc where we kind of "know" its going to work? Some tests seem to take forever to implement.. Such as when working with string output, is there a "better" way to go about this sort of thing? (e.g. test the object model before parsing, break parsing

I have been doing TDD and was using it more as unit testing than to drive my design. Recently I have read a lot about BDD; now that I have a better idea about them both, I was trying to figure out how to use BDD and unit testing concurrently. For example I would drive my design using BDD, Dan North style, and lets say I am working on an app and I have a simple spec and I implement it. I have just enough bdd/spec to cover it. Now after I've re-factored it and am happy and it's passed as done for that spec, should I start writing Unit tests to cover all possible inputs, because that's what I did

Either using Nunit or Microsoft.VisualStudio.TestTools.UnitTesting. Right now my assertion fails. [TestMethod] public void GivenEmptyBoardExpectEmptyBoard() { var test = new Board(); var input = new Board() { Rows = new List<Row>() { new Row(){Cells = new List<int>(){0,0,0,0}}, new Row(){Cells = new List<int>(){0,0,0,0}}, new Row(){Cells = new List<int>(){0,0,0,0}}, new Row(){Cells = new List<int>(){0,0,0,0}}, } }; var expected = new Board() { Rows = new List<Row>() { new Row(){Cells = new List<int>(){0,0,0,0}}, new Row(){Cells = new List<int>(){0,0,0,0}}, new Row(){Cells = new List<int>(){0,0