Shift-left testing approach explained

According to ISTQB there is 7 testing principles, one of them is the principle of Early Testing. What does it mean? Again, according to ISQTB, it means that testing activities should start as early as possible, before working piece of software is available.

Why am I wrote about this principle? Because the subject of this article, shift-left testing, eventually is the same as early testing principle and it is very important and crucial approach in Quality assurance. Let's discuss why it is.

As some of you might think or assume that testing can be performed once tester has a piece of software product that he can test. In some projects, or methodologies it's true, but in Agile projects it's no longer valid due to the fact that testing is not limited to the testing of a already built software product, but a lot of other work related products can be tested, like requirements, manuals and documentation, wireframes etc (Static testing). That means that testing activities, not just testing, but reviews, walkthroughs and inspections can be applied to a set of related work items which are available long before first products build will be available. 

In this way we can apply QA activities related to test planning, we can review our requirements, risks and based on them - create Test Strategy, define test approaches, think about testing processes, improvements, etc. Depending on a project and it's deliverables we can test early and more often, results of this testing can serve as inputs for defining next QA activities or change existing, if or when required, so test monitoring can be based on more live data and test results.

With sift-left testing approach we can build more effective QA processes as they will be based on relevant and actual data so, our QA activities can be Proactive rather than Reactive - we can prevent defects from happening and by this - improve overall SDLC processes. And this is one of the most important aspect of Quality Assurance, you are building not only a process, but a product as well.

Also, performing all these activities is almost impossible without close team collaboration, so you, as a QA, other dev team members and stakeholders will be more involved in building a quality product by continuously collaborating, communicating and resolving any issue or risk that could arise.

Of course, test automation will be good addition to your testing processes, so you will have more test results and inputs to work on related QA activities and improve them.

These are not the only pros or aspects that shift-left testing provides as it all, as usual, depends on a project, it's needs and agreed level of quality that has to be delivered, but these are essentials that will help you build effective QA processes and deliver right product

Reasons not to pass ISTQB certification

 In my previous article I presented my top 5 reasons to pass the ISTQB exam. In this article I would like to write my thoughts about reasons not to pass the exam.

So what were the reasons to pass the exam - you'd expand your testing theory knowledge, you will use "the same language" in your team, you will structure your knowledge and you would gain that knowledge even in case you'd just read the exam papers and last - you'd be allowed for the next, advanced ISTQB exams, like Test Managers or Test Analyst.

Ok, but these pros mainly applicable for junior/trainee testers and what about senior QAs? In case you have a lot of knowledge and was working on a multiple of projects as a QA or tester than you, should, already got most of the knowledge that ISTQB Foundation Level can provide you. Then, you will not, probably, expand your knowledge and in most cases you'd know all the terms and definitions that ISTQB FL provides. Sure, last item - allowance to pass advanced level exams could be relevant to you only in case you are about to pass it or want to go to QA management role, but in case you are not interested in obtaining this advanced level certificate, then you don't need it at all and it's no more an advantage.

In any case, if you a true Senior QA, know the difference between QA, QC and testing, apply QA practices and provides quality assurance then, of course, you already know more than ISTQB FL can provide. 

As you can see in this short article there is two category of quality specialists - experienced and those who need to became one. Last one would benefit from passing ISTQB, so in case you're in that category, I'd recommend to think about passing the exam or at least just read the papers.