Interview with Head of QA at worldwide media resource | Software Testing Company a1qa

At present, companies with software products introduce QA services to the agile lifecycle. From your point of view, what is the main mistake that organizations make while adopting QA practices?

To the present, the software industry is changing at a breakneck pace, so delivering a flawless product is becoming more crucial. This is why companies understand that introducing QA practices to their business strategies is not the wish — it is the need.

Your opinion: why hasn’t test automation replaced manual testing for 100%?

I’m not sure that it should. It goes without saying that there are several cases when manual testing simply cannot be replaced by automation (while conducting UX usability tests, UI testing, and many more). But I want to highlight another crucial juncture.

I do not actually separate manual testers from test automation engineers. Let me explain why.

If you are specializing in performance or test automation, that’s your specialism, but you are still an engineer who understands the code. This fact is also about the team members and their willingness to grow professionally, develop their skills, and become more rounded in their roles. A squad should contribute to a goal, and there should not be silos in the team, which mean that we cannot release a product, as we are dependent on a particular skillset.

Who is the last one to be responsible for software quality in the company? Why?

Each and every member of the project team or squad is in charge of quality.

All team players have to be on the same page and care about the one paramount thing — delivering a top-notch product to the market.

How has Agile methodology changed the attitude of IT representatives to the QA process?

Agile development practices have provoked to shift testing left and significantly changed the world of QA. Some time ago, software products weren’t even shipped to the end users until the business need was validated for years.

What is behind the term “shift-left testing”? Emphasize the benefits it can bring to the product and business in general as well as its main challenges.

Please name a few tips on how companies can leverage from CT to enhance the quality and speed of delivery.

By adopting test automation at each development lifecycle stage, CT can easily define the business risks concerning each potential release version. Due to that, bugs are fixed at the right time.

What similarities and differences can you name between the approaches of CT and shift-left testing?

To my mind, these concepts share more commonalities than differences. Both of them are considered to be vital approaches in the world of QA.

How can the company bring these concepts together to test continuously and shift the testing processes left?

To combine them effectively, one should first realize why they should be merged and then identify the main goal. Try to coach engineers on quality processes at code level, put the engineer back into QA engineer, and get the whole team to contribute to the automation product.

--

--

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
a1qa

a1qa

Software Testing & Quality Assurance Company. #QA #testing #mobile #security #performance #consulting #automation #telecom #ecommerce #banking #Agile #DevOps