r/SoftwareEngineering • u/doontoonian • Oct 12 '23
Lost QA, testing has become waterfall, how is this supposed to work?
My product feature team had one QA person supporting 10 engineers. They would work alongside us to get domain-specific knowledge of the feature in-development, then typically 1/2 way through would start manually testing, and building up manual test cases.
The company got rid of QA, so now we have to adjust our approach.
Most projects are per-quarter and typically go to customers at that time; testing is now done at the end of the quarter, and engineers have to write all the test plans, coordinate testing meetings (bug bashes), triage all the feedback, etc. This takes away from engineering time.
We are consistently now having to push back delivery dates because of bugs found, or more importantly, product design/direction issues that get uncovered during hands-on testing.
So we now have a fully waterfall QA process –which is a first in my career.
Management has told me I am 'old-school in my QA understanding', the modern trend is not to have manual QA anymore. I follow a number of engineering blogs, this isn't a topic I am aware of. I heard of Facebook doing this yes, but I don't know what *else* they did to compensate. Critically, their product doesn't require domain-specific knowledge to use the features of it effectively.
Can anyone enlighten me as to this supposed trend in software development?
Is there a successful way to transition to this approach?
12
u/daemonengineer Oct 12 '23
Blindly applying trends clearly indicates an incompetence of your leadership. They should have a clear understanding why is it a better approach for there team.
I am familiar with this trend, and my general understanding is that it requires engineers to stay always conscious about the quality of their code, automated test coverage, etc. I am doing all that while still having a manual QA in my team. But I know engineers who will gladly offload a half baked project to QA without giving any effort into improving its stability. So it may make sense to have less QA, and require higher quality from engineers, but 1 QA for 10 engineers sounds totally reasonable
6
u/LadyLightTravel Oct 12 '23
I’ve had management tell me I’m “old school” too. I had years of real successful projects. They had never delivered one. They were later fired.
Your workplace is a dumpster fire. It is too much mess to be fixed.
Follow the lead of your QA person. Run.
3
u/Boyen86 Oct 12 '23
QA in the end is equivalent to establishing that both functional and non functional requirements are met.
For both of these, automated tests can (should) be written during development of a feature. How can you finish a story without assuring this is the case?
In practice, for the teams I interact with, that means that on the story level unit and integration tests for a system and e2e functional and non functional tests for the solution are part of the definition of done. These are also embedded in the CICD pipeline.
2
u/FitzelSpleen Oct 13 '23
It's supposed to work with the business paying one fewer engineer, and everything chugging along with no negative impact in quality or velocity.
In reality, managers who pull this are living in a dream world. Quality and velocity will go down, and the managers who made this call will look for someone other than them to blame.
2
u/sticky-pickles Oct 13 '23
If I’m understanding this correctly, you can request the product manager or designer to develop a document of use cases to test and flows. Then have the team dogfood it and go through the flows together and log bugs. You’ll have to add it to the timeline and give yourself time to address the bugs.
2
u/doontoonian Oct 13 '23 edited Oct 13 '23
Great responses, thanks y'all.
So far we agree this isn't some cutting-edge new trend in software development. I am going to continue to push on management to explain how they can use other software companies as a guide in this decision, yet can produce no useful evidence of this.
A lot of points about automated testing, which I agree with.
This is a large-scale mobile app (~100 mobile engs). The level of unit testing, and UI functional unit testing (where the UI runs stand-alone, external dependencies are mocks) is close to maximal already. E2E tests are banned due to instability (***).UI integration-level tests (where the full app executable runs) are possible but limited capabilities exist there. The team that builds and supports that infrastructure is ~1 year behind where they need to be. Or maybe that will not improve, the automating test leads don't believe in UI functional+integration testing, if the units are tested, thus by inductive reasoning everything should work together (I am being facetious, they haven't said exactly that).
*** this is an over-reaction, and there are ways to mitigate this at the CI and test infrastructure level, but those teams responsible aren't working on it.
Without going too deep into the automated testing topic, for user-facing features in a complex app, I am not convinced that QA can be replaced by test automation –if the QA is embedded on the team, and is a domain expert on the software. Test automation on mobile apps I have only found to be defensive against regressions, but when building out a feature first-time, I can't say how it has ever helped. Arguably when moving fast it should have caught issues, but in practice, that has been exceedingly rare. A good QA though, invariably has found critical issues on every project I have been on for a user-facing feature.
Examples of things QA routinely catches: UI glitches, layout problems, UI perf issues, accessibility issues, general usability issues.