New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Request: option to provide features not from filesystem #328
Comments
Sounds interesting, maybe when building the godog testrunner we could have an include functionality that would embed the feature dirs/files you pass as arguments. Something like: |
Yep that’d be nice. We have our own golang cli that uses the godog package directly so wouldn’t immediately need the cli option, but I do like the idea of including packaged feature files in the godog cli tool itself |
Were you thinking something like:
and let your code read the content from pkger? |
Looking for the exact same functionality. |
@lcarrazana would you want to use it in a similar way as zhammer, or would you use the godog CLI directly? |
Now that Go provides standard We can follow the approach used in https://github.com/pressly/goose/pull/244/files (setting base fs of runner and keeping paths) to implement such feature with minimal API changes. |
Done with #476. |
Hi, I'm curious if y'all would be up allowing a way to provide feature files to
godog.TestSuite
that is not just passing file paths. Our use case is that we'd like to package a test tool as a binary using godog and ship features as static files in the binary using https://github.com/markbates/pkger. Here we'd have he feature file bodies and names; however, the TestSuite wouldn't be able to parse them from a list of filesystem Paths.Happy to discuss different ways this could work!
godog/options.go
Lines 54 to 55 in 28ad994
The text was updated successfully, but these errors were encountered: