Functional testing is the primary type of testing. It aims to check that the software's functional requirements match its actual behavior. The main goal of functional testing is to confirm that the software product under development has all the functionality the customer requires.

Depending on the goal, functional testing can be carried out:

• Based on the functional requirements stated in the specification. Test cases are created for the testing, and their design takes into account the priority of the software functions that need to be covered by tests. This way we can make sure that all the functions of the product under development work correctly with different types of input data, their combinations, quantities, and so on.

• Based on the business processes your application must support. Here we care less about whether individual software functions work and more about whether the operations are performed correctly from the standpoint of the system's usage scenarios. In this case, testing is based on the system's use cases (usecases).

• Based on common sense. Since there can be a mistake in the project documentation and even in the architect's head (something was forgotten, something was not taken into account), a tester must always be on their toes. When the written spec contradicts common sense and experience, the natural reaction should be: there's a bug here!

Unlike functional testing, whose goal is to check

the program's obvious ability to work, non-functional testing may not be stated in the requirements. This concept covers everything that affects the quality of the program but does not relate directly to its business logic.

Non-functional requirements characterize a product in terms such as:

• Reliability - the ability of a software system to work stably for a long time without human intervention
• Performance - how well the system works under various planned loads
• Scalability - requirements for horizontal or vertical scaling of the application. The application should adapt its layout gracefully and appropriately when structural elements are added or removed. The same goes for the application's architecture
• Security - protection of user data from hacking, protection of the system from outside interference and unauthorized access, and protection of user data from system errors
• Installation testing – checking that the application installs, is configured, and is uninstalled successfully. It reduces the risk of losing user data, of the application becoming unusable, and so on
• Usability testing – characterizes the system in terms of how easy it is for the end user to use
• Configuration testing (or portability testing) – investigating how well a software system works under various software configurations
• Failover and Recovery Testing – investigating how a software system recovers from errors and failures. Evaluating the reaction of the application's protective features
• Stress testing – a type of testing that characterizes the system in terms of how stable it stays under conditions beyond the normal. Don't confuse it with performance testing, because here we are talking only about peak loads, not the expected ones
• Performance testing – a group of testing types whose goal is to determine the operability, stability, resource consumption, and other quality attributes of an application under various usage scenarios and loads. Performance testing helps uncover potential vulnerabilities and weaknesses in the system, so that their harmful effect on the program's operation in real use can be prevented. Here we are talking only about the planned loads described in the product requirements
• Interoperability and compatibility testing – a type of testing aimed at evaluating how well the components of a software system, or the whole application, interact with other components or software

This is my favorite diagram. Take it to heart. Testing interviews very often include a task like this: test some object. It shows how flexible a tester's mind is when it comes to types of testing and the object under test. After all, it doesn't matter what is in front of you; what matters is understanding the logical concept of the types of testing. Study this diagram and absorb it FOREVER, if a tester you wish to become.

The time has come to put your new knowledge into practice.

First, practice the types of testing.

Your first task is to pick the item from the list that you like best and write one test for each type of testing.

Do it the same way we tested the pencil, but as a table (type of testing - test). The assignment should be prepared in a Google doc using this template and submitted through the form.

The second task is a theory test. Find out how well you understood the material. Don't forget to log in to the testing system.

The third task is even more hands-on. Try using the types of testing while testing the website. Write down all the bugs you find in a separate Google doc as well and submit it through the form. I believe you can do it!