Finding a bug is only half the job. I learned quickly during my internship that a bug nobody can understand from the report is a bug that never gets fixed, no matter how real it is. The format that changed everything for me Every single bug report I wrote followed
Before this internship, I thought QA meant clicking around a website until something looked wrong. My first real assignment, testing the Singh Engineering Works site, taught me it's a lot more structured than that, and a lot more useful. Expected vs Actual is everything The first thing I
If someone had told me before this internship that accessibility testing mostly means putting my mouse away, I wouldn't have believed how much that one change reveals. The Tab test One of the simplest checks I picked up was this: click the browser's address bar, then
One of the most effective parts of my QA internship was testing the same product on two platforms, the HomeSewa website and its mobile app, and realizing how differently they can fail. Same brand, two different experiences On paper, HomeSewa's app and website are supposed to offer the
Some of the most interesting bugs I encountered as a QA intern weren't about whether a feature worked, they were about what happened right at the edge of what it was supposed to handle. Testing the edge Early in my internship, I mostly tested with "normal"
Of everything I tested during my internship, SEO analysis was the part I expected the least, and learned the most from. It turns out a QA tester can catch problems that quietly hurt a business's visibility on Google, long before marketing ever notices. Starting with robots.txt My
Not every bug I found during my internship was dramatic. Most of them were small, almost boring on their own. But testing across half a dozen different websites and apps taught me that small, repeated problems add up to a much bigger trust issue for users. The "everything leads