Chrondeath

I'm using WAPT 2.5. I thought I understood how the Avg90 number was supposed to work: 90% of the response times were under this value. I was thinking that means "sort all the response times, go 90% of the way through that list, and the avg90 number should be slightly higher than that entry." On our latest run, while looking at the report, one of the blocks of data for one type of request read like this: Total requests: 216 Min: 0.12(0.12) Max: 10.1(10.1) Avg: 0.19(0.19) Avg90: 1.06(1.06) I had a co-worker express skepticism at the Avg90 number there. Our current main performance problem suspect is the Java garbage collector, so we weren't surprised to see a few instances where the garbage collector kicked in during the request and it took ten seconds, but the rest of the time things seemed to be consistently under a second. If our times were all either sub-second or 10+ seconds, how could Avg90 be 1.06 seconds? So I took a look at the CSV file of timings that WAPT generated, and I can't come up with that Avg90 number. Subtracting "Request Begin" from "Response End" for every line of that profile entry (not just the 216 for that chunk), the six highest overall were: 0:00:00.328000 0:00:00.359000 0:00:00.372000 0:00:00.404000 0:00:00.448000 0:00:10.111000 How can there be an avg90 of 1.06 seconds in any chunk if only one request ever took more than one second? I was able to compute numbers that matched the min, max, and average, so I don't think I've screwed up parsing the file.

I've been using WAPT Pro 2.5 for a while now, and I recently started running tests with more total users than I had before. I generally run using "ramp-up load". When reviewing the user logs (which I have set to record errors), it looks like most of the ramped-up users run fine, but at a certain point every user that gets created shows "Javascript Initialization Failure." For example, looking at the logs for one of my two profiles after a 24-hour run (ramping up to 600 users for this profile), User 535 shows two failed sessions labeled Session 1 and Session 2 (the errors it got were expected for this system). User 536 shows no failed sessions. User 537's log shows two entries under it, both labeled "Session 52090", both saying "JavaScript Initialization Error". In each of those tabs, the Request Body, Response Header, and Response Body are the same, and appear to be the contents of one of the two .js files configured in the WAPT Settings (the functions.js that came with WAPT and a javascript file I added for my profiles). Users 538 through 600 show the same thing, with only (five-digit) session number changing. The logs for my second profile show the same thing--the users are fine up until approximately the same time as the other profile started going bad, and then all the users created after that only show "Javascript Initialization Error." Users created before this point appear to have had no problems with the javascript, as it is integral to the test and I can see from my application that those users were succeeding. Based on the summary report's count of successful and failed sessions, I suspect that these initialization-error users were contributing a lot of failed sessions. This is the second time I've seen this; the first was an 8-hour 1035-user (across both profiles) run where the last 35 users exhibited the problem, this one was 1035 users over 24 hours with about the last 100 users exhibiting the problem. I never saw this problem on previous runs, but those didn't get over 700 users. Is this a known problem? Is this a factor of having too few load agents? Is this something that would be fixed in a more recent version of WAPT?

I have IE 10 installed, and both of these functions return "undefined": function testQuerySelector() { return typeof context.document.querySelector; } function testQuerySelectorAll() { return typeof context.document.querySelectorAll; } Is there something I'm doing wrong to get to these functions? I'm on WAPT Pro 2.5, if it matters.

I have a test scenario where I need to locate parameters to pass in the next request based on some context in the response that I don't think I can handle with the Search function type (there is dynamic text between the string I need to extract and the string I need to recognize). A Javascript function looked like the best solution to extract the response data that I need, but I'm having trouble figuring out what Javascript features are available for me to use. I tried to import JQuery and Sizzle, and both of them cause an error every time I hit "Test" for my Javascript function, as best I can figure because there is no "window" attribute? It doesn't look like I have access to document.querySelector. I tried to find the version of Javascript using navigator.userAgent, but "navigator" is also undefined. What version of Javascript is being used by WAPT for executing these Javascript functions? Is there anything like querySelector or JQuery available, or am I going to have to parse the document manually?