Give examples for classification by testing priority and severity: high priority, low priority, trivial, and serious.

The following combinations are used when classifying defects by priority and severity:

High priority, high severity: A defect that blocks core functionality or causes the entire system to fail. For example, inability to log in to an online store or the application crashing during checkout.

High priority, low severity: A minor defect that still affects many users or is critical for the business. For example, incorrect display of the company's logo on the main page or a typo in the name of a key product.

Low priority, high severity: A rare, hard-to-reproduce defect that causes system failure but affects very specific scenarios. For example, a service crash when performing ten very complex, atypical operations by less than 1% of users.

Low priority, low severity: A visual defect or minor grammatical error that does not affect functionality. For example, incorrect alignment of an element in the footer or a typo in a minor tooltip.

Trivial defect: A defect that does not affect functionality and is almost unnoticeable to the user. Often cosmetic imperfections. For example, an extra space after punctuation that is not visible in the user interface, or an incorrect color of a rarely used element.

Serious defect: A defect that disrupts key functionality or causes significant issues in system operation but does not lead to a complete failure. For example, incorrect discount calculation in the shopping cart for certain products, or sending a duplicate email to the user.

Table with examples of combinations:

Priority	Severity	Example
High	High	Inability to log in
High	Low	Incorrect logo on the main page
Low	High	Failure in a rare, specific scenario
Low	Low	Incorrect alignment in the footer
-	Trivial	Extra space in unnoticed text
-	Serious	Incorrect discount calculation