Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 363815 - Recording Selection of Table Cell shows IndexOutOfBoundException
Summary: Recording Selection of Table Cell shows IndexOutOfBoundException
Status: CLOSED WONTFIX
Alias: None
Product: Jubula
Classification: Technology
Component: Agent (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact: Oliver Goetz CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-11-15 08:17 EST by Felix Ziesel CLA
Modified: 2012-12-07 02:37 EST (History)
2 users (show)

See Also:


Attachments
StackTrace (2.13 KB, text/plain)
2011-11-15 08:17 EST, Felix Ziesel CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Felix Ziesel CLA 2011-11-15 08:17:04 EST
Created attachment 207022 [details]
StackTrace

This error can be reproduced using the DVDTool example

1. Create a simple project starting the AUT for the DVDTool.
2. Create a new DVD
3. Start recording mode
4. Click inside the any table cell

The appended stack trace occured. 
No test step will be created for the selection.
Comment 1 Peter Hancox CLA 2012-07-31 22:13:50 EDT
I am experiencing exactly the same problem with the Juno release on our Java application when selecting a cell within a table.  Only occurs when running in observation mode.

Can't find any explanation as to why this is closed with status "INVALID" ?
Comment 2 Alexandra Schladebeck CLA 2012-08-01 02:24:44 EDT
I believe this has been marked as invalid because the bug was also open in the GUIdancer Bugzilla: 
https://bxapps.bredex.de/bugzilla/show_bug.cgi?id=176

For simplicity, I'm going to close that bug and reopen this one.
Comment 3 Alexandra Schladebeck CLA 2012-08-01 02:25:52 EDT
Short update: the bug in the GUIdancer Bugzilla is also being left open as there are also other people as cc on it. When we close this bug, we should also close that one.
Comment 4 Alexandra Schladebeck CLA 2012-12-07 02:37:58 EST
Marking this bug as wontfix. The observation mode is not our focus as it really only should be used for:
- Trying out basic steps at the beginning to find out what sort of actions are available / how Jubula "thinks".
- At a push, for quickly collecting components and generating reasonable technical names for them. 

The workaround is to specify tests using the unbound modules.