cucumber / cucumber/godog

JetBrains GoLand Cucumber/Gherkin support for godog

Open
#128 4 comments 7 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
2.7k
Forks
280
Avg merge
2d 20h
Merged PRs (30d)
2

Description

Hey there,

I'm a huge fan of Cucumber in Ruby, and am now starting to learn Golang. I was able to get the Gherkin plugin installed to GoLand and the features formatter works great! I installed the Golang Cucumber module godog via:

$ go get github.com/DATA-DOG/godog/cmd/godog

godog homepage: https://github.com/DATA-DOG/godog

I was able to work all the way through FizzBuzz on the command line using godog, yea!

https://github.com/ssmythe/fizzbuzz_using_godog

In GoLand, the step_definitions highlighter obvious doesn't know what to do in the features file, since there's no mapping to the _test.go files. A big difference in how godog supports step_definitions is how it requires the _test.go files in the root directory. Kinda weird, since I really liked having them tucked under the features/step_definitions directory in Ruby.

I'm still working out how to get godog to work with 'go test' on the command line. I'm getting some errors still, but I'm hoping I'll get it soon.

I'm dreaming of the day when godog auto-run test support can be integrated into GoLand much the same way Cucumber is in RubyMine. :-)

Keep up the awesome work godog team!

---- UPDATED: Fri Apr 27 8:42 PM PST

Well, it looks like I got it to work with 'go test', but the test runner in GoLand doesn't seem to like the output to be able to parse the output like it does in RubyMine for Cucumber.

Any suggestions on output formatting so GoLand can parse it?

The automatic test runner works now too! :-D Whoo hoo!

Contributor guide

Open the contributing guide

Research direction

Reproduce the reported workflow with the godog _test.go files in the repository root, go test, and GoLand's test runner. Start by comparing the runner output with what GoLand expects; done would require a clearly defined, parseable integration path for automatic godog test execution.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
developer-experience, testing
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.