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.
In the past I would make a test suite per package, that would hold all of the tests in that package.
then I would roll up all of the package test suites into a master test suite, which would hold all of the package test suites.
Anyone know of a better idea?
Your approach is a good starting point, your Test-suits are structured in the way of your code definition. You could also add additional test-suits to cover special functional behavior.
For Example if you need for your
addXXX()Method a Controller/Model/Display(MVC-Pattern) out of different packages you should combine youraddXXX(),removeXXX(),updateXXX()to a Test-suite likemodifyXXX(). So you don’t have all Classes of the packages tested, but only the Methods for one pack of funcionality.