Geb

missing detail in stacktrace

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: None
  • Fix Version/s: 0.5
  • Component/s: Core
  • Labels:
    None
  • Number of attachments :
    0

Description

My first Geb script (intro.groovy, below) fails (below) without enough detail to fix it. The stack trace just says line number 8, the Browser.drive() line, but the script gets past that because I can see it input "wikipedia" in the query field. So, I need to know where it's failing inside the closure.

I'm using Groovy 1.7.4 and Firefox 3.6.12 on Mac OS 10.6.4 and Apple's Java Update 3 (1.6.0_22).

Also, I'd like an option to not close its Firefox, so I can examine what the script is failing on. On the other hand, for a test suite, I'd like an option to take a screen-shot of the Firefox window and a dump of its content files (HTML, CSS, JS, images, etc) at the point where each test script fails.

Issue Links

depends upon

Improvement - An improvement or enhancement to an existing feature or task. GEB-17 Don't wrap exceptions in drive blocks

  • Major - Major loss of function.
  • Resolved - A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.
is related to

Bug - A problem which impairs or prevents the functions of the product. GROOVY-4498 Only the root exception in a script is printed

  • Minor - Minor loss of function, or other problem where easy workaround is present.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
J. David Beutel added a comment -

A lot of the original issue http://github.com/geb/geb/issues#issue/6 didn't make it over, but the gist is that the exception has a cause that's not printed, which has the important line number from the drive() closure.

Should Groovy print the cause chain?

Show
J. David Beutel added a comment - A lot of the original issue http://github.com/geb/geb/issues#issue/6 didn't make it over, but the gist is that the exception has a cause that's not printed, which has the important line number from the drive() closure. Should Groovy print the cause chain?
Hide
Permalink
Luke Daley added a comment -

It probably should but doesn't.

For 0.5, I am going to ditch wrapping the exception with DriveException which should reduce confusion.

Show
Luke Daley added a comment - It probably should but doesn't. For 0.5, I am going to ditch wrapping the exception with DriveException which should reduce confusion.
Luke Daley made changes -
Field Original Value New Value
Link This issue is related to GROOVY-4498 [ GROOVY-4498 ]
Luke Daley made changes -
Link This issue depends upon GEB-17 [ GEB-17 ]
Luke Daley made changes -
Status Open [ 1 ] Resolved [ 5 ]
Resolution Fixed [ 1 ]

People

  • Assignee:
    Luke Daley
    Reporter:
    Luke Daley
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: