Open Stack

On Fri, May 2, 2014 at 2:32 PM, matt <matt at nycresistor.com> wrote:

> I am all for enforcing CI.  But, my understanding of the workflow is code
> doesn't go in without unit tests.  Frankly you guys removing sections of
> code for not having proper unit testing is downright terrifying.  Doubly so
> when it's major feature sets.

You are misunderstanding what we mean by CI in this case. We have unit
tests (although the coverage isn't always great, but its pretty much
on par with every other software project), but what we're talking
about here is tempest tests -- which are scenario tests. Things like
does booting a virtual machine actually work. Does getconsolelog()
actually return a console. etc etc.

We're raising the bar on testing. That's always a good thing. Worrying
about what we had in the past doesn't really help, because there's
nothing I can do about that.

Michael

-- 
Rackspace Australia