The feature crashed when the user submitted a form. What did you do?, relaxed, investigated, decorated, The developer asked you what exactly happened. What did you do?, clarified the behaviour, uninstalled the app, ignored the message, You needed more data to understand the issue. What did you do?, reviewed Netflix, reviewed lunch options, reviewed the logs, The bug turned out to be critical and urgent. What did you do?, escalated it, hid it, printed it, After the developer delivered a fix, what did you do?, confused the fix, confirmed the fix, compared the fix to a sandwich, You needed to add a new issue to Jira. What did you do?, logged your goals, logged out, logged the bug, You and another QA worked on the same module. What did you do?, collaborated, collided, complained, You weren’t sure what the expected behaviour was. What did you do?, clarified requirements, claimed the universe was wrong, closed the browser and cried, You needed to check if the fix worked after redeployment. What did you do?, redecorated the environment, rejected the build, verified the fix, A ticket had too little information. What did you do?, requested additional details, requested pizza, rested, The same bug reappeared in a new build. What did you do?, retired, retested the whole module, retold someone a joke, You found duplicated behaviour in two different features. What did you do?, identified the pattern, ignored it, iced the problem, You weren’t able to proceed because an environment was down. What did you do?, escaped to Mexico, escalated the blocker, estimated the API, You needed to make sure the issue couldn’t be reproduced again. What did you do?, reimagined it, removed the internet, retested with edge cases, The PM asked for a summary of your work yesterday. What did you do?, prepared a status update, prepared a sandwich, pretended you didn’t hear.

QA Process and Problem Solving

由
列印
嵌入

排行榜

視覺風格

選項

AI 強化版：此活動包含 AI 生成的內容。了解更多。

切換範本

)
恢復自動保存: ?