Community
Participate
Working Groups
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.
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.
Created attachment 207642 [details] Screenshot
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.
Fix verified manually: table entries are now recognized and can be checked
