Skip to main content

DevOps Testing – Do it Right

One of the key principles of DevOps stresses that we need to fail and fail fast.   A key part that frequently gets omitted.  That key element of the principle is that we fail fast so that we can LEARN. When we learn it is always best to act and to share.   In the spirit of learning and sharing here are some consequences of not performing DevOps testing properly that might help to mitigate some of your challenges.

Consequences of NOT doing DevOps testing properly – challenges and thoughts

Culture Conflict
Culture Conflict can exist between business leaders, developers, QA testers, infrastructure/tools staff, operations staff or any stakeholder in the entire value stream. When there are unclear roles and responsibilities for the testing of a new or changed service or product, a friction begins.  This friction propagates conflict.  Be aware.  Make management of organizational change a priority.

Test Escapes (False Positive)
          False Positive Test Escapes occur when the DevOps testing strategy is not
optimized across the DevOps pipeline because tests may not be sufficient to catch defects before the next stage in the pipeline, ultimately resulting in problems deployed to customers.  Do not underestimate the value of a good testing strategy for the DevOps framework that is integrated end to end.  Accelerate and automate when and where you can.  Know the DevOps Pipeline.

Test Escapes (False Negative)
False Negative Test Escapes occur when DevOps testing infrastructure failures incorrectly attribute DevOps testing failures to product failures, resulting in unnecessary, wasteful product failure diagnostic activities.  We do not want to absorb unnecessary time, resources and funding on false negative test results. Efficiency is key.

Increased Competition
Increased Competition occurs when the competitor realizes a more efficient DevOps testing capability and out performs a competitor.  Those who perform DevOps testing best are likely to lead the pack.

Even if you do not buy into the idea that we need to learn how to do more with less, this reminds us that we can always do better with what we have.  These are some very real challenges that create risk.  Pick one that is relevant to you and your organization. Start there in an iterative effort to succeed with DevOps Test Engineering for results.

Educate and Inspire:  DevOps Test Engineering



Comments

Popular posts from this blog

What is the difference between Process Owner, Process Manager and Process Practitioner?

I was recently asked to clarify the roles of the Process Owner, Process Manager and Process Practitioner and wanted to share this with you.

Roles and Responsibilities:
Process Owner – this individual is “Accountable” for the process. They are the goto person and represent this process across the entire organization. They will ensure that the process is clearly defined, designed and documented. They will ensure that the process has a set of Policies for governance.Example: The process owner for Incident management will ensure that all of the activities to Identify, Record, Categorize, Investigate, … all the way to closing the incident are defined and documented with clearly defined roles, responsibilities, handoffs, and deliverables. An example of a policy in could be… “All Incidents must be logged”. Policies are rules that govern the process. Process Owner ensures that all Process activities, (what to do), Procedures (details on how to perform the activity) and the policies (r…

How Does ITIL Help in the Management of the SDLC?

I was recently asked how ITIL helps in the management of the SDLC (Software Development Lifecycle).  Simply put... SDLC is a Lifecycle approach to produce the software or the "product".  ITIL is a Lifecycle approach that focuses on the "service".
I’ll start by reviewing both SDLC and ITIL Lifecycles and then summarize:
SDLC  -  The intent of an SDLC process is to help produce a product that is cost-efficient, effective and of high quality. Once an application is created, the SDLC maps the proper deployment of the software into the live environment. The SDLC methodology usually contains the following stages: Analysis (requirements and design), construction, testing, release and maintenance.  The focus here is on the Software.  Most organizations will use an Agile or Waterfall approach to implement the software through the Software Development Lifecycle.
ITIL  -  is a best practice for IT service management (ITSM) that focuses on aligning IT services with the needs …

ITIL 4 – Mapping the Customer Journey

All service providers are in the business of customer and user experience. It is not enough to compete on products and services, how services are delivered is as important as what is delivered.

The customer journey is the complete end-to-end experience customers have with one or more service providers and/or their products through the touchpoints and service interactions with those providers. In order to focus on the outcomes and on the customer/user experience, service providers are seeking to master the art of mapping their customer journey. Doing so allows them to maximize stakeholder value through co-creation of value throughout the entire value chain.

The customer journey begins by understanding the overall macro-level of steps or groups of activities that generate the need for interaction between the customer and the service provider. These activities begin at “Explore” and end with “Realize” where the value is actually being consumed by the end-users.
The Band of Visibility