Forum Discussion

dhundley's avatar
dhundley
Regular Contributor
2 years ago
Solved

is it possible to perform special processing in the event of an error

here's what i want my execution plan to normally do: login to my AUT execute test case 1 execute test case 2 execute test case 3 etc. logoff of my AUT   IF, for whatever reason, a tes...
  • dhundley's avatar
    dhundley
    2 years ago

    i think i finally figure out how to properly use the OnStopTestCase event handler to stop and restart my AUT when any test case has an error and I don't want that error to adversely impact any subsequent test cases. Generally speaking the following event handler contains the basic steps needed. Mine is quite a bit more complicated at the point where i put the commented statement "//any other stuff necessary to get the AUT where it needs to be for the next test case" but i have tested it an it works. i did have to convert some keyword tests into scripts and then copy and paste those lines into my event handler at the appropriate location and i had to be careful even then that what I copied and pasted did not contain any KeywordTest.Run statements (as explained in the SmartBear documentation for OnTestCaseStop event handler)

     

     

     

    function GeneralEvents_OnStopTestCase(Sender, StopTestCaseParams)
    {

      if (StopTestCaseParams.Status !== 0)
      {

        let appProcess = Sys.WaitProcess("myappname", 500);
        if (appProcess.Exists)
        {
          Sys.Process("myappname").Close();
          Delay(3000);
          appProcess = Sys.WaitProcess("myappname", 500);
          if (appProcess.Exists)
          {
            Sys.Process("myappname").Terminate();
          }
        }

        TestedApps.myappname.Run();

        //any other stuff necessary to get the AUT where it needs to be for the next test case

      }

      else

      {

        //Do the normal stuff here when StopTestCaseParams.Status === 0

      }

    }

dhundley's avatar
dhundley
Regular Contributor
2 years ago

ok. i guess i didn't realize that under Statements (for keyword tests) there is actually the set of Try, Catch and Finally options but I have been playing around with them in some test cases that generate an error and they don't seem to be getting "caught". my project's on error setting is to stop the current item and i have modified my keyword test to look something like this:

Try

     do something

     do something

     do something

     do something (that raises the error)

     do something

     do something

Catch

    log message

    run script routine

 

on the line that generates the error, it calls the ontestcasestop event handler but the Catch block never gets entered. i might be able to accomplish what i want in the ontestcasestop handler but i would like to know just how to get the try/catch to work like its supposed to. does anyone have some examples? is there some project setting that i might need to change?

 

on a similar note, can anyone tell me if there's any difference between onstarttestcase and onstarttest when the execution plan is being run by an azure pipeline? i would like very much to have an onstarttest event handler that ONLY runs once before all the following testcases in my execution plan but that event handler seems to run at the start of every test case in the pipeline (the same as the onstarttestcase event handler). as a workaround to that I have created a javascript function called initialize which i run at the top of my execution plan but for it to run in the pipeline it has to have the testcase checkbox checked when it's not really one of my test cases. ideally, i would like it's enabled checkbox to be checked but not it's test case checkbox. I want it to run but not be considered a test case since it's only doing some necessary initialization stuff but azure won't run it without the test case check box checked. if the onstarttest event handler would only run at the outset of the pipeline then i could use it but, alas, that runs at the start of every test case. any ideas about that?

  • Marsha_R's avatar
    Marsha_R
    Champion Level 3
    2 years ago

    Why not make it a test case and put it at the top of the list? You do need to know if it runs successfully or not so having it in your report is still useful.

    • dhundley's avatar
      dhundley
      Regular Contributor
      2 years ago

      well, that is the way i have my execution plan set up now. the first test item in my execution plan is a call to my initialization script function with both its enabled and testcase checkboxes checked. i would just like to have the ability/option to either:

       

      1. not have my initialization javascript function marked as a test case

      or

      2. have an event handler that only runs when the execution plan begins and not at the start of every test case in side of it

       

      but, apparently, neither of those are possible in testcomplete working with azure pipeline. now, i can uncheck the testcase checkbox for the call to initialization script in my execution plan when i run it via NetworkSuite and it doesn't report it as a "test case" in the results report. I just can't commit/push that to my azure repo that way because without the test case checkbox checked in azure it won't run it and my initialization doesn't get done. 

       

      i'm still curious as to how to utilize the try/catch statements so that an error branches to the catch block. it's not working for me as i explained before. can anyone show me how to get that to work?

      • dhundley's avatar
        dhundley
        Regular Contributor
        2 years ago

        i think i finally figure out how to properly use the OnStopTestCase event handler to stop and restart my AUT when any test case has an error and I don't want that error to adversely impact any subsequent test cases. Generally speaking the following event handler contains the basic steps needed. Mine is quite a bit more complicated at the point where i put the commented statement "//any other stuff necessary to get the AUT where it needs to be for the next test case" but i have tested it an it works. i did have to convert some keyword tests into scripts and then copy and paste those lines into my event handler at the appropriate location and i had to be careful even then that what I copied and pasted did not contain any KeywordTest.Run statements (as explained in the SmartBear documentation for OnTestCaseStop event handler)

         

         

         

        function GeneralEvents_OnStopTestCase(Sender, StopTestCaseParams)
        {

          if (StopTestCaseParams.Status !== 0)
          {

            let appProcess = Sys.WaitProcess("myappname", 500);
            if (appProcess.Exists)
            {
              Sys.Process("myappname").Close();
              Delay(3000);
              appProcess = Sys.WaitProcess("myappname", 500);
              if (appProcess.Exists)
              {
                Sys.Process("myappname").Terminate();
              }
            }

            TestedApps.myappname.Run();

            //any other stuff necessary to get the AUT where it needs to be for the next test case

          }

          else

          {

            //Do the normal stuff here when StopTestCaseParams.Status === 0

          }

        }