Skip to content
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

Open
la7eralus opened this issue May 17, 2024 · 6 comments · May be fixed by #100
Open

Specify Results directory #89

la7eralus opened this issue May 17, 2024 · 6 comments · May be fixed by #100

Comments

@la7eralus
Copy link

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 :-)

@FalcoSuessgott
Copy link
Collaborator

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 tee to redirect the output to a file. Im not aware there is a command for that on windows… Or we accept that the feature is only available on linux systems ..

@la7eralus
Copy link
Author

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.

@FalcoSuessgott
Copy link
Collaborator

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 :)

@wazoo
Copy link

wazoo commented Jun 7, 2024

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!

@mattlorimor
Copy link

This is timely.

I was just looking at a way to make it so that the Goss testing output wasn't simply piped to stdout.

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?

@mattlorimor
Copy link

Also, @FalcoSuessgott, Windows/Powershell has Tee-Object.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
4 participants