Scripting access to log messages
Hi, I have created a script that writes out tests results to a SQL database. I have got a bit stuck on the last part however. I was hoping to use the general event of on log error to write out th...
Forum Discussion
AdditionalText will return what you see in the "Additional Info" tab in the TestComplete log. MessageText will return the main text of the error message.
Hi TristanOgre,
Thank you for the help you have given. I am however still struggling to read the information from LogParams.AdditionalText and write it out elsewhere. Do you have an example you could share?
I think my other option would be to go down this path: https://support.smartbear.com/testcomplete/docs/reference/project-objects/test-log/logresults/textlogdata/text.html and pull the text out to a seperate file to use?
Many thanks,
MegO
Basically, what you have listed before is a good start to the code.
function GeneralEvents_OnLogError(Sender, LogParams) { TestComment = LogParams.AdditonalText }This assigns the value of "AdditionalText" to a variable called "TestComment". so, your next step would be to take "TestComment" and pass it in to some sort of function or value that you would then write out to a file or to SQL.
I guess the question I have for you is this:
What is your ultimate aim? Do you want to only write out the information for errors? do you want the whole log file output? You mentioned writing to SQL. Is that your preferred destination? For what purpose are you doing this output? We'd be happy to help but we need to know a bit more of what your desire is here.Hi TristaanOgre,
This is what I would essentially be be doing:
function GeneralEvents_OnLogError(Sender, LogParams)
{testStatusComments = LogParams.AdditonalText
var dbObj;
dbObj = ADO.CreateADOQuery();dbObj.ConnectionString = "MyConnectionString";
dbObj.SQL = "Update Test_Status set testStatusComments = testStatusComments + '" + testStatusComments + "' Where TestSectionName = '" + testname + "' AND TestStartTime Like '%" + TestDate + "%'";
dbObj.ExecSQL();
}
This will add to other information currently being written out to SQL on the start and stop events.
The eventual aim is to start using reporting services so that we can can see very quickly if there are any patterns in failure.
Generally speaking, that looks fine... I haven't run it or anything but it looks about right. What seems to be the problem with it that you can't access the information?
