using the junit formatter doesnt work

[wickett]

using --format junit doesnt work because underneath gauntlt, cucumber wants a --dir passed to it.

[karebear90]

any work arounds for this? i'm running into the same issue.

[Gaurang033]

I am also facing the same issue, I need to generate the JUnit xml, however if I run the command without --out option it gives following error.

You must specify --out DIR for the junit formatter

If i provide --out parameter, then I get following error.
Error: unknown argument '--out'.

would someone please let me know how to generate the JUnit report

[mjgorman]

+1 Have the same issue.

[frameloss]

I realize this doesn't really contribute to the fix of this issue, but for those held-up by this issue there is an easy workaround. In your working directory create the file './config/cucumber.yml' and add the --out setting there ... for example:

default: --format junit --out /var/tmp/gauntlt/blog/junit

I found that I had to use a fully-qualified path, but that is an easy problem to work around in your CI jobs. Hope that helps. Also if I specified a path to the attack files it also didn't work, example shell script that worked:

#!/bin/bash
set -vx

# make sure junit output dir exists, and is empty of earlier results:
mkdir -p /var/tmp/gauntlt/junit
rm -f /var/tmp/gauntlt/junit/*xml

# make sure we are really relative to the files
cd $(dirname $(readlink -f ${0}))

/usr/local/bin/gauntlt

Note: edited to correct an error in the example and to cover a couple of cases where this workaround didn't actually work. Second edit ... file name is cucumber.yml, not .config ... oops.

[MrSecure]

I believe this is fixed in #96