Please note that this is just a summary article of Content Bugs. In order to learn more about Content Bugs, please visit our main Content Bugs article.
In some tests, you can report content bugs which relate to the actual content of websites or apps, such as broken links or images, defective redirections, missing text or content, missing translations, and missing data.
If a content problem happens repeatedly, it should only be submitted once, even if it occurs on different pages or URLs. One bug report can cover all affected URLs, links, pictures, etc. Individual bug reports for each occurrence of the issue will not be accepted. The customer only needs one report to investigate and solve the problem for all occurrences.
Upgrade to functional bug
Report content bugs that cause issues with functionality as functional bugs. If the functionality can still be reached easily via another path, the problem should be reported as a content bug. Content bugs that occur in functional components like navigation menus or footers should be reported as functional bugs, but they are typically Low bugs.
Documentation of content problems
Content reports must contain screenshots. For more information on how bug reports must be documented, visit our article Bug Report Requirements.
Bug Report Requirements – our quality standards