Testing IIS module - what to look out for
Not 100% sure I have this in the right spot. I've been given a new version of our product to test embedded within an IIS module. I've never tested an IIS module before, but I'd have a little familiarity with IIS itself. I've tried googling for anything in particular to look out for but I'm either getting how to debug it when you're building it, or just web stress/load/performance testing.
I'm wondering if there is anything in between I'm missing, configurations I should watch out for, common problems with modules etc and was hoping the collective knowledge here could help me?
Many thanks for taking the time to read over this anyway!
It'll be similar to service level testing. Basically IIS is a platform for running windows hosted services. Think of it as a service manager.
So what you'll be testing is the service your SUT provides.
Thanks for getting back to me, I appreciate it!
I guess I thought there would be settings etc to play around with within IIS itself and that maybe some of these were notorious for causing trouble. Testing the service is definitely the main basis of my testing.