Which scenarios, areas of an application/system, etc. are best suited for ‘classic’ state based testing versus using mock objects?
Which scenarios, areas of an application/system, etc. are best suited for ‘classic’ state based
Share
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.
Which scenarios, areas of an application/system, etc. are best suited for ‘classic’ state based testing versus using mock objects?
You should be using mocks for dependencies. I don’t think that its an either-or; Usually you will create mocks for dependencies, set expectations (whether it is calls or state) on them, then run the unit under test. Then you would check its state, and verify the expectations on the mocks, afterwards.