provide a stub back end so we can test forge in isolation with no OpenShift / Github / Auth cluster

[jstrachan]

to simplify unit tests it'd be awesome to be able to test the forge commands using the regular forge testing framework and stubbing out the back ends (Auth, OpenShfit, Github).

• OpenShift there's work in the kubernetes-client ecosystem to create a simple mock OpenShift cluster that we can run against and perform asserts after the test (that the required BuildConfig, Secret, ConfigMap are created etc)
• github is the trickiest - there's a pending issue against the github client to add a stub implementation: https://github.com/kohsuke/github-api/issues/382 that will let us create repos and query the created repos but not talk to the github back and at all
• auth is a little easier since its a simple GET on the auth URL; we just need a little http server on localhost to mimick that one

[bartoszmajsak]

Forge Test Harness is a dead end at this point - it takes minutes to run a simple test. We tried it with @corinnekrych.

For the other points, I might have something working very soon.

[jstrachan]

awesome!

BTW on the kubernetes/openshift side of things we've a stub/mock implementation in kubernetes-client : https://github.com/fabric8io/kubernetes-client/tree/master/openshift-server-mock which provides openshift/kubernetes support on top of https://github.com/fabric8io/mockwebserver