Functional Bugs

Functional bugs are related to functionality. If a button doesn’t work, if the search doesn’t react to the user input or if an app crashes – it’s a functional issue. Every time you click and the website/app doesn’t respond as it should, it’s probably a functional issue.

If there are elements out of place or pictures with bad quality, it is not a functional bug.

Functional bugs have three priorities:

Low: Minimal impact on user experience

High: Serious impact on user experience, but doesn’t prevent the function of the app or website.

Critical: Preventing a main function of the app or website, Causes a potential loss of income for the company running the app or website. e.g. an app crash.


App Crash:
Critical issues like crashes etc. have to contain crash logs as part of the documentation. Please note that the video that documents the crash has to correspond (exactly) to the attached crash log, i.e. timings must be coherent.
This goes also for reproductions of those bugs.

Edge Cases:
Edge case bugs are never critical, even if they are crashes.
An edge case would be anything that does not reflect typical user behavior. A good example would be repeatedly opening and closing menus. Basically, every bug that is forced is an edge case.

Security issues:
Security issues (including XSS attacks) are not considered as functional issues. If a customer is interested in this topic, a specialized security-focused cycle will be set up. In all other cases, security-related issues are considered out of scope.

Application blocked by SmartFilter / Virus scanner
If the execution of an app is blocked by a smartFilter or by a virus scanner, this is no bug. Especially if it is a staging environment or a beta version of an app.

Severity Assessments:
Here you will find a list of more severity assessments and example for bugs often reported. The list will be updated with new bugs over time.

Take me to the list



%d bloggers like this: