A short note highlighting key facts related to tests in the DevOps practice

1. page 1 / 1
DevOps : the importance of Tests
Recently, I read few articles emphazing the role and status of Tests within an R&D
organization when it goes to « DevOps », Cloud / SaaS, « Continuous Delivery »…
I strongly recommend the lecture of the McKinsey article (« Finding the speed to
innovate ») which has inspired this note. Among the ideas developed in these
articles :
 the need for a strongly synchronized organization of tests and
development walking on two legs :
- high level tests done by the developers themselves (in order to ensure the
quality and reduce the time of test phases)
- fast standardized and/or automated tests able to run rapidly a global testing
phase.
In some companies, part of the success of this ideas lied in the reassignment of
one or two talented developers to tests and on more time allocated to tests in the
developers’ schedule.
 « test-driven-development »
or « test first » meaning that the tests have to be thought during the initial phase of
development and developers should be sensitive to the quality guidelines and
reflect them in their code.
 new organization of versioning and codes characterized by two main ideas :
- a « single source of truth »: each version of code should be stored in a very
well repository so that the testers can organize themselves and ensure the
testing of each new development ;
- a modular organization of the code with as limited as possible quality impact
of a new module development to another module. This facilitates and reduce
sthe duration of tests.
More in :
http://www.mckinsey.com/insights/business_technology/finding_the_speed_to_innovate
didier Robert
https://www.linkedin.com/in/didierrobert
…/…
1note