We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
It would be helpful to provide just the tests directory on command line. Then the tool would iterate over all tests it finds and runs the tests.
e.g.
scripts +- scripts1 +- script1.tick +- scripts2 +- script2.tick tests +- test1.yaml +- test2.yaml
And running: kapacitor-unit --dir scripts --tests tests/
kapacitor-unit --dir scripts --tests tests/
The tool would then execute all tests it finds from the directory
The text was updated successfully, but these errors were encountered:
Yep, this sounds like a good improvement! Would you push the ball forward @vhartikainen ? 😃
The cli already parses all the tick scripts in a directory when input in --dir script. Maybe that code can be reused?
--dir script
Sorry, something went wrong.
A big maybe from me 😏 Never written a single line of Go, but I'm willing to give it a go.
No promises on estimate when to be finished though 😄
Pr #33 accomplishes this. It checks the --tests config to see if it's a dir or a yaml file before parsing so it's backwards compatible.
No branches or pull requests
It would be helpful to provide just the tests directory on command line. Then the tool would iterate over all tests it finds and runs the tests.
e.g.
And running:
kapacitor-unit --dir scripts --tests tests/
The tool would then execute all tests it finds from the directory
The text was updated successfully, but these errors were encountered: