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.
I have a 3-tier application with Data access, service and presentation tiers. Where should i place the unit tests? On each layer? one presentation layer?
Some of this depends on you’re approach. If you’ve already got code in place, and you’re putting unit tests in after the creation of the code – I’d start by adding some end to end acceptance tests. This will exercise all layers.
Then as you go in to make changes to any part of the system I’d start putting unit tests around the component being changed – first off just testing the existing functionality, then move onto adding unit tests for the new functionality. This works well if you’re code is loosely coupled and split into well defined components. If not you’re got a lot of work to do.
Depending on how thin your data access is, I would be less inclined to write any unit tests here as errors should be picked up quite cost effectively without having to unit test these.
If you’re starting fresh, read up on BDD/TDD and use that approach to ensure quality.