Reply
Contributor
acastaner
Posts: 27
Registered: 04-22-2009
0

Avalanche Session Profile

[ Edited ]

Hi,

 

I use the (patched) Avalanche Session Profile in iTest 3.4. For some reasons the Queries don't seem to work after a test is run, but I'm not sure why. The screenshot below shows that the Response Map is working (I'm using the default, buit-in one):

 

reponsemap.jpg

 

But then when I run a test, iTest complains that it doesn't find match for the Queries I set in my test case? I attached the test case and a result file, in hope someone will make sense of this...

Community Leader
JeffJ
Posts: 240
Registered: 09-02-2008
0

Re: Avalanche Session Profile

Looking at your test report (HTML), I see that your query is asking for the 62nd entry in the table; however, the table only has 24 rows.  This is why the query is not working.

 

It looks like you're looking for the average CPU utilization for something specific.  If you can identify exactly what you're searching for in this response, we can help you write the query to extract this information regardless of the table size.

Contributor
acastaner
Posts: 27
Registered: 04-22-2009
0

Re: Avalanche Session Profile

Ah, that makes sense. I assume that removing the parameter will make it so that iTest will parse the entire column? I need each row to be tested.

Community Leader
JeffJ
Posts: 240
Registered: 09-02-2008
0

Re: Avalanche Session Profile

You are correct.  If you remove the "[62]" you'll get a list of the values (which is the entire column) in the table.  I see from your test case, that you have set the Processor Properties in your assert to "Analyze each separately".  This should test each value individually and provide a pass/fail for each.  If you do not need to know which pass and which do not, but do to fail the test if at least one of this is not correct, you can use "True if All True".  There are more options if you look at the "Processor Properties" for "When multiple matches:".  To find this, first click on the "assert" step, then click on "Processor Properties" at the bottom left of the editor window.