Open coopernetes opened 6 months ago
Hi, does this issue need to be looked at?
@marksmith388 - for sure! Wanna tackle it? 😇
Absolutely!
I have a working solution using goss, what are my next steps?
@marksmith388 - thanks for joining the community call today and apologies for missing your message from last week 🤗
@coopernetes - can we define a number of test requirements for this ticket to make sure @marksmith388 has something clear to work towards?
Of course appreciate you said you would both follow up on Slack but posting here to serve more as a small reminder in any case 💡
We have a collection tests that validate git-proxy internals but nothing which runs in CI that validates changes acting as a client integrating with the git-proxy server(s). Tests should be run (at least on main or pre-release) to validate the server's behaviour end-to-end using a tool like serverspec or goss.
Another option would be a simple Docker-based test (package the app, run a container, run an HTTP-based test through it and shut down the container). container-structure-test is an option there. The below is an illustrative example - it's not a working test but should give an implementer a starting point.
Originally posted by @lwhiteley in https://github.com/finos/git-proxy/issues/379#issuecomment-1879082571