getRunningThreadCount() returns strange value
Hi,
I am running a loadtest were I'm in the end of the test call another testcase for al threads (do a logout). This is done from the TearDown script of the loadtest.
At first, I thought that the test will not enter this script until all threads have run, but that doesn't seems to be the case...
Then I need to know when all threads have executed all their requests, and tried:
context.getLoadTestRunner().getRunningThreadCount()
but this doesn't seems to be working either. It always seems to be "number of total threads - 1".
Am I using it correctly, or is this a bug?
Anyone else used this?
To solve the problem currently, I am instead doing a sleep...
I am running a loadtest were I'm in the end of the test call another testcase for al threads (do a logout). This is done from the TearDown script of the loadtest.
At first, I thought that the test will not enter this script until all threads have run, but that doesn't seems to be the case...
Then I need to know when all threads have executed all their requests, and tried:
context.getLoadTestRunner().getRunningThreadCount()
but this doesn't seems to be working either. It always seems to be "number of total threads - 1".
Am I using it correctly, or is this a bug?
Anyone else used this?
To solve the problem currently, I am instead doing a sleep...
