Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
New option extraGlue in @CucumberOptions - adds packages to search, keeping default package
See original GitHub issueSummary
It would be nice to have a new option in @CucumberOptions to specify packages to search for glue in addition to the default search path.
Context & Motivation
The glue option in @CucumberOptions allows the glue search path to be specified, but it it is used, the default path (the current package) is not considered (unless it’s also included in the list passed to glue).
It would be nice to have an option, say extraGlue that allows packages to be added to the search path, in addition to the current package. It would be useful in adding common steps and especially hooks.
Possible Solution
I’ve looked at the code and I believe I can provide a pull request implementing this (including tests). I’m just checking before if someone would be against this feature.
Issue Analytics
- State:
- Created 5 years ago
- Comments:7 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Ideally you put the runner one level above your glue and features. This means you dont have to configure them.
However this also means you can’t add extra glue from a library that is a sibling package of your Runner.
When no glue is provided the glue defaults to the package of the runner (the class annotated with
@CucumberOptions).When glue is provided this default is ignored. Not so with extra glue.