This allows one to accommodate a lot of atypical situations, where rspec (for example) needs to be supplied with additional arguments (like a load path, a pattern, etc).
We do not yet support supplying this configuration on the CLI, but each tool may supply a command and/or exec_command value in the yaml config. If it does, that will be used instead of the built-in command (note that RelevantRunner will still suffix the list of files in the usual cases).
Updating your config file to add rspec: { exec_command: ["rspec", "-f", "d"] } for example will make qq -Xrspec run in documentation format. Though that's a lot of output in most test suites :-)
This allows one to accommodate a lot of atypical situations, where rspec (for example) needs to be supplied with additional arguments (like a load path, a pattern, etc).
We do not yet support supplying this configuration on the CLI, but each tool may supply a
commandand/orexec_commandvalue in the yaml config. If it does, that will be used instead of the built-in command (note that RelevantRunner will still suffix the list of files in the usual cases).Updating your config file to add
rspec: { exec_command: ["rspec", "-f", "d"] }for example will makeqq -Xrspecrun in documentation format. Though that's a lot of output in most test suites :-)