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

The Four Ps of Service Design - It’s not all about Technology

People ask me why I think that many designs and projects often fail. The most common answer is from a lack of preparation and management. Many IT organizations just think about the technology (product) implementation and fail to understand the risks of not planning for the effective and efficient use of the four Ps: People, Process, Products (services, technology and tools) and Partners (suppliers, manufacturers and vendors). A holistic approach should be adopted for all Service Design aspects and areas to ensure consistency and integration within all activities and processes across the entire IT environment, providing end to end business-related functionality and quality. (SD 2.4.2) People: Have to have proper skills and possess the necessary competencies in order to get involved in the provision of IT services. The right skills, the right knowledge, the right level of experience must be kept current and aligned to the business needs. Products: These are the technology managem

What Is A Service Offering?

The ITIL4 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 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. Note: Goods may not always be provided for every Service Offe

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

Search