[ QUOTE ]
Common guys is this question is so difficult or easy to answer it.. [img]/images/graemlins/frown.gif[/img]
[/ QUOTE ]
Difficult. Nobody except from HP knows how these results are stored. If you use your own code to check for values then it is something you yourself can do and export as HTML. But since you use internal checkpoint you should contact HP support
Thanks prince for your response. but previously posted threads are more specific to export the result in html format automatically.
Here what i am trying to discuss the details of xml checkpoints(parametrized) in the exported format(as if we export the results in the html it only has steps information and doesn't has any xml checkpoint details). so to be more elaborative there are two requirements i am facing:-
1) How to include the xml checkpoint with the actual and expected values of corresponding attributes.
2) DB Checkpoint with the actual and expected values of corresponding table columns.
Please refer the attached screen shot for the xml checkpoint details.
Right now if we export the result in the html format it doesn't include the xml checkpoint details or DB checkpoint details along with the respective values.
Thanks again and sorry if i am unable to understand the solution given in the previously posted threads.
Oh am sorry, [img]/images/graemlins/frown.gif[/img]
I didn't read your question correctly and i posted the way to enable the option only. Currently i am using Yaron's Reporter Manager in our project for customized html and excel reports. And we are using some Ruby gems for xml validations. WE don't depend upon QTP completely. Again sorry.
Yes Tarun, I am doing complete xml comparision from the benchmark xml(present in QTP repository with parametrized attributes and its values)through the QTP xml checkpoint, which further verifies the generated xml with the benchmark one.
Now what we are facing as the challenge is that we only have details of these xml attribute with passed or failed status through the QTP result viewer and we have to maintain the html format separately so that any one can have these details (not having QTP installed)).So the problem is that in the HTML format we are not having any details of the xml attributes.