Forum Discussion

MichalinaK's avatar
MichalinaK
New Contributor
25 days ago

Test error after rerun tests

Hi,

I am testing desktop application in TestComplete. When I open TestComplete and run my test suite all tests are pass. But when I rerun this suite there is some inexpected error. When I colse TestComplete and open this again everyhing is OK, tests pass.  What could be the causes?

  • rraghvani's avatar
    rraghvani
    Icon for Champion Level 3 rankChampion Level 3

    Can you provide more details, as "unexpected error" does not really give us much information to work from!

    What version of TC are you using? What scripting language are you using? How are you opening your application? What's the actual error message?

  • Hassan_Ballan's avatar
    Hassan_Ballan
    Regular Contributor

    You need to provide more details, for starter what does the error message state? Screen shot or log complete entry.

    • MichalinaK's avatar
      MichalinaK
      New Contributor

      For example:  "RuntimeError: The object does not exist"  in Log.CreateFolder(name) function. This is first step of test.

      • rraghvani's avatar
        rraghvani
        Icon for Champion Level 3 rankChampion Level 3

        What value are you passing in for "name"?

         

  • scot1967's avatar
    scot1967
    Regular Contributor

    A complete guess as we don't have anything to go on.  Are you using project or suite variables?

    https://support.smartbear.com/testcomplete/docs/testing-with/variables/collections/project-and-project-suite/about.html

    Project and project suite variables can be temporary and persistent. You create them in the appropriate sections of the Variables page of the project or project suite editor. Persistent variables store their values between test runs. This way, you can share data between test sessions. Variables of the Object, Table, and DBTable types cannot be persistent.

    Note: Use persistent variables carefully. When a test run starts, the variable will have the value stored during the preceding test run rather than its initial value and this may cause your test to fail.