"He had little testing experience but a lot of development experience, so there was a lot to learn. First, he had to understand the pitfalls and challenges of testing, like what needs to be tested when, how, and why. Another challenge Bischoff faced was understanding test levels: I initially tried to test a lot through UI automation, not realizing that many checks would be faster and more stable as unit or integration tests on the API or database layers."
"Learning when not to automate was crucial, like for one-time migration scripts, Bischoff said. It was difficult at first to realise that you can't just jump into automation, but that it has to be done carefully and with the involvement of all stakeholders, he added. Bischoff mentioned that his perspective on developers and testers changed along the way. When he first came into contact with software testers in his career, he saw them as a "necessary evil"."
A professional moved from software development into test automation and faced substantial learning needs due to limited testing experience. The professional learned to identify testing pitfalls and to choose appropriate test levels, recognizing that many checks are faster and more stable as unit or integration tests rather than UI automation. The professional learned when not to automate, avoiding one-time automation like migration scripts and involving stakeholders before automating. Early development attitudes sometimes treated QA as a hindrance and even ignored known bugs until QA found them. Working within a core QA team led to a renewed appreciation for QA engineers and collaboration.
Read at InfoQ
Unable to calculate read time
Collection
[
|
...
]