We can never guess user behaviour. Just because he should press that nice green button, doesn't mean he will. We can develop the features and protect the application to avoid exceptions, errors, and handle all that but we need QA to work with us, make sure that if the user's cat jump in the keyboard, and if option B is selected and he press the green button everything still works fine
Developing software solutions for too many years. The majority of my time has been either Managing Software Development efforts or as a Software Quality Engineer.
So if I could rashly summarize what you're saying. A developer should build their software to handle all of the potential logical pathways. QA would also validate those logical pathways manually & hopefully automated as well. But then a QA should also test the illogical potentials or unpredictable interactions to make sure the logical gates function accordingly (aka the Cat on keyboard test).
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
We can never guess user behaviour. Just because he should press that nice green button, doesn't mean he will. We can develop the features and protect the application to avoid exceptions, errors, and handle all that but we need QA to work with us, make sure that if the user's cat jump in the keyboard, and if option B is selected and he press the green button everything still works fine
oh man . . . you brought out the cat test 😂
So if I could rashly summarize what you're saying. A developer should build their software to handle all of the potential logical pathways. QA would also validate those logical pathways manually & hopefully automated as well. But then a QA should also test the illogical potentials or unpredictable interactions to make sure the logical gates function accordingly (aka the Cat on keyboard test).