Export Test Results To Excel Sheet

Hi Anil,



As long as I know, there is no 'one click' way to export the results to a excel from the log generated by Test Complete.



What you can do is a function that everytime a message is posted in TestComplete log, to write it down in an excel sheet. For example:



function LogMessage(text, excelRow, excelColumn)

{

  Log.Message(text);

  // Write to excel

  return new Array(newRow, newColumn);

}



This function should post a message to the Log, and then write it to the excel file you wish. There are some issues that you will have to solve:

1. 
   Keep the excel opened all the execution? Or open it and close it everytime? (You can execute Excel without beeing visible, so it won't bother in screen)


2. 
   You have to keep track over the rows and columns, so you won't write over the same cell all the time.


3. 
   You will need to change the script if you want to post messages, warnings, errors... Or create othe functions.


4. 
   What about pictures?

You can use the earlier links to know how to write on excel.



In my case, what I do is keep an array with everyline of text I want to write on excel (text + message type), and when I finish on a test set, I write them down in the excel file. What I do with pictures is save them in a shared folder and put a link in the excel file, so it won't grow up like a monster.



I hope it helped!

Hi  Javier Coll ,



  Can you please tell how to hyperlink the file that I am writing back to the excel file.



I am capturing screen shots and saving it in file. I am writing the filepath back to excel file. But I am not able to create a hyperlink to that path.



Can you please help me with it.



Thanks

Jenifer.

> [...]  some of the values (sentences, etc.) that I wrote to the log contained commas [...]

AFAIR, such strings should be quoted. Then they will be processed fine by the csv driver. Possible quotes within quoted values must be quoted as well, so I can recommend aqString.Quote() to handle this.

You are correct. In most cases, surrounding the values with quotes is enough to allow commas. I actually forgot about that step in my discovery process and so I didn't mention it in my post above.  Some of the text I was processing already had quote marks (measurements, e.g. 2 1/2") so that messed up my plan so I ended up doing what I mentioned above.



So... a quick summary for those that come later...

1. 
   If you don't have commas or quotes in your values, you can just separate all values with commas. e.g. value1,value2, value3


2. 
   If you have commas (but not quotes) in your values, you can surround those strings with quotes. (This is probably just good practice anyway to avoid the oops later) e.g. "$1,200","$1,400","$1,600"


3. 
   If you have quotes in your strings, pick a different separator value that will never show up in one of your values. e.g. 2 1/2"|3"|3 1/2" (where | is the separator)

If you don't have to use #3, you can save the text file with the CSV extension and Excel will open it as is. If you have to use #3 then you will have to use Excel's text import wizard to specify the separator value... it's not that hard but it's an extra step. I ended up writing a quick Excel macro to do the import for me.

I would add:

-- If you have #2 but don't want to resort to custom separator, you may try aqString.Quote() which will quote the string and double quote every quote within the string (e.g [1 1/2"] will become "[1 1/2""]"). This should make it possible for the csv file to be imported into Excel without the necessity of any additional setting.



Note: I did not check explicitly the above, but this is what I seem to remember from the documentation.

Hi Jeff,



Indeed, aqString.Quote() works as you wrote (and I think this is a problem in certain cases like ours).

Utilities.QuotedStr() works as required, but it works with single quotes only.