Controller tests and stubbing filters/actions. What's the guideline?

Is stubbing filters/actions in controller specs considered as a good practise?

Let's say I have filter authorize! on almost every controller. Can I just stub it in all controller specs or I should have shared examples for testing each action if it has filter/action behaviour?

Things are getting messy when there are dozen of filters/actions on controllers (also inherited...)