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 m

Diego Pacheco Tech blog

submited by

Style Pass

2021-06-09 06:00:17

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.

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.