-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
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
Specify Results directory #89
Comments
Hi, I had the same idea and started working on it. Only problem was getting it to work on windows as well. On linux I could use |
Wow, that was blazing fast. I don't want to be selfish (;-)), but I think its a good idea to publish the feature for all OSes that can easily be supported. Other OSes might follow when someone with Windows Know-How steps by. |
I can publish what I have so far and then we could update the docs accordingly stating that this option only works for linux/macos based systems :) |
I am definitely interested in this as well, I would love to be able to capture the output to add it to CI job reporting! |
This is timely. I was just looking at a way to make it so that the Goss testing output wasn't simply piped to This improvement should allow me to easily configure the output file as an artifact to be uploaded to our build pipeline's artifacts section. Is there anything I can do to assist in getting these two relevant PRs merged and released? |
Also, @FalcoSuessgott, Windows/Powershell has |
👋🏽 Little bump here! :) It would be VERY usefull! |
Hello,
thanks for this useful provisioner. Is there a way to save the testresults in a file so that I can later upload it to my CI/CD Environment? It can deal pretty good with junit output, and would also give me statistics about each tests runtime.
Best regards :-)
The text was updated successfully, but these errors were encountered: