Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 362673

Summary:

CaA - RCP: Table - Check Existence of value in Column fails with index out of bounds

Product:

[Technology] Jubula

Reporter:

Markus Tiede <markus.tiede>

Component:

Assignee:

Markus Tiede <markus.tiede>

Status:

CLOSED FIXED

QA Contact:

Oliver Goetz <Oliver.Goetz>

Severity:

critical

Priority:

CC:

alexandra.schladebeck

Version:

1.1.0

Target Milestone:

Juno M6

Hardware:

All

OS:

All

Whiteboard:

Attachments:

Description	Flags
Testexecution log of executed test	none
Screenshot	none

Description Markus Tiede

2011-11-02 09:39:44 EDT

Invoking the action "Table - Check Existence of value in Column" fails with an index out of bounds exception on certain "Eclipse"-tables. This internal IOOB is also displayed in the client.

Steps to reproduce:
 * download Eclipse 3.7.1 
 * start Eclipse as an AUT and open the java class editor
 * invoking code completion in the editor IDE and map this appearing "list" (which is technically a table)
 * invoke "Table - Check Existence of value in Column" for an existing entry --> IOOB is display in the client when trying to access a table entry.

This issue is critical as it prevents other eclipse projects (like Eclipse Code Recommenders) from using Jubula.

Comment 1 Markus Tiede

2011-11-29 02:13:46 EST

Created attachment 207641 [details]
Testexecution log of executed test

It's interesting that other code completion proposals such as ".*syserr.*" and ".*sysout.*" are tested successfully though the "System" check fails. Please also see the attached screenshot for further information.

Comment 2 Markus Tiede

2011-11-29 02:14:08 EST

Created attachment 207642 [details]
Screenshot

Comment 3 Markus Tiede

2011-11-29 05:13:34 EST

This issue should be fixed with changeset

http://git.eclipse.org/c/jubula/org.eclipse.jubula.core.git/commit/?id=bfcee10cc23e9c24b51690a3593c34066b01a8a6

The problem occurred due to the fact that we did not check whether a table header was present or not - which access though not existing caused the IOOB.

This also explains the behavior that some *existing* values succeeded and non-existing caused this problem as we checked the header value at last. 

The "System" check failed previously, as "System" did not match the whole table cell content which is "System - java.lang" - this was my test specification fault.

Comment 4 Oliver Goetz

2011-12-06 09:19:19 EST

Fix verified manually: table entries are now recognized and can be checked