- From: Lamont Granquist <
>
- To:
- Subject: [chef] Re: Re: Re: Re: Re: Re: Re: Re: Testing Cookbooks vs Testing Infrastructure
- Date: Wed, 22 Apr 2015 14:25:52 -0700
On 4/22/15 2:02 PM, Zac Stevens wrote:
"
type="cite">
This may be philosophical naval gazing.
The way that I'd test a cluster end-to-end would be to consider the
load balancer part of the cluster and it should issue API calls to
its own VIPs and should also assert that the health checks of all of
its servers are healthy. But the way that I express that is via the
load balancer testing itself, but that API is the externally
available interface to the cluster which is what you are going to
test against for 'integration' or 'end-to-end' tests.
So I suspect we get the same test coverage, but I think its
important the way that I state who is responsible for testing what,
and I don't see the need for 'external' testing and more pieces
bolted onto the infrastructure to do 'new' kinds of tests. I think
the tools are already mostly there if you squint at it, and I agree
that chef-provisioning and test-kitchen and serverspec/bats/etc seem
to be the way forwards to deliver the whole thing and it will evolve
to provide it. All we need is to make test-kitchen more
cluster-aware and then the process of simply being able to spin up
the cluster, login and converge chef on everything and then run the
tests on each individual node should be sufficient. Even though
there's no overall end-to-end testing framework being additionally
added into test-kitchen, I don't think you'll miss it since by each
node testing itself they also test their dependencies (it isn't like
unit testing because you'll really be communicating with all your
neighbors and not stubs or mocks of your neighbors -- if you fully
test yourself, you should have also fully tested all of your
adjacent dependencies and the whole should really be the sum of the
parts).
|
- [chef] Re: Testing Cookbooks vs Testing Infrastructure, (continued)
- [chef] Re: Testing Cookbooks vs Testing Infrastructure, Tensibai, 04/22/2015
- [chef] Re: Re: Testing Cookbooks vs Testing Infrastructure, Tensibai, 04/22/2015
- [chef] Re: Re: Re: Testing Cookbooks vs Testing Infrastructure, Torben Knerr, 04/22/2015
- [chef] Re: Re: Re: Re: Testing Cookbooks vs Testing Infrastructure, Tensibai, 04/22/2015
- [chef] Re: Re: Re: Re: Re: Testing Cookbooks vs Testing Infrastructure, Torben Knerr, 04/22/2015
- [chef] Re: Re: Re: Re: Re: Re: Testing Cookbooks vs Testing Infrastructure, Morgan Blackthorne, 04/22/2015
- [chef] Re: Re: Re: Re: Re: Re: Testing Cookbooks vs Testing Infrastructure, Mike, 04/22/2015
- [chef] Re: Re: Re: Re: Re: Re: Testing Cookbooks vs Testing Infrastructure, Lamont Granquist, 04/22/2015
- [chef] Re: Re: Re: Re: Re: Re: Re: Testing Cookbooks vs Testing Infrastructure, Zac Stevens, 04/22/2015
- [chef] Re: Re: Re: Re: Re: Re: Re: Re: Testing Cookbooks vs Testing Infrastructure, Lamont Granquist, 04/22/2015
- [chef] Re: Re: Re: Re: Re: Re: Re: Re: Testing Cookbooks vs Testing Infrastructure, Lamont Granquist, 04/22/2015
- [chef] Re: Re: Re: Re: Re: Re: Re: Re: Re: Testing Cookbooks vs Testing Infrastructure, Torben Knerr, 04/22/2015
- [chef] Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Testing Cookbooks vs Testing Infrastructure, Zac Stevens, 04/23/2015
- [chef] Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Testing Cookbooks vs Testing Infrastructure, Cassiano Leal, 04/23/2015
- [chef] Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Testing Cookbooks vs Testing Infrastructure, Torben Knerr, 04/23/2015
- [chef] Re: Testing Cookbooks vs Testing Infrastructure, Zac Stevens, 04/23/2015
- [chef] Re: Re: Re: Re: Re: Re: Testing Cookbooks vs Testing Infrastructure, Tensibai Zhaoying, 04/22/2015
Archive powered by MHonArc 2.6.16.