Are you answering me or Ganesh? I can't tell if you are or are not. If not, the integration path is detemined by the implementer and hopefully meets the requirement. However, the approach to testing a thread depends upon the type and implementation.
Which server components? What types of servers are you referring to? Are you testing from a blackbox/end-user perspective? What do you hope to prove by testing the threads you refer to? Are you functional testing or performance testing - or both? Please answer each of this as it will help to give you a better answer.
The ultimate think to be aware of when using/testing threads is synchronization issues. It is a very common family of problems: data gets curropted, objects are used after deletion etc - all thanks to multiple threads accessing the same data without proper synchronization.
So, apart from verifying the logic of each execution thread by itself, you MUST verify the integrity of them all when working together.
I might be wrong, but possibly "thread testing" is not literally testing process threads. I think you guys are talking about 2 different things?
.. just did a search. Prasanna is on the right track. Here's the definition I found:
A variation of top-down testing where the progressive integration of components follows the implementation of subsets of the requirements. As opposed to the integration of components by successively lower levels.
That sounds rather confusing and my brain isn't working too well after the keg yesterday, so can someone else interpret that on lower level? Like,.. um.. 7th grade?