Closed scastrec closed 4 years ago
There this thing called expectedTestDuration in the KITEBaseTest. It is to prevent the test from getting stuck. You might want to include it in the payload and give it another try. It doesn't close down the test since it doesn't close the process that run the js code I think.
Btw I don't think 1 client creating 80 tabs is a good idea, but as long as it works for you I guess 😄
Looks like the JS code still runs because I have my js console.log
.
I'll try expectedDuration.
How would you do to run 80 tuples. The first one on a specific publisher URL and the other in subscriber URL?
Kinda, yeah. That's how I set different steps for caller, who creates the room, and calee, who just joins after room creation, in a call as well. You can use the index to set different script for as many participants as you want.
Besides, we do have load test functionality as well, just not open source. For any kinda large tuple size we would switch to load test mode instead.
Looks like Java KiteBaseTest has currentIteration
and nothing in the JS version of KiteBaseTest.
Yes, we don't have the bandwidth to develop the JS library as the Java one. Even though I wrote the JS one to mimic the Java and to make KITE run Js code, it's not my forte.
@namvuCosmo I'll give a try to the load test solution from Cosmo.
If you want to know more about it, you can contact us from our website https://www.cosmosoftware.io/ :)
I'm running test with 1 publisher and ~80 subscribers. To do that, I have 1 client, and running a loop which creates all tabs. At some point (~40eme), there is a crash in KITE but it doesn't stop the test and doesn't generate reports.
That's weird.