I was recently reading "mounting object-oriented software, tested test" progress To always lose a track and to ensure that you are still running, always start developing a feature with an end-to-end acceptable test ( before starting the TDD cycle ) The authors of this book have also refined the unit while testing the unit.
Okay, so I started writing viral simple applications in just Python + Pyro to exclude this approach. I want the user to be able to ask a question through a contact form, then the question in DB should be accumulated, and after the completion, the signal should be sent to send the mail-up message.
The question is - how will you approach this first end-to-end test in this case? Do you have all possibilities in this first test, or maybe I am misunderstanding the whole technique?
Any examples will be most welcome.
You do not have to include all the possibilities in acceptance tests - if you still write unit tests then I will say That is enough to start with a single test "User can fill the form, save it and can load it back", then you can add more tests if you think that a particular aspect of your system It is important that this test acceptance Are not required. Do not worry about handling all the possibilities here, you will still write many unit tests where you will check everything!
The easiest way to start is to increase your acceptance test in parallel with the code: with the test that the user can implement the input data until it fails, then in that case test Add that the user has to back this data back etc. Applying the initial infrastructure for acceptance testing will take some time. You also start writing a production code, but you can not escape from it, and there are many benefits to the test.
Comments
Post a Comment