These are chat archives for mojotech/pioneer

11th
Oct 2014
Dominik Guzei
@DominikGuzei
Oct 11 2014 16:56
Hey @samccone is there a way to provide config vars per argv arguments instead of a config file?
Sam Saccone
@samccone
Oct 11 2014 16:57
yep
it should be able to be run only via config flags
that is how we do it in grunt-pioneer
Dominik Guzei
@DominikGuzei
Oct 11 2014 16:57
but does it also work with new Pioneer()?
ok ill have look there
is this the trick: global.ARGV = Array.prototype.slice.call(process.argv);?
because all grunt-pioneer does is this: proc = spawn './node_modules/.bin/pioneer', execOptions
my problem is, I have to provide a dynamic path to the feature/require files of the configuration
Sam Saccone
@samccone
Oct 11 2014 17:02
yeah i see the issue
hmmmmmmmmm this needs to be better :(
Dominik Guzei
@DominikGuzei
Oct 11 2014 17:02
i could generate the config file before running
Sam Saccone
@samccone
Oct 11 2014 17:02
it is all debt because of the ghetto way we have to use cucumber
Dominik Guzei
@DominikGuzei
Oct 11 2014 17:03
it would be cool if we could tell cucumber from which directory to run
Sam Saccone
@samccone
Oct 11 2014 17:03
i agree
Dominik Guzei
@DominikGuzei
Oct 11 2014 17:03
since I instantiate pioneer from a process that lives somewhere else than my test files i can't just say tests/features
Dominik Guzei
@DominikGuzei
Oct 11 2014 17:23
ok generating the config file before running does work ;-) its not beautiful but gets the job done
Sam Saccone
@samccone
Oct 11 2014 17:23
blah
ok well at least you got it working
Dominik Guzei
@DominikGuzei
Oct 11 2014 17:24
yeah – this was pretty important, I hope I can access my app environment from within the tests now