![]() Web testing is tough. That’s why settling on a is necessary. Whether your organisation need to report defect in a bug tracking app like,, or keep a backlog in an Excel (xls) spreadsheet, a Word document (doc file) or via email, this post offers bug reporting templates you can copy and implement in your team. Find yours in this list: • Table of content • • • • • • • There are man different elements you can include in your bug report, but here are the most important. Usually, the bigger your organization, the more detailed your reports need to be. ![]() The indispensable elements are: • ID / Name: Keep it brief and use correct terms. A best practice is to include the name of the feature where you found an issue. A good example would be `CART – Unable to add new item to my cart`. • Description/ Summary: If you feel the name is not sufficient, briefly explain the bug with words. Phare it in a natural language. Keep in mind that your description might be used to search in your bug tracking application so be sure to use the correct language. • Environment: Depending on your browser, operating system, zoom level and screen size, websites may behave differently from one environment to another. Make sure your developers know your technical environment. • Source URL: Make it easy for your developers spot the problem by including the URL of the page where you found the bug. Big time saver! ![]() ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
April 2018
Categories |