🙌Today, we'll roll back to Test Types and look deeply into categories of ☝🏻 the Formal Test Case types.

The list of them you will find in the previous post: Types of Test Cases in software testing. Part 1.🧐 Check it out if you've missed it.

Formal Test Cases:

✅Functionality - the most obvious because its primary purpose is to determine whether the target functionality of the product works appropriately or fails to perform its function. QA Engineers write functional test cases looking at the product requirements and execute them as soon as the function is released.

✅UI. These tests focus on the application's visual elements to confirm they perform as intended for the product. Display elements such as menus, sub-menus, buttons, tables, and columns are checked to ensure they are precise and concordant.

✅Integration. It's designed to evaluate how combined features work when added to an application. While it is important to test individual pieces of software, it is equally essential to ensure that disparate systems can communicate effectively with each other. QA Engineers must understand application flows well to write effective integration tests.

✅'Pressure tests' and 'Load tests' these terms sometimes interchangeable. Performance checks execute to see if the device meets the productivity requirements.

✅Usability. These tests are prepared by UX researchers for end users, not testers, to assess how easy or difficult the product is to use.

✅Database. These tests verify application data is stored following requirements and regulations. The scope can vary from testing a small database object to a complex action involving multiple application parts.

✅User Acceptance. These tests are valuable when business requirements change during development. QA Engineers can document entry/exit criteria that fill gaps in other tests.

✅Exploratory test cases are valuable when QA Engineers test the application to discover bugs missed by structured testing.