General iTest Topics

[palemerald]

Hello,

Can Some one tell me what this HTML report means. I am just pasting a snip from my report. I would like to know what each field means here. Looks like internally for every command that gets executed, iTest is trying to apply some global analysis rules to verify the response. But can some one explain from this output what does the number present in the regexp pattern correspond to and finally what the interpreter is trying to assert.

5.2.4.1 command dut2 00:32:47.3 00:00:00.8
Command: exit all

Post-Processing:  

event OnApplicableMapsNotFound
analyze
  regex (\\[02910872\\]|\\[02670135\\]|\\[02690400\\]|\\[02690399\\]|\\[02690397\\]|\\[02690398\\]|\\[02690563\\]|\\[02690128\\]|\\[02910882\\]|\\[02910917\\]|\\[02910879\\]|\\[02912544\\]|\\[02690248\\]|\\[02910885\\]|\\[02910272\\]|\\[02760131\\]|\\[02670543\\]|\\[02910140\\]|\\[03540141\\]|\\[02910881\\]|\\[02910778\\]|\\[02911024\\]|\\[02910873\\]|\\[02910911\\]|\\[02760434\\]|\\[02760379\\]|\\[02910919\\]|\\[03200290\\]|\\[02651100\\]|\\[02760156\\]|\\[02910841\\]|\\[02690080\\]|\\[\\d+\\]\\s*\\:\\s*Cannot): assert $value != ""
analyze
  regex (\\[02810001\\]): assert $value != ""

5.2.4.2 command dut2 00:32:48.1 00:00:01
Command: enable config

Post-Processing:  

event  OnApplicableMapsNotFound

analyze
  regex (\\[02910872\\]|\\[02670135\\]|\\[02690400\\]|\\[02690399\\]|\\[02690397\\]|\\[02690398\\]|\\[02690563\\]|\\[02690128\\]|\\[02910882\\]|\\[02910917\\]|\\[02910879\\]|\\[02912544\\]|\\[02690248\\]|\\[02910885\\]|\\[02910272\\]|\\[02760131\\]|\\[02670543\\]|\\[02910140\\]|\\[03540141\\]|\\[02910881\\]|\\[02910778\\]|\\[02911024\\]|\\[02910873\\]|\\[02910911\\]|\\[02760434\\]|\\[02760379\\]|\\[02910919\\]|\\[03200290\\]|\\[02651100\\]|\\[02760156\\]|\\[02910841\\]|\\[02690080\\]|\\[\\d+\\]\\s*\\:\\s*Cannot): assert $value != ""

analyze
  regex (\\[02810001\\]): assert $value != ""

5.2.4.3 command dut2 00:32:49.1 00:00:01

Command: no interface ge-1/8/2/3

Response:

[02910284] : Interface does not exist.

Post-Processing:   event
            OnApplicableMapsNotFound
analyze
  regex (\\[02910872\\]|\\[02670135\\]|\\[02690400\\]|\\[02690399\\]|\\[02690397\\]|\\[02690398\\]|\\[02690563\\]|\\[02690128\\]|\\[02910882\\]|\\[02910917\\]|\\[02910879\\]|\\[02912544\\]|\\[02690248\\]|\\[02910885\\]|\\[02910272\\]|\\[02760131\\]|\\[02670543\\]|\\[02910140\\]|\\[03540141\\]|\\[02910881\\]|\\[02910778\\]|\\[02911024\\]|\\[02910873\\]|\\[02910911\\]|\\[02760434\\]|\\[02760379\\]|\\[02910919\\]|\\[03200290\\]|\\[02651100\\]|\\[02760156\\]|\\[02910841\\]|\\[02690080\\]|\\[\\d+\\]\\s*\\:\\s*Cannot): assert $value != ""

analyze
      regex (\\[02810001\\]): assert $value != ""

[WeiD]

Test report simply records what happens when each step get executed, for example, user is able to see post testcase execution, what was the step,  what was the response, step duration etc.Another aspect of a test report is that it also provides information about the post processing of each step. Post processing is consist of various stage/phase, the first phase is to perform mapping to a response based on the "Expected Response" defined in the "Other Post-processing "section under step properties of each step from a test case.From what you pasted here, Expected Response settings for those steps had  "Use the response  map  library  configured for  the  session"  but iTest was able to find any map that is refered in the session profile. When this happens, iTest declare an "OnApplicableMapsNotFound" event, by default, this event had no action.

the second phase is to perform analysis on the step, analysis rules can come from the onse that are added to the step or the global analysis  rules defined in the testcase (global analysis rule tab) where all rules will be applied to each every step, it is hard to say from  the snippet, it might be from global rule or might be identical rule from the different step. It is better to look at your testcase.

hope this helps.

[KumarS]

iTest does not have any built in analysis rules. So your testcase, session profile or testbed has this "regex" analysis rule which is getting evaluated. Someone in your group has added this global rule which is getting evaluated on every step. You can check global rules in your testcase editor or testbed editor or session profile editor.

If you export your test report from iTest as a "fftz" file and attach it, we may be able to tell more. (You can open the Test Reports view and then select the test report and then use File->Export->iTest->Test Report as compressed file to export this file).

Generally these numbers look like unicode character codes - but it will be impossible to tell without looking at your report.

[palemerald]

Thanks WeiD and Kumar   for   your responses.

Yes there was a global analysis rule defined in the Base session profile used by my session and this was causing it to be applied for every step being executed in the tc. Let me confirm it with my team why that rule is required.

Thanks for your time.