Hi,
unfortunately tristaanogre is right: I have made manually the test (copy the .tcLog files into the project MDS) -> the .tcLog files are not linked to the project and do not appear on it when I open the project :-( ).
So, by pending an hypothetical enhancement of testcomplete, maybe I could work differently, i.e currently I used TestExecute to run test and generate nearly 10 logs.
At the beginning, I analyzed the log generated by testexecute in .html format.
Then I found that it was more handly to analyse the logs in testcomplete due to the possibility to go/jump from a warning or error to the following (warning or error): it save me time.
So, guys with your large experience of testcomplete/testexecute tools, would you work or do you work like me? How do you analyze you logs files (with testcomplete/testexecute or another smartbear tools) ?
So, guys, with you large experience of testcomplete/testexecute tools, would you work or do you work like me? How do you analyze you logs files (with testcomplete/testexecute or another smartbear tools) ?
Related Content
- 10 months ago
- 10 years ago
- 3 years ago
- 10 years ago