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

Four Service Characteristics

Recently I came across several articles by researchers and experts that laid out definitions and characteristics of services. ITIL provides us with a definition that can help drive the creation of value-laden services: A means of delivering value to customers by facilitating outcomes customers want to achieve without the ownership of specific costs and risks. An area that ITIL is not so clear is in terms of service characteristics. Several researchers and experts put forth that services have four basic characteristics (IHIP): Intangibility—Services are the results of actions not things. They have no physical presence and represent a logical set of elements. One way to think of service is “work done for others.” Heterogeneity—Also known as “variability”; services are unique items because of the mechanisms used to deliver services, which is people. Because the people element adds variability, the service is variable. This holds true, especially for the value proposition—not eve...

What Is A Service Offering?

The ITIL 4 Best Practice Guidance defines a “Service Offering” as a description of one or more services designed to address the needs of a target customer or group. As a service provider, we can’t stop there! We must know what the contracts of our service offering are and be able to put them into context as required by the customer. Let’s explore the three elements that comprise a Service Offering. A “Service Offering” may include: Goods, Access to Resources, and Service Actions 1. Goods – When we think of “Goods” within a service offering these are the items where ownership is transferred to the consumer and the consumer takes responsibility for the future use of these goods. Example of goods that are being provided in the offering – If this is a hotel service then toiletries or chocolates are yours to take with you. You the consumer own these and they are yours to take with you. ...

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

This article was originally published in 2015. With the Introduction of ITIL 4, some of this best practice has changed. See ITIL 4 and the Evolving Role of Roles . Updated Definitions in ITIL 4: Process Owner: In ITIL 4, the concept of 'processes' has expanded into broader 'practices.' Consequently, the Process Owner is now often referred to as the 'Practice Owner.' This individual is accountable for the overall design, performance, integration, and improvement of a specific practice within the organization. They ensure that the practice achieves its intended outcomes and aligns with the organization's objectives. Process Manager: Now commonly known as the 'Practice Manager' in ITIL 4, this role is responsible for the day-to-day management of the practice. The Practice Manager ensures that activities are carried out as intended, manages resources assigned to the practice, and oversees the practitioners performing the work. Process Practit...

Search