Testing environment / templates

[mag37]

As suggested by @yoyoma2 in #131 (comment)

Would it be possible to have in github a docker-compose.yml that specifies a bunch of image tags not latest and an identical docker-compose.yml that specifies image tags of latest to facilitate/accelerate dockcheck.sh testing? If dockcheck's github provided such testing docker-compose.yml's, myself and others with few images could contribute more to testing large image count issues such as this one.

I think this is a good suggestion and I'm open for suggestions on test-templates or similar.

I'll also need to take a look at errorCheck.sh to keep it up to date with the main script.

So please contribute with ideas or code snippets or any input! Thank you folks for being involved.

[yoyoma2]

If it's a test script it would be good if it could use or even download a dockcheck.sh from main or development branch to a testing directory so users could try out a new/in progress dockcheck.sh version before putting it in production.

[yoyoma2]

One thing I find difficult about testing dockcheck is that is depends on what's available on docker hub. I wonder if a test script could set up a local registry and populate it with various scenarios and test against it.

Seems like too much work for what it's worth but just brainstorming. Aside from an occasional minor glitch, staying on the latest dockcheck has been relatively stable even with the best effort manual testing currently being done.

[mag37]

Yeah, I usually have enough machines with enough stacks to do a bunch of testing without running out of new images.

But I've been playing with the same idea, setting up a local repo with a few custom images that could just be rebuilt locally.

But currently I just need to write something that plows through a few different scenarios.

I've manually fixed up some things like labels, env files, multi composes, locally built, a few different notification channels etc. And just try to test as best as I can when something big changes.