I created a query, interface_status_up, that looks like this:
//Row[interface='{0}']/interface_status
Then I created a second query, lo_status_up, that looks like this:
interface_status_up('l0')
iTest tells me that this query doesn't match. So I created a third query, lo_status_up_1:
//Row[interface='lo']/interface_status
And iTest tells me that the query matches! And this related query, bvi0_status_up:
interface_status_up('bvi0')
Works fine; iTest finds it no problem! This seems like a bug to me; at the very least, it is wicked inconsistent. I've attached a simple test case to reproduce it. This is in 4.0
Answer by Sreekanth · Jul 08, 2010 at 08:14 PM
I didn't get what you are expecting.I have gone through your test case and response map,but it works fine.
Could you please explain detail on this.
You ran it? Doesn't work for me!
Parameters
Execution Issues
Steps
Interface bvi0 state Admin up: yes Link up: yes Interface lan0 state Admin up: yes Link up: yes Interface lo state Admin up: yes Link up: yes Interface mgmt0 state Admin up: yes Link up: yes Interface mgmt1 state Admin up: yes Link up: noPost-Processing: analyze
Looks like it was on 4.0, too, from the report format. That's just completely weird!
I think I found the cause for the failure. There is a mistake in the query format of "lo_status_up". The query format has "interface_status_up('l0')" instead of interface_status_up('lo'), where "lo" is the interface name. let me know if it solves your query?
documentation error on info issueCount 1 Answer
Response Mapping Eval Statements 2 Answers
how to assign a name for variable token that contains multiple words in block response mpa 1 Answer
Response map query 1 Answer
Response map queries 1 Answer
Copyright 2008- Spirent Communications, all rights reserved. Terms and Conditions.