DEV Community

Cover image for 5 ways to skip QA approval forever!

5 ways to skip QA approval forever!

Dhruv Agarwal on July 04, 2024

3 days of planning, 5 days of execution and then the whole work gets stuck for weeks on QA. On the flip side if it gets picked up, it results in ...
Collapse
 
californiak15 profile image
DEVing_Testing

devs should always own the code and never throw crap over the wall to be tested.

that said there is no left or right approach. dev needs to be responsible for coding and unit testing and automation. QA is there to be sure all requirements are met as a extra set of eyes 👀 for the development and PM.. keep everyone honest.

Collapse
 
dhruvagarwal profile image
Dhruv Agarwal

That is spot on! All efficiency approaches are bespoke to the context ☺️

Collapse
 
arifchauhan profile image
Arif Chauhan

Shift left is fine and approach has been in use for some time. QA is never a bottleneck if the code quality you build is good. And, if your code quality is good and QA taking more time to validate then you need to review the efficiency and skills of testers, and fix the team accordingly with right testing skills.

Collapse
 
dhruvagarwal profile image
Dhruv Agarwal

You're right! All process improvements are bespoke ☺️

Collapse
 
craig99 profile image
Craig • Edited

This is the age old issue....Dev takes their time to create, QA is always the bottleneck. Solution, create an accurate project plan, follow it and adjust it when situations happen when something takes longer than expected. Keep management informed. And, when deadlines have to be met, the team puts in the extra effort and in some instances you drop features to make deadlines. You need QA....recall recent issues last week. That was a failure in the development, QA and release process. Final thought, the most successful projects are, when DEV and QA are working together. The writer of this article sounds like they work in a Waterfall development environment. They may want to try Agile development . It's a team approach to development.

Collapse
 
jayantbh profile image
Jayant Bhawal

Shifting left is one of those things that feels so obvious once someone says it to you. 👏

Collapse
 
samadyarkhan profile image
Samad Yar Khan

Great post! The struggle with QA bottlenecks is real. Loved the idea of shifting QA left and having devs own their code. Collaborating better and looking back for improvements can make a huge difference. Thanks for sharing these tips!

Collapse
 
jayantbh profile image
Jayant Bhawal

Oh yeah. I've seen an impact of this pretty instantly at one of my previous jobs.

Collapse
 
shivamchhuneja profile image
Shivam Chhuneja

the genie is out of the bottle!

Collapse
 
ahmed_saif_b41028964a6d30 profile image
Ahmed Saif • Edited

Wonder post , can we shift the ITIL to UP or DOWN as well as kind of shifting coz they need to be automated Lol... Waiting to your article about it

Collapse
 
dhruvagarwal profile image
Dhruv Agarwal

Haha!

Collapse
 
dhruvagarwal profile image
Dhruv Agarwal

Although automation comes slightly later when the use cases are solidified. For the fresh features, it's generally and rightfully on a lag

Collapse
 
motss profile image
Rong Sen Ng

Devs can be good at writing test plans. QA engineers who do not test anything should not even exist. Just ditch them.

Collapse
 
dhruvagarwal profile image
Dhruv Agarwal

💯

Collapse
 
martinbaun profile image
Martin Baun

Well done! QA is something that can start from the design/requirement state

Collapse
 
pauluz profile image
Paul Canning

What if it's the opposite and there isn't enough QA resource?

Collapse
 
dhruvagarwal profile image
Dhruv Agarwal

Then someone needs to prepare the test plan. The devs then ☺️

Collapse
 
Sloan, the sloth mascot
Comment deleted
Collapse
 
dhruvagarwal profile image
Dhruv Agarwal

The ones I have used or as a concept?

Collapse
 
david_delrio_2b4674b71db profile image
David del Rio

"Manual QA"

There's your problem. Get SDETs.