Testing is an activity. Anybody can test. Sometimes testing is just using a product. Quality assurance is a focus on measuring and improving the quality of some product. QA looks at the product itself and the processes and systems that produce that product. QA does use tests and testing as part of its toolbox, but it takes a high-level strategic look at the *problem* of testing that product in that domain in order to identify what *could* be tested and to define what *will* be tested. Testing is an activity, while QA uses testing strategically, after planning how and what to test, wait for it…, strategically. An analogy: say that you can cook. You are pretty good at keeping your family happy with reasonably appetizing dinners. Cooking is an activity, albeit one where some planning and skill of execution is necessary. Given that you can cook dinner for your spouse and kids, could you run a restaurant? Could you plan weekly menus, source the supplies, manage freshness and supplies turnover, set up a cooking line, design the menus, train staff, set up and manage front and back of house teams, etc., and deliver deliver deliver. The individual ability to cook something is a small — even if essential — part of a larger process (project) that is complex, dynamic, and full of pressure, and that requires strategic view and tactical execution. Quality control involves inspecting the product and evaluating against some set of quality criteria. In our analogy, this would mean examining the presentation of the meal, and seeing if it tastes correct (assuming it tastes *good*, too). Quality assurance would be looking into changes in the kitchen and process to correct problems with the dishes presentation or taste, AND finding ways to improve it even if it is already pretty good.