Help needed with scripting interface to current test log during test run

Add this to your script in the OnStop event handler and I assure you it will actually create log files during test run :).



Log.SaveResultsAs('c:\\testlog',1);



You can then attach the index.html file to your email and send that along.

Like I said it has some issues with the formatting that I don't like but the option does exist.

Chris,

Those properties are actually available for read ("Data such as number of error messages, warning messages etc.") as well. I apologize for not fully understanding the second part of what you were trying to accomplish. Here are some of the log properties you should look for:








This is how my email summary looks:



Scripts run:

[09:58 AM] - [10:06 AM] Infinity_4_VOCTracking.xls

[10:06 AM] - [11:22 AM] Infinity_5_SpecialColors.xls

[11:22 AM] - [11:45 AM] Infinity_7_OrderNet.xls

Total Errors: 34

Total Warnings: 0

Click to view test results.

Thanks Ryan. So I used your suggestion of creating my own log. I did the following:



1. Various Event scripts increment different ProjectSuite variables (test passed, warning message, error message).

2. OnStopTest script finds the name of the test currently running and the name of the last test in the test run. If these match then I am at the end of the test run and the remainder of the script is executed and does the following:

2.1  Perform opertations on ProjectSuite.Variables to generate some test metrics (number of tests passed, number of tests failed, total number of tests).

2.2  Format the test metrics nicely into a message body suitable for email and export the test logs (mht format) to local drive. 

2.3  Send an email notification using SendMail method, message body contains test metrics and log is attached to email. 



Seemed like a lot of work and felt like I was working around the TC framework to achieve something that should be available out of the box. Ie. providing a scripting interface to the current test run. 

Well they do provide the method out of the box I just prefer to have things my own way that is why I created my own logs. The help file is actually pretty good about explaining how to email log files (as I previously noted) and such which is where I got the idea to begin with, but it seems like everyone uses Test Complete in a lot of very different ways so it's understandable to me that it works the way it does. Glad I could help though!

Hi Ryan,



My issue was that I couldnt access the current test run logs data during a test run. For example, getting the number of tests passed and failed by using the Status property of the LogItem object (http://support.smartbear.com/viewarticle/55562/?_ga=1.87424088.1554134704.1392816096)



You can only access current test run data after the test run and the event handlers have all stopped running. When I say 'during a test run' I was trying to get the logs as the final step in my test run by scripting it in the OnStopTest Event. 



I  found this in SmartBear documentation which confirms there is no scripting interface to the current test log during a test run. 

• 
  TestComplete does not provide a scripting interface to the test log of the current run. TestComplete is compiling the log during the test execution and this process is only finished when the test is complete. Scripts can access the log only after it has been added to the list of project logs that is displayed in the Project Explorer panel.

Also found this caveat on the same documentation page: 



The LogResults object provides access to project logs listed in the Project Explorer. It does not provide access to the current test log. This is because the test log contents are formed during the test execution and the log is only added to the list of project logs after the test run is finished.





http://support.smartbear.com/viewarticle/55140/?_ga=1.145209844.1554134704.1392816096

Hey Ryan,



The issue wasn't  saving the test log file during the test run or emailing it. I probably wasn't clear enough in my earlier posts :-)



The issue was extracting data from the test log of the current test run. Data such as number of error messages, warning messages etc. This cannot be achieved using the scripting interface as I found first hand and is also documented by SmartBear in their documentation (see my posts above).



I found another way to do this by counting  the occurrence of events I am interested in and storing the values in ProjectSuite.Variables. I then have some logic in my OnStopTest script that selects an email subject line dependant on whether the test run passed or failed and also generates a message body containing some high level metrics, ie. total number of tests, tests passing, tests failing, warning messages.

When you are recieveing multiple emails a day from the testing machine its handy to skim the subject line and see if there are failed tests or not. I think its also a non brainer that a user shouldnt have to open up every email they receive and look at the log file to find out if a test run was succesful or not.



Is seems to me that the 'out of box' solution that SmartBear had in mind was to send a generic email that does not indicate the test run status with the log file attached. The recipient should then open each email and examine the test log in IE. For a small team and small number of recipients and or a low number of daily runs that would be fine but it doesnt seem like a good solution to me for larger teams. 



As I said before, I dont understand why the scripting interface cant access the logs data for the current test, it exists, it just isnt compiled into a 'pretty' format. I suspect other users may also have wanted to do seomthing similar and just scripted their own solution rather than request a feature from SmartBear.

Perfect. I can call those methods rather than count the events in the script. Thanks Ryan.

Ok, those don't help. The methods above are for the current script that is being executed not the project, lol. Some more searching indicates that SmartBear support suggests creating global variables to count all these events as I was doing! 



http://smartbear.com/forums/f74/t49367/log-errcount-log-wrncount/