Thanks. :)

The examples directory (which actually only contains one example) shows what is the bare minimum needed. You need:

1. A file with the .wire extension with the host and port for cucumber to connect to in features/step_definitions (just like the example). Cucumber automatically finds this 2. An "app" D source file that tells the compiler which modules to look for step definitions in at compile-time. These are passed in as compile-time string parameters to cucumber.server.runCucumberServer (look at examples/source/app.d) 3. Compile the server app with its dependencies by using dub or the build system of choice 4. Run the server, run cucumber in another shell, marvel at the results :P

The only thing that may be confusing in the example directory is the fact that the modules that app.d references are themselves in the `tests` directory. The reason being that I actually use them for unit tests too and as we all know, duplication is bad.

I expect to run the acceptance / feature tests from a shell script that compiles and runs the server, runs cucumber then brings the server down. Now that I think of it it should be possible to do that from Cucumber itself by using `After` and `Before`. I had to do something like that whilst bootstrapping the process and also for some tests I wrote for my MQTT broker. I think this should work but I can't try it right now so don't trust me:

    Before do
      @server = IO.popen("./your_server_name")
      Timeout.timeout(1) do
        while @socket.nil?
          begin
            @socket = TCPSocket.new('localhost', port)
          rescue Errno::ECONNREFUSED
            #keep trying until the server is up or we time out
          end
        end
      end
    end

    After do
      @socket.nil? or @socket.close
      if not @server.nil?
        Process.kill("INT", @server.pid)
        Process.wait(@server.pid)
      end
    end

The reason it should work is that Cucumber supports mixing step definitions in Ruby and over the wire. Which is awesome.

Atila

On Wednesday, 23 April 2014 at 14:58:26 UTC, Jacob Carlborg wrote:
On 23/04/14 15:24, Atila Neves wrote:
Like testing with Cucumber? Wish you could call native D code with it?
Now you can!

http://code.dlang.org/packages/unencumbered
https://github.com/atilaneves/unencumbered

I especially like registering functions that take the parameters with
the types they need from the regexp captures, as well as the
compile-time failures that come from that if done incorrectly.

Now I just need to use in "real life".

This is awesome. I've been thinking several times about implementing something like this. Now I don't have to :)

How do I set up the environment to use this? How complicated is it with the server and wire protocol?

Reply via email to