More in-depth testing

[crimsonfaith91]

Existing smoke tests only cover limited test paths for meta-controllers. For example, the tests do not cover whether a resource is namespaced or not. As the project becomes larger, perhaps it is time for us to write more in-depth tests like e2e and integration tests.

@enisoc

[enisoc]

In #136 I've added an integration test framework, and these tests now run in Travis along with unit tests.

I've also briefly described the testing philosophy in the contributor docs:

https://metacontroller.app/contrib/build/#tests

Next, I plan to flesh out the set of integration tests since this is where the most interesting aspects of Metacontroller should be tested, as described in the above doc.