Replies: 1 comment
-
See if you like it :) |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
These are the bones of a testing system that runs locally and in CI. It needs work as there are side issues too.
It's all based on reusing the make files for local and CI testing.
all-ci tests everything, making sure all deps are installed.
Your basically making github bend to your will, by directly installing and running golang code at runtime bypassing docker, etc
This allows you to run your testing infrastructure anywhere.
bin-install will install he golang thing your testing.
caddy gives you the https you need often locally. YOu need ot run a server somewhere with it and use NATS to drive it, where you infect the binary and caddy servers it and Git hub actions call it.
This is all because github wont give you a Server locally, so you just run on one fly with caddy and then your binary behind caddy.
github runs on linux, mac and window. So testing there is easy.
github can not run mobile OS's:Mobiles need to be local connected to a laptop over USB, and github actions then drives them over NATS. You tell the mobile to install the app and test it.
Its exactly the same as what we are doing on fly.
saucelabs can also be used: https://github.com/saucelabs/saucectl
For external services outside your control you can run go tests to capture their output.
root makefile of repo:
caddy.mk
github action:
Beta Was this translation helpful? Give feedback.
All reactions