My 2 Cents on "On the Diverse And Fantastical Shapes of Testing"

I want to share my cents about the post: "On the Diverse And Fantastical Shapes of Testing". First of all, I believe this is a very interesting subject and yet still see very few engineers talking about it. People mostly take tests for granted. Secondly, I would like to acknowledge the parts I agree with on this post mainly around the concept of Sociable and Solitary Unit Tests are quite useful and show be widespread. Also with the need for teams to have reliable, fast, Bounded(Isolated) and not Flacky on Justin tweet. Now that I acknowledge that, let me elaborate on what I think we are missing and why IMHO the pyramid is dated and we need a mentality shift. I have 4 points I want to elaborate on and give more context.

I expressed these ideas before on this blog posts and if you more details and more context:

* http://diego-pacheco.blogspot.com/2021/02/testing-in-production.html

* http://diego-pacheco.blogspot.com/2020/08/hardening-prodution.html

* http://diego-pacheco.blogspot.com/2020/03/pipelines-from-cicd-to-self-operating.html

* http://diego-pacheco.blogspot.com/2020/02/going-faster-with-testing.html

TL;DR; It's about having a bigger test diversity and shifting our mindset to hardening production rather than trying to predict all possible failure modes. 

#1 - Engineering Evolution - frontend, mobile, data, ops, etc

Test Pyramid was great but also dated. Today we have other fields of software engineering much more evolved them before such as Frontend Engineering(look React, Vue, Angular) look micro frontends and module federation, Mobile with IoS, Flutter, Dart, React-Native, look Server Driven UI for instance, Big Data or just Data with Streaming(Spark, Flink, Kafka Stream), Machine Learning and let's not forget about Ops(or like some folks call it DevOps or SRE) with plenty of infra and automation work - such as Terraform. 

Engineering had evolved in so many specialized fields than the generic full stack developer or classical and only backend work tends to fade in big companies. Things are much more specialized now and software is much more distributed thanks to cloud computing, edge computing, blockchain, IoT, and the trend if to have more distribution not less. 

As we have more distribution(look Microservices and Serverless also) - Unit Tests and Integration tests cannot be the only form of testing and we also need to acknowledge that because of the complexity of the systems we have we need more them testing. 

#2 - Limits of pre-production testing - Triggering failure modes and recovery from them

Pre-Production testing has limits. The classical test pyramid aimed at pre-production testing. Pre-production testing still will exist forever probably but it has limits. As we have more and more distribution and specialized software in different places(#1) we can't predict all failure modes. It is very hard to replicate and maintain pre-prod envs. So how we reproduce important failure modes? With classical test pyramid approach will be hard because we need more tests. We need a modern approach with Chaos Engineering, Observability, Testing Diversity, and more. 

#3 - Observability, Chaos Engineering, and understanding

Observability is about understanding and having better systems. How much does the Test pyramid talk about that? Chaos Engineering is about recovering from failure and testing your infra and software to make sure they are anti-fragile, you can't do that with unit and integration tests. 

We need a wider spectrum considering not only pre-prod but also prod(pre and post-deploy). Testing needs to be blend with Observability and Chaos Engineering. In the end, Observability is not that different from testing but how it works is pretty different. In the end, what we need is a better understanding of production systems and hability to recover from failure and that's very different from the classical pyramid mindset. 

#4 - Waste, Mindset(Hardening production), and Diversity

All Forms of testing have WASTE. Unit Tests can suffer a lot from Mocks and that could be a smell. Integration tests can be expensive, flaky, and also full of waste. A % or specific test coverage means nothing in this sense since you can't give this number to different services and different pieces of software considering frontend, backend, data, and ops. it's also very hard to measure and therefore we have WASTE there.

What we need is a mindset shift where we need to harden production and always make production better.  IF the code is not in prod is a waste. Lean is all about production and reducing cycles and deploy often to production. It's getting harder and harder to simulate failure in pre-production. In the end is all about diversity, having more forms of testing with a wider spectrum, not a pyramid. 

Cheers,

Diego Pacheco

Popular posts from this blog

C Unit Testing with Check

Image
When I start on IT, several years ago(+15), C was the first language that I learned. But was not the first language I mastered and deployed in production which was...surprisingly Visual Basic 6.0. However, when I learned C or any language back on that old and arcane time noddy was into testing. However now is impossible to work professionally in any language without tests. C is a low-level language but still kicks ass and has several interesting libs/frameworks. People use to fear C a lot because of lack of syntactical sugar but once you get used to it is not that hard at all. Today I want to show how you can do Unit Testing with C. I will not show how to do Unit Testing with C++ but with C ANSI actually. We will be using Check a unit test lib for C ANSI.
read more »

Having fun with Zig Language

Image
Zig is a general-purpose language created in 2016 by Andrew Kelly .  Zig aims to fix the issues C language has while being pragmatic and simple at the same time. Zig really shines as being simple by not having any hidden control flows, not having hidden memory allocations, no pre-processors, and no macros. Basically, it's one language and one language only. Since pre-processors and macros can get really complex and become their own universe. Sure it's not the Zig Philosophy.  Zig Compiler(Zig cc) also is a C compiler, and the interoperability from C to Zig is very good. Clearly, we can see influence from other languages like Go and Rust; however, Zig is pretty unique and different from Go and Rust.  Zig is fast. Zig is perfect for system programming. I bet we will see a lot of solutions being built in Zig. As a languages aficionado, I like to learn at least one language per year and sometimes more; Zig was my 2021 pick, did not regret it. Even if you dont use all languages in p
Keep reading

HMAC in Java

Image
In 2018 AWS CTO(Vogels) said : "Security is everyone's job". For the last 2 years, there was so many famous and big data leaks and breaks that made that statement be very true more than ever. Security often could mean worst performance and worst user experience so in order to get it right you really need to think about the designs before jumping into to code and consider performance and user experience has main requirements.  I was thinking about writing about how to do HMAC in Java for a while and recently Redis 6.0.0 come out and to my surprise, there was a refactoring on the password part in order to use HMAC.  Security easily could scare engineers often because it is not something well spread yet but I believe this will change soon. It does not matter if you have to deal with PII Data or not, security is super relevant because everybody is running their workloads at the cloud or with IoT and Edge devices which means more distribution, more code, more points of fail
read more »