How do I test my catalogue entry?

[errordeveloper]

I'd like to be able to spin up a cluster and install new version of my thing in at least semi-automated way (i.e. one or two commands). I am happy with Vagrant or any cloud or whatever is good place for doing this.

[nevotheless]

To give an answer to the initial question "How do I test my catalogue entry?" first:

• You can either log into your docker host machine and do something like docker-compose my-test-template.yml
• Or within the Rancher UI, you can navigate to Stacks -> Add Stack and put your template file(s) in there to spin up your thing.

---

I don't know what you mean with the rest of your question, please be more specific if the answers above couldn't help you.

[mathuin]

@ununseptium Your approach would effectively test the docker-compose.yml and rancher-compose.yml but wouldn't help with the catalog-specific stuff like config.yml and answers.txt.

I will be submitting a PR with an additional catalog entry. I currently plan to test that PR by creating a brand new Rancher server, environment, and host a la Rancher on a laptop -- if there exists some kind of test suite which is superior to this approach, please let me know!

[errordeveloper]

When I've opened this issue, is some kind of automated test I could run to validate changes... In fact, I'd be quite happy with linter script of sorts too.