Forum Discussion

gabe1's avatar
gabe1
New Contributor
10 months ago

Workaround for MessageType when using Region.Check method

Hey.  I need to move away from Region.Compare to Region.Check because of some expected tolerance in pixel values and Region.Compare only has PixelTolerance and not ColorTolerance. However, Region.Ch...
  • gabe1's avatar
    gabe1
    9 months ago

    I ended up doing this, which works but it just feels really stupid that 2 core Test Complete functions that are seemingly the same take different arguments. 

    1. Change playback options so tests don't stop on error
    2. Create a new onError handler
    3. Inside this, stop the execution for the current test only

    function GeneralEvents_OnLogError(Sender, LogParams) {
       if (!LogParams.MessageText.includes('The region checkpoint')) {
          Runner.Stop(true)
       }
    }

rraghvani's avatar
rraghvani
Champion Level 3
10 months ago

You can also change the playback options, so the automation doesn't stop on error.

  • gabe1's avatar
    gabe1
    New Contributor
    10 months ago

    That was the only other thing I could think of. The way our tests are designed is to stop on error as new tests assume the app is in the correct state. For example, if it's half way through a for loop and the app crashes, ignoring the error will end up in a weird state where TestComplete will try and execute the rest of the for loop functions on a non-existing app. Our tests are designed with that in mind, and each test is on its own unit, so if one fails, it doesn't affect the others.