Keyword “Fenster aufnehmen” captures the wrong window

[QA-Tester42]

I use the keyword “Fenster aufnehmen” from the “RoboSAPiens.DE” library (version: 2.22.3) to take screenshots during test execution. I also use two screens.

The test execution is started from the VSCode IDE terminal. The SAP session runs on the second screen.

During test execution, screenshots are sporadically or incorrectly taken from the screen where VSCode IDE is running.

The library is imported with the following statement:

Library RoboSAPiens.DE x64=True

Can you please check what might be causing this error?

[QA-Tester42]

Update: If both VSCode IDE and SAP session are running on one screen and SAP session is maximized in the foreground, only the SAP session window will be recorded.

[mardukbp]

I just released version 2.24.2, which only takes a screenshot of the region within the boundaries of the main SAP window.

[QA-Tester42]

I installed version 2.24.2 and used it to run the test.
The screenshots are now only taken from the SAP window, but they are incomplete/cropped.
This means that only part of the window is captured with the new version.

[mardukbp]

The screenshot is taken using a Windows API function, which only copies the pixels from one monitor. Therefore, if the window spans more than one monitor, it will be cropped. If that is not the case, I will take a look at it in January.

[QA-Tester42]

This is not the case because the SAP window is not larger than the screen.

[QA-Tester42]

Update:
I just noticed that I also have the problem with cropped screenshots with the Verrison version 2.22.3

The status bar is not captured when taking the screenshot, even though it is visible.

Further details: Screenshots are not embedded in the log file, but are stored as PNG files in the log directory.

Thank you for your support!

[vadurk]

Further details: Screenshots are not embedded in the log file, but are stored as PNG files in the log directory.

You could try using listener. In RoboSAPiens documentation look for: == Automatically take a screenshot when a keyword fails ==

[QA-Tester42]

Thanks for your feedback.

I placed Listener.py in the “.\libs\Listeners” folder and called the script as follows.

robotcode -p dev robot -P .\lib\Listeners\ --listener Listener .\tests\scenarios\SAPLogin\

Although I get the following message, the test runs without errors.

[ ERROR ] Calling method 'end_library_keyword' of listener 'Listener' failed: No active SAP-Session. Call the keyword "Connect To Server" or "Connect To Running SAP" first.

I don't understand why I need a listener for this. All key words in the script can be executed without errors. The PNG files can be created without any problems, but they are cropped.

[vadurk]

I don't understand why I need a listener for this. All key words in the script can be executed without errors. The PNG files can be created without any problems, but they are cropped.

You don't need a listener for your particular problem. I was referring to your comment that the screenshots are not embedded in the log file. Listener can help you with that.

[vadurk]

This is my Listener:

from robot.api.interfaces import ListenerV3
from robot.libraries.BuiltIn import BuiltIn

class Listener(ListenerV3):
    ROBOT_LISTENER_API_VERSION = 3

    def __init__(self):
        self.keyword_stack = []

    def start_keyword(self, data, result=None):
        self.keyword_stack.append({
            'data': data,
            'child_failed': False
        })

    def end_keyword(self, data, result):
        context = self.keyword_stack.pop()

        # Check if any parent keyword is 'Run Keyword And Ignore Error'
        parent_is_ignore_error = any(
            k['data'].name == 'Run Keyword And Ignore Error'
            for k in self.keyword_stack
        )

        if result.failed and not context['child_failed'] and not parent_is_ignore_error:
            try:
                robosapiens = BuiltIn().get_library_instance('RoboSAPiens')
                robosapiens.save_screenshot('LOG')
            except Exception as e:
                BuiltIn().log(f"Failed to take screenshot: {e}", level='WARN')

        if result.failed and self.keyword_stack:
            self.keyword_stack[-1]['child_failed'] = True

This is how I run it in my workflow:

robot --nostatusrc --listener utils/Listener.py --loglevel DEBUG -d results tests/

Hope it helps. This was the discussion that I faced some issue with the listener: #41

[QA-Tester42]

Thank you for providing the code for the listener.

The listener is a workaround that allows to get complete/embedded screenshots.
The analysis of the actual problem will then take place in January.
Am I understanding this correctly?

Perhaps this information will help with the analysis:
I looked at all the screenshots from the test run. They are all the same size: 1550 x 926px.

[mardukbp]

Yes, I will analyze it in January. Thanks for the information. I was going to ask precisely that.

[vadurk]

Thank you for providing the code for the listener.

The listener is a workaround that allows to get complete/embedded screenshots. The analysis of the actual problem will then take place in January. Am I understanding this correctly?

I'd say listener is an alternative and not a workaround. I've used several libraries that do screenshots and all of them save screenshots to a specified folder. To be honest I don't think that embedding screenshots to log file as a default is a good idea to begin with.

[QA-Tester42]

Hi Marduk,

thanks for your feedback!

Just to clarify.
We used to save screenshots in the LOG file.
Since there were problems importing test results to Xray, we now save the screenshots as PNG files in the OUTPUTDIR directory.

I started the test run today in the office (yesterday I was working from home) with version 2.24.2. Now the screenshots are displayed in full. Apparently, the problem is with the monitor, although on my monitor at home, the SAP window was displayed on one screen. Really strange.

I wish you a wonderful and relaxing holidays.
Yury

[mardukbp]

Hi Yury,

thanks for the clarification. I was a bit confused, but now I understand.

Ok. That's strange. I would encourage you to do some experiments at home. Maybe you will figure it out. I don't think there's much I can do.

Happy holidays!

Marduk