The second part of your testing journey is to equip yourself with common tools that are very useful for your testing activities.Have your test cases ready
Test cases are the foundation for the test execution and automation in the later stage. You should be familiar with test case management tools such as Testrail, Xray, and Zephyr. These tools will help you manage your test cases when they keep growing and also create the testing report with ease. To learn more about test cases, check out this list of example test cases in this website testing checklist.Start executing tests
Once you have the test cases ready, you need to know how to execute the tests. Commonly, a web application supports multiple browsers (Chrome, Firefox, Safari, etc.) and platforms (Windows, macOS, Android, iOS, etc.). If you don't have access to multiple devices, cloud services can be a simple solution. Learn how to use some cloud services that provide the ability to perform such tests efficiently. Some cloud services you could use are BrowserStack or SmartBeer.
The primary purpose of testing is to find defects of the web apps and report them to developers so that you can fix them. Writing a good bug report is an art in itself. A good bug report consists of essential details that provide developers with enough information to reproduce and find out why
a problem happened. To do this, you'd need to piece and combine all information in one place. Some essential details you need to include in a bug report are:
- Console log
- Screenshot or video of the issue, and more
Keep track and communicate issues
Finally, once you've reported all issues you've found, use bug tracking tools
to help you keep track and communicate with your team. Many cloud services provide a way to manage bugs such as Jira, Trello, Linear, or GitHub. Fun fact: Bug reporters using Bird Eats Bug notice a significant decrease of unnecessary back-and-forth with developers, saving up to 2-4 hours/day.