When we do agile, the last thing that we want to do is “documentation”. We do not have much design documents except they are necessary. For software architecture, we use diagrams and photos that were taken during the architecture discussion. We do have documents like “user guide” or “read me”. However, as the application that we developed have rich usability, and well designed so sometimes even documentation is not necessary. It vary case by case. Roughly speaking, compared to Waterfall model, agile software development has much less documents.

For your questions, I’d like to give you an real example for explanation, please have a look at the post context if you still have questions please feel free to ask.

Questions: I understand that in TDD you write the test cases before you write the code. In your test, you run totally 4 test cases.
1. Is each test case designed to test one of the three acceptance criteria?
2. How do you define the test is “failed”? e.g. If the result data is not “exactly match” the expected data? or the test doesn’t run properly?
3. Why did you “pass” this test with only one test case for each requirement?

Thanks.