Test-Driven Development is Fundamentally Wrong By @Cheopys The second problem here is that TDD presumes that developers should write their own tests. This is supremely ridiculous. I’ve seen this many, many times; the project appears solid to me, I can't break it, but someone else can break it in less than a minute. Why? Because the same blind spots that I had in design will appear in my tests. Read More Why AI & ML Will Shake Software Testing up in 2019 By @oleksii_kh The problem of ignored bugs is very diverse and bears extremely negative consequences. We all know how traditional testing works at this moment. If you do not devote enough attention to data management, then, as a result, you will receive a whole bunch of ignored bugs. But that’s not all, because as a result, you get an unsatisfied customer and spoil the brand’s reputation. Read More Three Patterns for an Effective Cloud Native Development Workflow Obviously services should be designed to be as cohesive and loosely coupled as possible, which means that the can be developed in isolation. However, when this is not practical, or an engineer wants to drive a more production-like test, techniques like service virtualisation and consumer-driven contracts can be useful patterns. Read More mabl Uses AI to Bring Software Testing into the DevOps Era By @David “Drive” is one of our core values as a company, and I think that comes across in the pace. We’ve been working on the product for about 10 months now, it’s being used extensively by many companies, and we’re getting great feedback on the alpha. Read More GCP and the Future of Software Testing By @mabl Watch Dan Belcher and Joe Lust present the 4 principles of the Intelligent Testing, and how GCP has allowed us to traverse this era through the development of mabl. Read More |