Forum Discussion

nelsonbritto's avatar
nelsonbritto
Occasional Contributor
23 days ago

log message issues in testcomplete

i try to double click on the log messages in testcomplete it doesnt bring me to code where it was declared. and it doesnt show anything when i am trying to double click it. please explain about why d...
Hassan_Ballan's avatar
Hassan_Ballan
Icon for Champion Level 3 rankChampion Level 3
22 days ago

If you ask ChatGPT it would provide you with a lot of reasons to why this could be expected based on your situation.

đź‘Ť Found it helpful? Click Like
âś… Issue resolved? Click Mark as Solution

  • Hassan_Ballan's avatar
    Hassan_Ballan
    Icon for Champion Level 3 rankChampion Level 3
    22 days ago

    Also you stated messages in plural does not bring you back to the code, hinting that none of the messages, is that correct or is it only some of the messages? 

    If some of the messages that should give you a hint to why.

    • nelsonbritto's avatar
      nelsonbritto
      Occasional Contributor
      9 days ago

      None of the log messages navigate back to the code on my machine.
      When I double-click any message, it does not take me to the line where the code is declared.

      On my manager’s machine, the same log messages correctly navigate to the corresponding script line, but on my system, none of them do.

      I am using .scpp scripts in TestComplete version 15.64.3.7 (x64) on Windows 11 24H2.

      • Hassan_Ballan's avatar
        Hassan_Ballan
        Icon for Champion Level 3 rankChampion Level 3
        8 days ago

        Since this works on your manager’s machine but not yours, I’d recommend isolating environmental differences:

        1. Confirm the project path is identical on both stations (same local path). 
        2. Create a brand-new TestComplete project on both machines and verify log navigation in both JavaScript and ScriptCPP to confirm whether the issue is ScriptCPP-specific.
        3. Validate the OS version/build on both machines (e.g., Windows 11 24H2 vs older). If they differ, raise a SmartBear support ticket, as this may be OS-related.
        4. Clear TestComplete caches on the affected machine:
          Close TestComplete, then delete
          %LOCALAPPDATA%\SmartBear\ %APPDATA%\SmartBear\
          Reopen TestComplete and retest.

         

        These steps should help determine whether the issue is OS-related, cache-related, or specific to ScriptCPP rather than the project itself.

        đź‘Ť Found it helpful? Click Like
        âś… Issue resolved? Click Mark as Solution