I'm not entirely sure how postsharp works, but as I currently understand, you invoke a post build process to weave the aspects into the IL.
If my understanding is correct and if you can skip the post-build weaving then you should be testing your method in ignorance of the aspect ( and testing the aspect separately somewhere else ).
Why?
If you test the aspect and the method, you are testing 3 things at once:
- the method
- the aspect
- the weaving of the aspect into the code
This is bad karma and may lead you down the rabbit hole if something goes wrong ( as well as making your unit test into an integration test ).
Looking at the list above:
- you do need to test the method, in isolation with no other distractions as this will let you focus on making sure the method does exactly what you expect - no more, no less.
- you don't need to test the aspect every time it is used, just test it once and make sure it does what you think it does
- you don't need to test that the weaving works; it is ( should be ) tested as part of the post sharp implementation.