Content Bugs - Summary

What are content bugs?

Nikolas Fantoni avatar
Written by Nikolas Fantoni
Updated over a week ago

Please note that this is just a summary article on Content Bugs. To learn more about these bugs, visit our main Content Bugs article.

In some tests, you can report content bugs related 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.

Repetitive problems

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 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.

Did this answer your question?