Forum Discussion

Inok's avatar
Inok
Occasional Contributor
13 years ago

Howto export results in error state

In my project suite I have several projects which are triggered by cruise control in the nightly build and I want to store the results in a *.mht file.


1) Currently I use a script to save the result in a file at the end of the test. But when the test fails, the test run will be stopped and this script will not be called. How can I specify that the results will be exported anyway?


2) Using this method I have to add a script to every project. Is there a way to use one script for the suite that exports the results of ALL projects?


Thanks 

13 Replies

Sort By
  • SALVETA's avatar
    SALVETA
    New Contributor
    13 years ago

    Hello fellow testers!


    I’m trying to do something similar to what Konrad K was describing in the first post. But with all functions and help about how to start and execute tests automatically I can’t really believe that there is no better solution to export the results after a completed (or faulty) test run. To generate a log with the results must be the most basic and logical thing to do after testing so why is it so hard to accomplish? Isn’t there anyone who has come up with a simpler solution for this problem?


    Thanks from a slightly frustrated TestComplete user.

  • saurabh1484's avatar
    saurabh1484
    Contributor
    13 years ago
    Hi,



    Put the code in try catch and a finally block. You can export the logs in finally block.

    I hope that solves your problem.



    regards,

    Saurabh
  • Inok's avatar
    Inok
    Occasional Contributor
    13 years ago
    Hmm.... let's assume our solution will have 8 Projects and each project contains 10-30 KeywordTests. If I use a try catch solution I have to add this pattern in each keyword test -> 80-240 times the same code!
  • saurabh1484's avatar
    saurabh1484
    Contributor
    13 years ago
    Then you can add a General Event (OnLogError) for each project and write the same code in this event.

    I hope this will reduce your overhead of adding extra lines of code.
  • Inok's avatar
    Inok
    Occasional Contributor
    13 years ago
    I tried it but when I simulate an error, the result is always 100% success. It seems the OnLogError is fired before the error is added to the log.




    Sub ExportResult

      pos1 = aqString.FindLast(Project.FileName,"\")

      pos2 = aqString.FindLast(Project.FileName,".")

      name = aqString.SubString(Project.FileName, pos1, pos2-pos1)

      FileName = "\TestCompleteResults\" + name + "_Results.mht"

      Log.SaveResultsAs FileName, 2

    End Sub



    Sub GeneralEvents_OnLogError(Sender, LogParams)

       ExportResult

    End Sub


  • saurabh1484's avatar
    saurabh1484
    Contributor
    13 years ago

    Then Please try with the OnStopTest Event. This event is called when an testcomplete stops executing a test. This event is working fine for me.



    Please create a script file say common and add the event

    function GeneralEvents_OnStopTest(Sender)


    {


     



     



    Log["Message"]("Event is caught");

     


     



     



    Log["SaveResultsAs"]("C:\Testlog.mht",2);

     


    }



    //USEUNIT Common  [ add a reference to common script file in your orignal script]

    The above event will be called when you execution is over.



    Please see the above lines of code works for you.

    Note: The above code is in C# script. You have to modify it to work it for Vb script.



    regards,

    Saurabh


  • Inok's avatar
    Inok
    Occasional Contributor
    13 years ago
    Hi Saurabh



    I added the event to my real projects and have seen it slowes down the testexecution dramatically. On closer examination I have seen that OnStopTest will be also be fired when a test item is over. Thus results the additional load that slows down the test execution. Any other ideas?



    Best regards

    Konrad
  • chicks's avatar
    chicks
    Regular Contributor
    13 years ago
    I'm having a very similar problem.



    I had created an event handler for OnStopTest, but it was executing after every test item and slowing down the test execution tremendously.

    What I'm doing now is using the same function call and just making it the last test item run.  This works fine, unless I want to manually stop the test execution.  In that case, my last test item doesn't run and I don't get my log file.



    So, what I need now is an event that triggers when the stop option is selected in test complete or test execute.  It looked for a while like the Manual OnStopTest might do the trick, but it seems that's only for manual testing or when stepping through a teset scriptt.



    Regards,  Curt Hicks



    function GeneralEvents_OnStopTest() {

      Log.Message("Before saving results"); // Timestamp before calling Log.SaveResultsAs

      if (!Log.SaveResultsAs("c:\\TestCompleteLogs", 1, true))

        Log.Error("Unable to save test log");

      Log.Message("After saving results");  // Timestamp after calling Log.SaveResultsAs }





    }
  • saurabh1484's avatar
    saurabh1484
    Contributor
    13 years ago
    Hi Konrad,



    There is a concept of description.xml which is used to call some fucntions at the start and end of execution. You can use this feature to export all the logs after the execution is finish at project Suite level.

    I have never used this approach but you can get some help from http://support.smartbear.com/viewarticle/12104/

    Also can add a help within forum itself.



    Regards,

    Saurabh