Can you view Test Complete exported logs (html files) in Chrome or Firefox?
SOLVED- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Can you view Test Complete exported logs (html files) in Chrome or Firefox?
Our exported test complete log html files are not rendering in Chrome or Firefox.
Adding the --allow-file-access-from-files command line parameter in Chrome has not solved the problem.
Is anyone else having this problem?
Images below:
Chrome 45
Firefox 35
IE 11 (correct log rendering)
Thanks in advance for your help
Tom
Solved! Go to Solution.
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The reference here
https://support.smartbear.com/viewarticle/70885/
explains that the log is being exported in mhtml format
Wikipedia has some options for opening those files in other browsers
https://en.wikipedia.org/wiki/MHTML
Marsha_R
[Community Hero]
____
[Community Heroes] are not employed by SmartBear Software but
are just volunteers who have some experience with the tools by SmartBear Software
and a desire to help others. Posts made by [Community Heroes]
may differ from the official policies of SmartBear Software and should be treated
as the own private opinion of their authors and under no circumstances as an
official answer from SmartBear Software.
The [Community Hero] signature is used with permission by SmartBear Software.
https://community.smartbear.com/t5/custom/page/page-id/hall-of-fame
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks for the response Marsha.
We are exporting as html though, not mhtml. In Log.SaveResultsAs, the logFormat parameter = 1 (or IsHtml) and the result contains index.htm with external resources, rather than an mht file with resources contained within.
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Has anyone encountered this issue? This is with a .htm file, not .mht.
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I figured it out. After the logs are exported, we programmatically alter testlog.xml and were allowing the default whitespace behavior. This resulted in default indenting to be applied, which caused the rendering trouble in Chrome and Firefox.
Solution was to set XmlDocument.PreserveWhitespace = true before saving testlog.xml.
