Should every test method have at least one assert?

Question

When I'm testing a void method there is nothing to assert.For example a CreateSomething method. I know I could call in the test method an other method like FindSomething,but anyway, if there is (in the create method) an error it will show up. So it's a good practice to call an assertion in every method or i'm fine sometimes without an assertion ?

Answer 1

Not necessarily an Assert

But your test code should do at least one of these:

• assert that some property/result has/hasn't been set to particular value
• verify that certain methods have been called/avoided
• check that exceptions behave (fire or not) as expected

So it's values, actions and errors that you should be checking. Sometimes just one of these, sometimes you can't do it without a combination.