What Is The Difference Between Quality Assurance, Quality Control, And Testing?

                             Many people are confused about the difference between quality assurance (QA), quality control (QC), and testing. They are closely related, but they are different concepts. Since all three are necessary to effectively manage the risks of developing and maintaining software, it is important for software managers to understand the differences. They are defined below:

Quality Assurance: A set of activities designed to ensure that the development and/or maintenance process is adequate to ensure a system will meet its objectives.

Quality Control: A set of activities designed to evaluate a developed work product.

Testing: The process of executing a system with the intent of finding defects. (Note that the "process of executing a system" includes test planning prior to the execution of the test cases)

                 Testing is a process that everybody follows in their daily routine. Without testing anything no one can start a day. For example, when you wake up in morning, you will make sure check the time is the time that you want to wake up. If time is different than the time you want to wake up, you will go to sleep again. So you have already setup a requirement before you go to bed that you want to wake up at 8 AM and you will follow.
                  Same thing we have to follow in our testing job. The definition varies from person to person but objective is same. Testing is a process to make sure a functionality of a product or project meets requirements or not. If it meets then testing is passed else it is failed.

Testing Objectives

• Testing is a process of executing a program with the intent of finding an error
• A good test is one that has a high probability of finding an as yet undiscovered error
• A successful test is one that uncovers an as yet undiscovered error