Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 363007 - screenshot of failed step only captures one display in a multi-monitor desktop
Summary: screenshot of failed step only captures one display in a multi-monitor desktop
Status: CLOSED WONTFIX
Alias: None
Product: Jubula
Classification: Technology
Component: Agent (show other bugs)
Version: 1.1.0   Edit
Hardware: PC Windows XP
: P3 minor (vote)
Target Milestone: Indigo SR2   Edit
Assignee: Project Inbox CLA
QA Contact: Oliver Goetz CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-11-06 21:03 EST by Greg B CLA
Modified: 2011-11-07 06:20 EST (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Greg B CLA 2011-11-06 21:03:51 EST
Build Identifier: 20110916-0149

When a test step fails and a screenshot is captured, it seems to always be of the primary display even if the AUT window is located on a different display.

Consequently the screenshot may not always include the AUT if the environment has multiple displays.

This should not normally be a problem except in the case where the purpose of the testing is to address issues in the AUT involving multiple displays.

Reproducible: Always

Steps to Reproduce:
1. With an AUT already running on a multi-monitor desktop, drag the main AUT window to a different display.
2. Start Test Execution (with a Test Suite that includes at least one failed test).
3. Observe Test Execution appears to behave the same regardless of which display contains the AUT, however the failure screenshot displayed in the Image View is of the primary desktop, not the one containing the AUT.
Comment 1 Alexandra Schladebeck CLA 2011-11-07 06:20:06 EST
Although it is not explicitly documented at the moment (I'll make sure it gets done today), Jubula does not support screenshots on multi monitors. This is partially because the demand just hasn't been there, and also because an implementation for various toolkits / platforms would not be trivial. For the same reasons, it's not something that we are planning on implementing any time in the foreseeable future. 

From our perspective, I'm going to put this to "wontfix". If anyone wants to submit a patch for the function, we would be interested in including and maintaining it.