Logo: Relish

  1. Sign in

Project: Aruba 0.11.0

Publisher: Cucumber

Debug your command in cucumber-test-run

As a developer
I want to use some debugger in my code and therefor need system() to execute my program
In order to find a bug

Background
Given
I use a fixture named "cli-app"
And
the default aruba exit timeout is 60 seconds
Scenarios
  1. Can handle exit status 0
  2. Can handle exit status 1
  3. You can use a debug repl in your cli program
Can handle exit status 0
Given
an executable named "bin/cli" with: 
#!/usr/bin/env bash

exit 0
And
a file named "features/debug.feature" with: 
Feature: Exit status in debug environment

  @debug
  Scenario: Run program with debug code
    When I run cli
    Then the exit status should be 0
When
I successfully run cucumber
Then
the features should all pass
Can handle exit status 1
Given
an executable named "bin/cli" with: 
#!/usr/bin/env bash

exit 1
And
a file named "features/debug.feature" with: 
Feature: Exit status in debug environment

  @debug
  Scenario: Run program with debug code
    When I run cli
    Then the exit status should be 1
When
I successfully run cucumber
Then
the features should all pass
You can use a debug repl in your cli program

If you want to debug a strange error, which only occures in one of your
cucumber-tests, the @debug-tag becomes handy. You can add @debug in
front of your feature/scenario to make binding.pry or byebug work in
your program.

Please make sure, that there's a statement after the binding.pry-call.
Otherwise you might not get an interactive shell, because your program will
just exit.

We are going to demonstrate this using pry, but any other interactive
debugger for any other programming language should also work.

Given
an executable named "bin/cli" with: 
#!/usr/bin/env ruby

$stderr.sync = true
$stdout.sync = true

require 'pry'
binding.pry

exit 0
And
a file named "features/debug.feature" with: 
Feature: Exit status in debug environment

  @debug
  Scenario: Run program with debug code
    When I run cli
    Then the exit status should be 0
When
I run cucumber interactively
And
I stop the command started last if output contains: 
pry(main)>
Then
the output should match: 
7:\s+binding.pry

Last published about 7 years ago by Max Meyer.