𝗧𝗵𝗲 𝗧𝗲𝘀𝘁𝗲𝗿 𝗪𝗶𝘁𝗵 𝟭𝟬 𝗖𝗲𝗿𝘁𝘀 𝗪𝗵𝗼 𝗖𝗼𝘂𝗹𝗱𝗻'𝘁 𝗙𝗶𝗻𝗱 𝗮 𝗕𝘂𝗴
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%の決済システムに携わったことがあります。すべてのテストはパスしていました。しかし、本番環境で丸め誤差が発生し、システムが損失を出してしまいました。私たちのテストは正常系（ハッピーパス）を網羅していましたが、計算ロジックをテストしようとは誰も考えていませんでした。
今では、すべてのテストを一つの問いから始めます。「この機能が、エラーを出さずに（サイレントに）失敗するとしたら、どのような条件が満たされた時か？」
ポートフォリオサイトを作る必要はありません。LinkedInを更新する必要もありません。
「失敗することを目的としたテスト」を一つ書いてください。もしそれがパスすれば、安全性が保証されたことになります。もし失敗すれば、バグを見つけたことになります。
何をテストしたか、どのようにテストしたか、そして何を見つけたかを書き留めてください。それこそが、あなたが「思考できる」という真の証明です。
あなたがバグを見つけられることを証明するために、今週書くテストはどのようなものですか？
オプションの学習コミュニティ: https://t.me/GyaanSetuAi