Test using wrong response map
I am running a test and I cannot get it to use the right response map. I have tried changing the priority and it will then use that response map, but other steps then fail as they use the wrong map. How do you get around this issue?[link text][1] [1]: /storage/temp/4241-snmpwalk_mib2_tcp.ffrm
First, check that you're not forcing the map with the Step Properties. That's usually the first culprit. Next, force the map that you want by setting the Step Properties. This is useful to test if there are any errors in the map that may be flipping it over to the other map. Once you find out, don't forget to unset this as you don't want to leave it connected. The other thought is combining these two maps. As I look at the maps, the only difference is in the patterns. Unless you need to guarantee the pattern is present, you can put all three patterns in one map and uncheck the "Generate an error if no matches are found" checkbox. Then you only have to deal with one map. If all else fails, contact support so they can take a look at this via webex. There may be something else afoot here that they can help you resolve.
17 People are following this question.
