Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
With an existing n-tier web application using ASP.net WebForms what is the best approach to get TDD acceptance on the application. What is a good plan to gain acceptance by developers to move forward to write test first code opposed to ignoring the tests while the TDD implementation is in limbo?
Knowing there will be a large “in-limbo” time of low coverage:
What areas of the model do you start writing tests for first? Critical use areas, or new development?
I agree with womp, unit testing and WebForms is hard. Especially if most of your logic is embedded in the code behind files.
I have found it helpful to create functional tests first using something like Selenium. With some decent functional test coverage I can then start refactoring, adding unit tests as I go.