Skip to content
This repository has been archived by the owner on Jan 23, 2024. It is now read-only.

Using with Continuous Integration Systems #509

Open
nwams opened this issue Nov 11, 2020 · 2 comments
Open

Using with Continuous Integration Systems #509

nwams opened this issue Nov 11, 2020 · 2 comments

Comments

@nwams
Copy link

nwams commented Nov 11, 2020

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!

@Jammjammjamm
Copy link
Contributor

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:

  - rvm install ruby --latest
  - git clone --single-branch -b development https://github.com/onc-healthit/inferno.git
  - cd inferno
  - bundle install
  - RACK_ENV=test rake db:setup
  - rake inferno:execute_batch[../.inferno.json]

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

@guybartal
Copy link

guybartal commented Jun 23, 2021

Hi,

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 free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants