Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 367156 - Dual-screen setup can cause Action Errors when executing click test steps
Summary: Dual-screen setup can cause Action Errors when executing click test steps
Status: CLOSED WONTFIX
Alias: None
Product: Jubula
Classification: Technology
Component: Core (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 minor (vote)
Target Milestone: Indigo SR2   Edit
Assignee: Project Inbox CLA
QA Contact: Oliver Goetz CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 515745
  Show dependency tree
 
Reported: 2011-12-20 04:14 EST by Martin Müller CLA
Modified: 2017-04-25 05:38 EDT (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 Martin Müller CLA 2011-12-20 04:14:37 EST
Build Identifier: 1.1.0

When using a dual-screen setup with a monitor to the left of the main screen this monitor is adressed using negative X-values causing Jubula to assume the coordinates are invalid. Hence, executing a click test step with any negative coordinates causes an Action Error "Point to click (-998, 401) is outside of screen bounds".
The same Action Errors occur when Jubula comes across negative Y-values, such as with a monitor above the main screen.

Reproducible: Always

Steps to Reproduce:
1. Set up a secondary screen to the left of the main screen.
2. Move the AUT onto the left screen
3. Execute a click test step
Comment 1 Alexandra Schladebeck CLA 2012-01-04 08:50:20 EST
Hi,

We do not currently support multi-monitor setups. We have neither tested what does work, nor have we evaluated the feasibility of adding support for this kind of environment. This is partially because of the relatively small amount of use cases that require multi-monitors and partially because of the effort that would be involved in testing such support for all actions, on a variety of platforms and window systems. 

If it's avoidable in your use case, I would avoid it. You could try using positive coordinates and see whether Jubula interprets them correctly, but I don't know whether this would work all or even some of the time. 

I'm going to set this to won't fix, as it currently isn't high on our list of priorities to look at.