TestExecute Alternatives To MHTML

Question

We are executing our tests from an Azure DevOps pipeline via TestExecute. The tests are executing correctly and are happily logging the results to a .mht file. The problem we have is that we are running out of machines that can open .mht files as the only browser that can open them is Internet Explorer.

How do I use the same Azure DevOps/TestExecute process while exporting the logs to a format that can be opened in a modern application such as Edge or Chrome?

marsha_r · Answer

Here are your options for that:
https://support.smartbear.com/testexecute/docs/logs/choose-storage-location.html
&nbsp;
&nbsp;

mattb · Answer

Hi,Another option is using the Command-Line run test step in Azure. You could use the CLI arguments, not using VSTest, and use the exportlog flag to the relative Azure location in the Azure AD:&nbsp;https://support.smartbear.com/testexecute/docs/running/automating/command-line/command-line.html&nbsp;

sonya_m · Answer

Thanks everyone!
&nbsp;
Hi&nbsp;DaveBillingham&nbsp;, were you able to solve the issue? Please share your solution with us!

Forum Discussion

TestExecute Alternatives To MHTML

3 Replies

Related Content

FindAll by alternative properties

Alternatives for "SelectedTab [Set]"

Alternative for set_item in grids

SwaggerHub smtp alternatives

JSONPath - negative match alternatives

Recent Discussions

TestComplete14.72 is not recognizing WinUI-3 objects

Floating window bleep overlapping window takes longer time (~10 min) to click the button on it.

Test case randomly fails with "parent object was not found"

Does TC have a .within() method similar to Cypress.io?

SessionCreator /Timeout option not firing EventControl_OnTimeout