Step definitions as dynamic libraries about cucumber-cpp HOT 8 CLOSED

Hmmm... again, I think going the other way around may be better. I already have a working runner that handles launching the cpp side using native hooks in cucumber. I think that would be better and easier to contain.

I don't think it would take much more work to handle the --glue args as well, and that would be a nice addition.

Let me know if you are interested in a pull request... ;)

from cucumber-cpp.

Shouldn't this be closed now? With the latest cucumber-cpp, I can run tests selectively with:

cucumber features/foo.feature:34

from cucumber-cpp.

@paoloambrosio can you answer that? I don't know what the goal of this issue originally was. Your description seems to be less about dynamic libraries and more about control over which step definitions run at what time (with dynamic libs as a possible solution to that).

from cucumber-cpp.

Running features with something like features/foo.feature:34 is implemented in Cucumber-Ruby. This was about loading step definitions from dynamic libraries.

I've updated the description.

from cucumber-cpp.

Except for the dynamic library portion (startup and invoking) your describing a script a Python I wrote for our company's CI system: it starts the wire server, writes a cucumber.wire file with the right details and then starts cucumber with some parameters passed through. That's combined with some process monitoring to ensure proper handling of exit codes and standard output/error.

from cucumber-cpp.

I'm going to close this and some other outdated issues if that's OK.

from cucumber-cpp.

Sure.

I think the dynamic-lib aspects are already addressed by your thread on cukes-devs btw: https://groups.google.com/forum/#!topic/cukes-devs/vYLS-Pv8oNo

from cucumber-cpp.

Closing due to inactivity.

from cucumber-cpp.