Issue with Data-Driven Loop, script is not gracefully exiting on error

Hi diwakar_sh12, not sure if you saw my previous response, but FindElement() does not throw an error. It either returns the Object or None. You need to raise an exception if the object is not found, for the try...except statement to work

For example, in the following code, Log.Message("Error") will never been called if FindElement() returns None

def test1():
    obj = None
    try:
        obj = Sys.Browser("chrome").Page("*").FindElement("//a[@title='Contact Me']")
    except:
        Log.Message("Error") # Never called!
    Log.Message("Continue...")

You need to do something like this

def test1():
    try:
        DoSomething()
    except Exception as ex:
        Log.Message(ex)

def DoSomething():
    obj = None
    obj = Sys.Browser("chrome").Page("*").FindElement("//a[@title='Contact Me']")
    if obj is None:
        raise Exception("Object not found")

Do you expect all of this data to work or do you have some planned failures?

You are using the FindElement() method which either returns the Object that matches the search condition or returns None if condition not matched. FindElement() does not throw an error.

Hi diwakar_sh12 ,

I am not that proficient with python, but you might want to put the try/except block inside of the while loop, that way it can continue with the next entry if an error is raised. I'm not certain of the exact syntax/format, but something like this might work:

  while not ddv.EOF
    aqTestCase.Begin("Test Case" + ddv.Value[0]);
    try:
      openApp()
      clickObject(contactUs)
      waitTillPageLoads()
      fillContactForm(ddv)      
    except:
      Log.Error("Error Occured")
    closeBrowser(Project.Variables.browser)    
    aqTestCase.End()
    ddv.Next()

I hope this helps.

During design, you need to decide how your want your automation to behave if a failure occurs. Such that,

1. If an error occurs, continue with remaining steps?
2. If an error occurs, stop automation?
3. If number of errors logged, is greater than number of errors allowed, stop current test and move on to the next test?
4. If an error occurs, stop current test and move onto the next test?

Within my automation project, I use name mappings and I also use the Find method for dynamic objects. If a UI Object is not found, for whatever reasons, I stop the current test and move onto the next test. Once the automation is finished, I can then report on the number of tests passed/failed. I can then afterwards look into the failed tests.