Skip to main content

DevOps Testing vs Traditional Testing

Appropriate testing is THE differentiator for high performing IT organizations.

What is the Same?

Tests need to be classified according to the attributes of the system or the product that is to be tested.  Test types include:

Unit Test - This is a method that validates that the code statements satisfy assertions.

Static Code Analysis – Testing that checks source code logic and consistency.  Static testing evaluates code against development standards and guidelines. Code execution is not required.

Dynamic Analysis – This type of testing might also be referred to as “Functional Testing”. In this type of test, code is executed against positive and negative functional scenarios.

Code Coverage – Measures the percentage of relevant lines of code tested.

Integration Test – This form of testing will help to determine if code changes work after a code merge.   Integration testing may also be referred to as smoke test, sanity test or build test.

Compatibility Test –  This is used for testing feature interactions.

Conformance Test – This is where we test to ensure the code/product conforms to standards.

Usability – Tests to evaluate the user experience.

Application Testing – Tests to verify the application functions.

Regression Testing – This is required to ensure that changes made did not break something else.

The list goes on to include compliance, security, performance, acceptance testing and more.  Not all test types apply to all products or organizations and the names may be different.

What is Different?

Testing must happen much earlier in the development pipeline and must also take into account all aspects of privacy, security and monitoring. 

Tests are Automated apart from some nonlinear test types requiring human intervention.  Non-automated testing is limited.

Test Environment and Test Data provisioning self-services increase test reliability.

DevOps Tests including pre-flight tests, are performed in an environment that is equivalent to the production environment of customer deployments.  This limits the risk of false positives.

New Thinking for when and how to accelerate change, become a ticketless IT organization and how to provision for skillsets and structures that shatter silos will continue to be integrated into Continuous Testing and the DevOps Pipeline.


Comments

Popular posts from this blog

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 than 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

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 th