𝗧𝗵𝗲 𝗧𝗲𝘀𝘁𝗲𝗿 𝗪𝗶𝘁𝗵 𝟭𝟬 𝗖𝗲𝗿𝘁𝘀 𝗪𝗵𝗼 𝗖𝗼𝘂𝗹𝗱𝗻'𝘁 𝗙𝗶𝗻𝗱 𝗮 𝗕𝘂𝗴
You have every certification. ISTQB, ScrumMaster, Cloud, and Security. Your resume is a wall of acronyms.
But you cannot write a single test that finds a real bug.
I interviewed a candidate last quarter. They spoke only in theory. They mentioned the V-model and shift-left. When I asked them to show me one test they wrote that caught a bug, they stayed silent.
They had never written a test that broke something. They only wrote tests that passed.
Certifications test your memory. Bugs test your thinking.
Certifications provide vocabulary and structure. They help you pass recruiter screens. They do not teach you how to find defects.
Exam questions follow a syllabus. Real applications do not. A login form does not have a syllabus. It has weird edge cases, like server clocks being off by four minutes or specific timing issues.
The certified tester follows a checklist. They write tests from requirements and mark them as pass or fail.
The bug hunter treats testing like an investigation. They start with a hypothesis. They try to prove the application wrong.
Look at the difference in mindset.
A standard test checks the happy path:
- Go to products.
- Add to cart.
- Enter valid card details.
- Expect order confirmation.
This test proves the feature works when everything is perfect. It will never find a bug.
A bug hunter test is suspicious:
- Enter a card number with a typo.
- Expect an error message.
- Check that the order confirmation did not appear anyway.
The second test assumes the application will fail. It asks: "Where does this break?"
Many testers have a gap in experience, not a gap in their resume. You have seen tests fail because of bad data or down environments. You have not seen tests fail because you found a flaw in the logic.
Stop studying for new exams. Close the gap by writing tests designed to fail.
Try this exercise: Pick one feature. Spend one hour trying to break it.
For a search feature:
- Test gibberish queries.
- Test SQL injection characters.
- Test empty strings.
For a file upload:
- Test files with no extensions.
- Test massive file sizes.
- Test malicious file names.
예전에 테스트 커버리지 95%를 달성한 결제 시스템을 작업한 적이 있습니다. 모든 테스트는 통과했습니다. 하지만 운영 환경에서 반올림 오류로 인해 시스템이 손실을 입었습니다. 우리의 테스트는 정상적인 경로(happy path)를 다루었지만, 아무도 수학적 로직을 테스트할 생각은 하지 못했습니다.
이제 저는 모든 테스트를 한 가지 질문으로 시작합니다. "이 기능이 조용히 실패(fail silently)하려면 어떤 조건이 충족되어야 하는가?"
포트폴리오 사이트를 만들지 마세요. 링크드인을 업데이트하지 마세요.
실패하도록 설계된 테스트를 하나 작성하세요. 만약 통과한다면, 안전이 보장된 것입니다. 만약 실패한다면, 버그를 찾아낸 것입니다.
무엇을 테스트했는지, 어떻게 테스트했는지, 그리고 무엇을 발견했는지 기록하세요. 그것이 당신이 사고할 수 있다는 진짜 증거입니다.
당신이 버그를 찾을 수 있다는 것을 증명하기 위해 이번 주에 작성할 테스트는 무엇인가요?
Optional learning community: https://t.me/GyaanSetuAi