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

Support for test output formats like JUnit #37

Open
MMerzinger opened this issue Jul 3, 2021 · 2 comments
Open

Support for test output formats like JUnit #37

MMerzinger opened this issue Jul 3, 2021 · 2 comments
Labels
enhancement New feature or request

Comments

@MMerzinger
Copy link

MMerzinger commented Jul 3, 2021

Hello,

I use cryptonice often to verify if my internet facing endpoints are configured properly. This configuration is done in K8s or on a cloud platform such as Azure with Azure Resource Manager templates. As soon as I test changes I need to re-run cryptonice to verify the changes. I can do this in a pipeline as a post-deployment step, but I have to go through the agent logs to check the cryptonice output. To simplify this step, it would be handy if cryptonice supports output formats such as JUnit, which can be visualised by all common CI/CD solutions.

Please let me know what you think about this enhancement.

Thank you and regards
Marc

@warburtr0n warburtr0n added the enhancement New feature or request label Jul 5, 2021
@warburtr0n
Copy link
Contributor

Hi @MMerzinger thanks for the suggestion. This makes complete sense and I'd love to implement it. It's not an insignificant amount of work, however, so I'll add it to the list of enhancements and think about when I might be able to get to it.

@MMerzinger
Copy link
Author

Hi @warburtr0n,

thank you for the positive feedback.

I agree about the effort. Will you link the implementation to this issue? I would be happy to test the feature.

Regards
Marc

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants