You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 23, 2024. It is now read-only.
Those instructions aren't totally up to date, but still look mostly correct. Really, it's following the instructions for running tests from the command line and doing whatever your CI system needs to make that happen.
For travis, I think the script would now look more like this:
You will probably want to clone from your own fork of inferno so that you can update the config.yml (or have some other way of getting your own config.yml into your CI system).
We are also looking into ways to automate Inferno tests, is there a way to export all test results in a structured format so we could display a nice report inside our DevOps solution?
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi there,
I started looking into ways to automate Inferno tests via the Running Tests from the Command Line section.
And now I'm exploring integrating Inferno in our CI pipeline. I stumbled upon these instructions in the Wiki: https://github.com/onc-healthit/inferno/wiki/Using-with-Continuous-Integration-Systems
Would you say that these instructions are still relevant for how Inferno Program Edition operates today?
Just asking because I noticed it was published in 2018.
Thanks!
The text was updated successfully, but these errors were encountered: