Should tearDown methods contain common test logic?

Is it a bad practice to include common test logic (e.g. verify no more interaction with mocks) in the tear down method?

I was told once that I should only include clean up code in tearDown, but I've seen many times common logic included there as well.