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.
Sometimes integration tests are rather complex to write or developers have no enough time to check output – does it make sense to write tests that make sure “no exceptions are thrown” only? Such tests provide some input parameters set(s) and doesn’t check the result, but only make sure code not failed with exception?
May be such tests are not very useful but appropriate in situations when you have no time?
An integration test is basically the same as a unit test albeit more complex more involving due to the significant extra components. Unit tests are all about providing some inputs and asserting some results be they values or exceptions etc. The same should be applied to your integration tests. At worst at least test that the actual outcome makes sense instead of just assuming no exceptions means its ok. Such an assumption is extremely poor practice and smells of laziness or perhaps lack of thought about the approach.