godog does not print stack trace when panic is caught about godog HOT 4 CLOSED

Hi, thanks. That is something what needs to be improved. Currently caught panics does not print stack trace, which needs to be changed. probably an error should have a different type similar to https://github.com/pkg/errors so it could print stack trace in verbose mode on %+v

Currently what I suggest you to do, is catch panic in your step in order to debug the reason. Later when I have some more time, I will revisit this. The issue is important but not critical to behavior. Thanks for reminding.

from godog.

Thx @l3pp4rd , how do I print a stack trace if all print statements are swallowed?

from godog.

to replicate it, lets simply create a small feature:

Feature: panic

  Scenario: panics
    Then fail with panic

Now implement the panic step in _test.go file.

package main

import (
    "fmt"

    "github.com/DATA-DOG/godog"
)

func myStepCallsFunc() {
    arr := make([]int, 0)
    fmt.Println(arr[6])
}

func failWithPanic() error {
    myStepCallsFunc()
    return nil
}

func FeatureContext(s *godog.Suite) {
    s.Step(`^fail with panic$`, failWithPanic)
}

Run it:

Then lets print stack trace of panic instead.

package main

import (
    "fmt"
    "runtime/debug"

    "github.com/DATA-DOG/godog"
)

func myStepCallsFunc() {
    arr := make([]int, 0)
    fmt.Println(arr[6])
}

func failWithPanic() (err error) {
    defer func() {
        if r := recover(); r != nil {
            err = fmt.Errorf("runtime error: %s", r)
            debug.PrintStack()
        }
    }()
    myStepCallsFunc()
    return
}

func FeatureContext(s *godog.Suite) {
    s.Step(`^fail with panic$`, failWithPanic)
}

And you see the output now:

from godog.

The simple answer is to use "log" which still outputs. Apologies for the noise.

from godog.