@lisa.crispin recently asked an excellent question on one of the Slack groups I’m in:
Yesterday I learned that what I mean when I say “continuous testing” and what other people mean when they say “continuous testing” are dramatically different. I’m curious what y’all think of when someone says “continuous testing”? I want to collect as many definitions as I can, now that I know they are not all the same.
One person suggested this representation from @danashby
I was curious though, like Lisa, about what you mean when you say continuous testing?
I just wrote up what I think of when I say “continuous testing” on our Testing in DevOps community site blog: https://testingindevops.org/what-is-continuous-testing/ . Obviously I have a strong view on it, but, I will try to keep an open mind and would love to learn what others think!
For me Continuous Testing is more Omni Testing (or Omnipresent Testing), in the sense that testing is always present during the whole development life cycle.
Some people may thing about Continuous Testing as meaning tests are “continuously” running; these tests are assumed to be automated ones (i.e. automated checks).
In my opinion I would prefer Omni Testing as I see testing as something that is always present, no matter what kind of approach you’re following or at what phase of your development life cycle you are.
You use testing to guarantee and seek a bunch of quality attributes.
I think @danashby and @lisa.crispin see it in a similar way (correct me if not).
My 2 cents
Good point about the small definition. I like yours. I might add, though, that continuous delivery is about delivering small changes frequently without any drama. And I agree, continuous testing is all the tetsing that gives us the confidence to do CD.