𝗧𝗵𝗲 𝗧𝗲𝘀𝘁𝗲𝗿 𝗪𝗶𝘁𝗵 𝟭𝟬 𝗖𝗲𝗿𝘁𝘀 𝗪𝗵𝗼 𝗖𝗼𝘂𝗹𝗱𝗻'𝘁 𝗙𝗶𝗻𝗱 𝗮 𝗕𝘂𝗴
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.
Saya pernah mengerjakan sistem pembayaran dengan cakupan (coverage) 95%. Setiap pengujian berhasil. Kemudian, sistem tersebut kehilangan uang di produksi karena kesalahan pembulatan. Pengujian kami mencakup jalur utama (happy path), tetapi tidak ada yang terpikir untuk menguji logika matematikanya.
Sekarang, saya memulai setiap pengujian dengan satu pertanyaan: "Apa yang harus terjadi agar fitur ini gagal secara diam-diam?"
Jangan membangun situs portofolio. Jangan memperbarui LinkedIn Anda.
Tulis satu pengujian yang dirancang untuk gagal. Jika berhasil, Anda memiliki jaminan keamanan. Jika gagal, Anda menemukan bug.
Catat apa yang Anda uji, bagaimana Anda mengujinya, dan apa yang Anda temukan. Itulah bukti nyata bahwa Anda bisa berpikir.
Apa satu pengujian yang akan Anda tulis minggu ini untuk membuktikan bahwa Anda bisa menemukan bug?
Komunitas belajar opsional: https://t.me/GyaanSetuAi