Ten lessons I learned in my first year of software testing

Photo by Ruijia Wang on Unsplash
  1. Real software testing begins after acceptance testing is complete. In the software testing process, acceptance testing is just the tip of the iceberg.
  2. There is a visible and an invisible component to a website. The tester should look at as much of the website’s invisible part as the visible part. Testers should search for unseen bugs to identify their impact on the visible part of the system. Google Dev Tools are the best friend of a tester.
  3. Testers break software and developers build it. Nevertheless, testers break software in order to help developers protect them against future problems.
  4. Exploratory testing involves thinking about things that software engineers or product designers might not have thought about or overlooked. Testers should also think about ways to improve their thinking skills.
  5. The more you study website technologies, the better you understand how an organization’s website works, and its weaknesses, the more dangerous your testing becomes.
  6. Find the bugs that developers and product managers care about the most and you’ll make their day. “A good catch” is the best compliment for the tester he can get.
  7. Software developers do not always believe in your found edgy bug, so the best solution is to make a video recording to convince them. Screenshots aren’t enough all the time.
  8. Inquiring about the website is as essential a software tester’s character trait as curiosity, attentiveness, desire to break. You need to define what software testing means to you. It gives a unique perspective to test the website and look for bugs. Testing the software has no one definite method.
  9. Testing with multi-tier systems is the best way to learn software testing as it provides many different scenarios to test the website as well as numerous chances to look for bugs that were not previously observable.
  10. Knowing and reading about software testing is as important as practising it. When combined, these two elements will enable you to improve your abilities as a software tester. Reading will teach you what you have to know about software testing and what next to learn, how to improve the things you already know, while practicing will give you experience and will make you faster at finding bugs because you will know where to look and you will know how to find them.

Testphilosopher. A diary on software testing, automation, and personal reflections