What Do You Dislike Most About Quality Assurance? (2024)

LaToya F.

Senior Customer Service Representative at Dialog Direct

8y

I have found that quantity has begun to outweigh the quality where my experience is concerned. It has seemingly been more about the number of evaluations or grades rather than the substance that is coming from the analysis itself.

Al Swearingin

Mfg. Quality Assurance Engineer for Starting USA Corporation. A division of Briggs + Stratton corporation RETIRED

8y

This is right on. It seems that time lines do not allow for the proper QA qualifications. Most of the time production moves forward even if PPAP submissions have not been completed. pFMEAs lag way behind or are an after the fact idea. Unforeseen problems which could have been avoided if the proper time had been allowed for review. Sometimes operator instructions are not posted until well after the production has started for a new project. It seems although some companies have a QA department and follow ISO procedures its still seen only as a customer or market requirement rather than a functional tool.

Khubaib Rehman

Fintech Product Manager, PCI DSS 4.0 Consultant | I help organizations to build better products. | Product Management | User Experience | SCRUM | JIRA | Leadership | Communication | Strategy |

8y

Indeed! Ruslan Desyatnikov most of the cases matches your article. But it is also improving day by day as QA is going towards Automation. More priority is being given to QA nowadays.

Michael Buening

Senior Manager with the BDO Digital Enterprise Business Applications Division

8y

The root of "the problem" is improper positioning of testing (typically misnamed QA) in the business of software/system development. The decision to release a project or product to the wild is always the responsibility of the business executive sponsoring the work. There should be no group or person or role in IT who has the responsibility to make a release decision. Once the business sponsor understands the release decision is hers to make, the relationship with testing (or more broadly QA when applicable) can be far more constructive. The question becomes "how much information do you need to make a release decision?" Testing's job is to deliver that information the most efficient way possible. QA's job is to provide the best environment possible, end-to-end, to generate good results including information provided by testing.If you have this kind of a relationship, arguments about the level of investment in testing decline. They never go away - who doesn't want to spend less on insurance? It also frees the testing team, from junior tester to test manager, from working under the oppression of unrealistic and typically unstated objectives.

Valentin Shakhov

Java Backend Engineer

8y

When planning a new product, one should have a system architect in his team with robust performance testing experience. Bad initial architectural design is what usually spoils software. That is to say that a good development team must be managed by an experienced QA engineer, what's unfortunately rarely implemented.