Skip to main content

What does it mean to “shift testing left”?

What does it mean to “shift testing left”?

I used to think shifting left meant starting all these testing activities earlier in the process, but I realise it is more than that: it means doing different things. Shifting left on testing means thinking about architecture and design differently, considering different stakeholders early and continually. Which in turn means shifting left on security, accessibility, and all the other dimensions of quality that we should care about. So shifting left on testing motivates all kinds of assurance activities, which can stop us over-investing in a solution that was never going to work. It is like TDD on steroids.

As an unintended consequence, we can remove much of the traditional work that testers would have to do downstream when they only have late sight of the product. Again, we aren’t doing that work earlier, we are setting ourselves up to never need it at all!

Comments

Popular posts from this blog

On working remote

The last company I worked for, did have an office space, but the code was all on Github, infra on AWS, we tracked issues over Asana and more or less each person had at least one project they could call "their own" (I had a bunch of them ;-)). This worked pretty well. And it gave me a feeling that working remote would not be very different from this. So when we started working on our own startup, we started with working from our homes. It looked great at first. I could now spend more time with Mom and could work at leisure. However, it is not as good as it looks like. At times it just feels you are busy without business, that you had been working, yet didn't achieve much. If you are evaluating working from home and are not sure of how to start, or you already do (then please review and add your views in comments) and feel like you were better off in the office, do read on. Remote work is great. But a physical office is better. So if you can, find yourself a co-working s

Capture and compare stdout in python unit tests

A recent fan of TDD, I set out to write tests for whatever comes my way. And there was one feature where the code would print messages to the console. Now - I had tests written for the API but I could not get my head around ways to capture these messages in my unittests. After some searching and some stroke of genius, here's how I accomplished capturing stdout.

AIT a.k.a Army institute of Technology

Been quite a while that I wrote anything. But I am glad, that I am back. Now that I am done with my submissions for my third year second semester (and that too right on time. Bang!), and 10 days right before the practicals start banging my head off, I am feeling a certain urge of writing about this place. AIT. Army Institute of Technology, Pune. But how could I end up writing a post on AIT . I should instead be doing something else . Anything …sleeping , rope-skipping, play gilli danda , dancing or doing anything more worthwhile. But NO! My idiotic , uncontrollable , insensible , psychotic and involuntary mind could think of doing nothing else when I was getting the urge to write this senseless post. But as I am a man of my words [huh ? What words ? Half the time I don’t even know what I speak] . MAN AM GOING CRAZY THESE DAYS . I blame this summer heat for turning me crazy with the utter joy of timely submissions, So I am going to write something on AIT. Mighty mighty AIT they s