Forum Discussion

GPatchk0r1a's avatar
GPatchk0r1a
New Contributor
11 days ago
Solved

Enabling Screenshots on every event

Hello,

How can i turn on screenshoting every event? 
right now it only screens when there is error. not just some events. besides when i double click event it does not redirect me to the exact line of code where event has happend. error does.

my testcomplete version is  15.74.33.7.
i am making desktop script tests.
let me now if you need any kind of information

 

5 Replies

  • GPatchk0r1a's avatar
    GPatchk0r1a
    New Contributor

    I created new project and when i write script and run it, pictures are made on every event. but it does not work in old project? why?

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

      You can enable screenshots on every event by turning on Test Visualizer for both recording and playback.

      Project → Properties → Visualizer
      Set the following:

      • Collect Test Visualizer data during test run → Capture images or Capture images and object data
      • (Optional) Collect Test Visualizer data during recording → same setting
      • Ensure Capture style is consistent (e.g., Top-level parent)

      In your new project these settings are enabled by default. In your old project they were likely turned off, so TestComplete only captured images on errors. Re-enable the settings in the old project and it will start capturing every event again.

      If double-clicking a Visualizer frame doesn’t jump to the code, it’s because no Visualizer frame was recorded at that point—once you enable the settings above, this will work moving forward.

      Documentation references:

      🤖 AI-assisted response
      👍 Found it helpful? Click Like
      âś… Issue resolved? Click Mark as Solution

      • GPatchk0r1a's avatar
        GPatchk0r1a
        New Contributor

        Hello Hassan,

        Thank you. Actually i had all of those settings turned on but it still didnt capture screenshots.
        But when i updated tests from Jscript to javascript, it resolved my problem.

        Thank you once again and sorry for taking your time