mayertj1
New Contributor
Joined 7 years ago
User Profile
User Widgets
Contributions
TestExecute Log Viewer
When a test starts, a log folder is created and used to capture results real-time as steps complete. However there is no way to view it using TestExecute until the test finishes. Also, the XML format of the log is proprietary without any easy way to interpret and display directly.The only solution I found is a script command that allows saving the current log as HTML: “Log.SaveResultsAs("C:\\Users\\User1\\Documents\\Test",lsHTML,false);” Placing this command at various strategic locations, and refreshing the browser, can get close, but ideally a seperate utility is available that allows for viewing and monitoring the progress of a long running script.683Views5likes0CommentsTestExecute Log Viewer
Currently I'm issueing the following command throughout my script: Log.SaveResultsAs("Test",lsHTML,false); Then open the HTML log results in a browser and use refresh to monitor the progress. Ideally there's a runtime log viewer that could do the same thing without the refresh, but TestExecute "View Results" is only available AFTER the test completes. Does such an option or tool exist?Solved1.3KViews0likes2CommentsManage order of configurations in Collaborator Enterprise Client
I'm working on two projects, each with a large and complex folder structure. To speed up scanning for differences, the projects were futher divided folders within each of the projects. Although this dramatically speeds up scanning, it does result in many SCM configurations listed in the client, and it appears random, making the task of finding the correct "Local Path" tedious and error prone - especially considering that each of the two projects share very similar paths. It would be ideal if Collaborator could support the following features: Maually ordering the configurations within the client, or at least sorting by Local Path. Support for groups of configurations. If more than one group is configured, prompt the user which group should be loaded, and provide the ability to switch groups. I'm considering trying to manipulate the ".smartbear\profiles" folder in an attempt to simulate this (i.e. have two seperate profiles directories, that get renamed to ".smartbear\profiles" depending on which project I'm currently working on, and then rename the ".options" files to manage the order).819Views0likes0Comments