how to check the robustness of an event driven multithreaded application that runs as windows service without any user interface?
-
-
Well the most basic top level test is to start it and use something like process explorer to find out how many threads it has, how much memory it is using and it's other system resource use.
Then leave it running for a day or 2 in normal operation and check back to see if it's resource use has changed significantly (and unexplainably).
You will also want to try and exercise it in extreme conditions, that may mean finding (or writing) a program that has the ability to interact with your program in a extreme manor (for instance if it is a web service a program what will create lots of connections to it).
Comment