Quality Assurance (QA) vs. Quality Control (QC) in the web project.

"The web is finished ... but why is it messy?" The problem of the world broke the web people to meet!

Have you ever met yourself? Project to make a website that is intended to mold with hands Sit out both the budget and many months. On the day of the launch, he encountered various problems, swollen in time! The keypad is not, the link is broken, the webpage is broken on the mobile phone, the backyard system is so slow. Or the most serious is Customers pay but the system does not work! The feeling of excitement was happy that the web launched ... turned into stress and complaints from customers instead.

If you used to nod in these stories Show that you are not faced by this problem alone. This is the classic nightmare of the project owner and many web development teams. That often occurs when we overlook the "quality" or misunderstand that "The final website test before sending the work" is enough. But the truth is a lot more complicated than that And the beginning of all solutions Hidden in two words that look similar. But the different meaning is "QA" and "QC".

Prompt for illustrations: Graphic images that show the stressful expression of the business owner or Project Manager, who is holding the temples in front of the computer that shows the website full of errors (ERROR 404, the picture does not display, Layout distorted) with a full red icon.

Why is the new launch website having a problem? Solve the origin of the error

Many people tend to combine that web quality inspection is "Bug Bug" at the end of the project, but actually, that's just the end of the problem. The true source is often caused by confusion between the two main concepts: ** Quality Assurance (QA) ** and ** Quality Control - QC) ** These two separation Causing the web development process to lack proactive prevention

Imagine:

• Teams that focus only on QC (Reactive): will accelerate the development of various features. To finish as soon as possible And then come to chase "catch the fault" or "Test finding" together in the final period before delivering the work The result is that there are many problems that are deeply rooted and difficult to solve. Must dismantle the new code Waste of time and budget escalating
• The misunderstanding team: Some teams may think that having a test is to find a Book is to do QA, which is not correct. Finding a bug is part of QC, but not all QA, causing lack of planning to prevent problems from the source.
• No central standards: When there is no clear QA process, each developer may write different styles. No clear reference documents Causing when the work is combined, it can easily cause errors Like building a house by architects and engineers talking to different languages

These roots that make your website look like a time bomb. Waiting for the day to create problems after the launch. Which affects more than you think Understanding the differences of QA and QC is the first step in the building to build a strong website. Having a checklist for good websites is part of the QA planning that helps reduce errors as well.

Prompt for illustrations: simple infographic images Compare two routes One way is a winding path named "Focusing on QC at the end", which is full of icons and red lights. With another straight and smooth route named "QA throughout the process" which leads to the trophy written "quality website"

Release the website that lacks quality ... the disadvantage that is more serious than just "losing face"

Letting the website full of errors go out to the user's eyes Does not affect the impact, just causing the "losing" team or "waste time" to fix, but it directly affects the business in many dimensions that are much more scary than that:

• Loss of credibility and destroying the image. Brand: Website is the face of business. If the customer comes in and finds only the web is broken slowly, it is difficult to use. The confidence that your brand will decrease immediately. And may not come back again
• Lost business opportunities and sales: Imagine that customers want to buy things will be broken. But can't press the payment button Or fill out the form. Contact the website ... that is the sales and the LEADS that disappeared in the blink of an eye. And may mean the loss of that customer to the competitors forever
• Wasting marketing budgets. Benefits: You may throw a lot of money to shoot Facebook or Google Ads to pull people into the web. But if your website doesn't really work Is like pouring water into a leaky tank The traffic that was obtained will not mean. While also increasing advertising fees because the BondCe Rate is increasing
• In the long term SEO: Google is very important to the user experience (User Experience). The website that loads slowly, has a high bounce rate, or Broken Links will be reduced continuously. Make your search search worse.
• Higher correction costs: The correction of the bug after the Live website has been costly higher than the prevention of bugs from the beginning. Both in terms of time, manpower and loss of business opportunities

Therefore, investing in the process of creating "quality" is not "cost", but the most important "investment" to prevent these damages from occurring. Making UX Audit Process regularly is one way to help find and solve these effects.

Prompt for illustrations: Dairy images that show negative effects, starting from "web with bug" and have an arrow pointing to "Customers are frustrated", "lose sales", "brand loss", and "SEO rank" is Domino Effect.

Solve the cause! Separated between QA and QC and then used as

When understanding the problems and impacts It's time to see the right solution. The key is to distinguish and lead both ** QA (Quality Assurance) ** and ** QC (Quality Control) ** to use in your project correctly.

In order to see the most obvious image Imagine health care:

• QA is "preventive health care": like you plan to eat useful food, regular exercise, sleep enough All of this to "prevent" not to get sick from the beginning.
• QC is the "annual health check": like you go to the hospital for blood tests, measurement, x -ray to "check" and "Search" what diseases are hidden in your body.

Will see that we want both Can't live without The web is the same.

Quality Assurance (QA) - Quality Assurance (emphasizing "process" to "protect")

QA is a proactive activity that focuses on ** "Working process" ** to ensure that the final result will come out quality and reduce errors to a minimum. It is to create a standard and set up the protection system since before writing the first line code.

Example of QA activities:

• Setting the Coding Standards standards
• Choosing the right technology and tools
• Creating clear Requirement and Spec documents
• Workflow design, such as using Webflow Staging Environment to have a safe test area.
• Training the team to have the same knowledge and understanding.

Quality Control (QC) - Quality control (emphasizing "results" for "inspection")

QC is a receiving activity (Reactive) that focuses on ** "Results" ** or the website created To check and identify the error (Defects) that occur as much as possible before the real user website

Example of QC activity:

• Tested various functions Whether it works correctly according to the request or not (functional testing)
• Examination of display on different browser and equipment (Cross-Browser/Cross-Device Testing)
• Performance testing
• Broken link checking

So instead of asking, "QA and QC, which one is better?" The correct question is ** "How can we merge both QA and QC into our project?" ** ASQ (American Society for Quality) has clearly described this difference that QA is a process planning. QC is checking the results of that process.

PROMPT for illustrations: Infiguer image, Table 2 column, comparing QA and QC clearly. QA column has a picture icon "Calendar, document" with keywords "proactiveds, preventings," QC column "with an enlarged icon" with keywords "with reacle Product-Oriented, Identify Defects "

Examples from the real thing: when Tech turned the web crisis ... into a smooth launch

In order to be clearer I would like to give an example of the company "Innovatech" that made a saas platform for project management.

The first expensive lesson: In the opening of the version 1.0, the Innovatech team focuses on the development of features as soon as possible. With only superficial QC in the last week before launching The result is a disaster! Users encounter many bugs. The system often crashes. Some customers are missing. The team must work in the evening to follow the problem. Causing both the reputation and the first group of customers

Cleaning thin and newly created in version 2.0: From that lesson In the development of version 2.0, they have adjusted all the new processes by using QA and QC principles seriously.

• QA level (prevention):
  • Located on the foundation: they define the "Coding Standards" that everyone must follow, create "Design System" to make the UI consistent and write "Technical Specification" of all features.
  • Create a process: There is a "Code Review" every time before combining the code and using the "Continuous Integration (CI)" system to test the new code automatically.
• QC step (inspection):
  • Create a test plan: Test team creates a "Test Cases" that covers every possible situation.
  • Divide the tests into rounds: Unit Test by Developer, Integration Test by QA team, and finally, User Acceptance Test (UAT), with the actual sample customers try.
  • Checklist before releasing: Before launching, they used Post-La Unch Checklist thoroughly to check everything for the last time.

Different results and abyss: The release of version 2.0 is very smooth. The number of bugs that the user reported by more than 90%. The system is highly stable. And new customers give excellent satisfaction scores This is the power of the integration of QA and QC, which has changed from a project that almost failed to become a successful product.

Prompt for illustrations: The picture of the Graphic BEFORE & After is a rocket that is about to release, but there is a black smoke and a broken piece with "Version 1.0 (QC only".

What do you want to do? Checklist for using QA/QC to actually use

Read here You would like to apply these principles to your own project, right? You don't have to worry about not being able to try using this simple checklist as a guideline, which is divided into 2 main parts: ** QA activity (do all projects) ** and ** QC activity (made around) **

Part 1: QA activity (Quality Assurance - Prevention)

These should be part of the work culture in every project:

• [] Clear goals and Requirement: Everyone in the team must understand that "The finished website" looks like What features are there?
• [] Create working standards (Standardization):
  • - There are Coding Standard and Style Guide for Developer.
  • - There is a Design System for Designer to control the design tone.
• [] Documentation: Technical decision notes, API methods, or other important information That the team must use together
• [ ] Planning on the test area: Determine workflow works through clear Staging Environment so that it can be tested and reviews without affecting the actual website .
• [] Provide a review of the work (Cross-Functional Review): For example, developer, reviews of each other, Designer. Reviews at the Developer work up the web frame and etc.

Part 2: QC activity (Quality control - Sure check)

These will happen at the important points of the project, especially before delivery:

• [] Create a Test Plan and Test Cases: What are the plan to test? And how are the test procedures? Good information sources like Guru99 have examples to study more.
• [] Functional testing: Check if all functions work correctly as designed or not (such as application, ordering, forming)
• [] Usability & UX Testing: Test whether the website is easy to use or not? Is the user confused? UX Audit can help in this part a lot.
• [] Compatibility Testing: Check the display and work on
  • - Popular browser (Chrome, Firefox, SAFARI, EDGE)
  • - Equipment (Desktop, Tablet, Mobile)
• [] Performance Testing: Test the webpage loading speed and measuring with tools like Google Pagespeed Insights.
• [] Do User Acceptance Testing (UAT): Let the real customers or users try to try and give feedback before the launch.

Having a comprehensive checklist will help you be sure that nothing is dropped. And ready to deliver High quality website That creates good results for your business

Prompt for illustrations: The beautiful checklist images are divided into 2 parts, which are "QA Process" and "QC CHECKPOINTS" with the right tick side.

Questions that people tend to doubt (FAQ) clear all issues on QA vs. QC.

So you can understand this more deeply I have compiled a common question about QA and QC to answer clearly.

Q1: In the team, it is necessary to have a "QA" and "QC" position separately?
A: In a large team or complex project Having a separate position (such as QA Manager and QC/Tester) is considered Best Practice, but for small teams or startups that are limited No need to have a separate position. But the important thing is ** Everyone in the team must understand and responsibility for their roles. ** For example, Project Manager may take care of QA, Developer. UNIT Test (part of the QC) and the owner of the project or the marketing team to make UAT (User Acceptance Testing).

Q2: If our business is very small There is no additional budget for the team. What should I focus on first?
A: If you have to choose ** Start by creating a good QA culture first ** because the prevention has a lower cost than always. Trying to create a clear work process, have good documents, and often communicate in the team. QC can do at a basic level, such as developers helping to test the work of friends. Or let people who are not techniques in the company to help play the web in the real user's corner

Q3: What is the difference between QA and QC?
A: It's a very good question! To look at 3 layers of overlapping images:

• Software Testing: Is the "activity" test to find bug. Is the smallest part
• QC (Quality Control): is the "process" that uses software testing and other activities. To check the quality of "results" (website)
• QA (Quality Assurance): is the "framework" that covers both the development process and QC process to ensure that everything will meet the standards and "prevent" from causing problems from the beginning.

In short, Testing is part of the QC and QC is part of QA.

Q4: We should start doing QA and QC since when the project?
A: ** QA starts from the first day (Day 1) ** of the project. From the collection of Requirement and planning. ** QC will start periodically. ** When there are works or results, for example, when the feature A is finished, the QC's QC features, when the SPRINT is done, the SPRINT and the big QC will be opened before the actual website.

Prompt for illustrations: People are talking. With question markers and correct marks To convey the question-answers that clear the questions

In conclusion, easy to understand: QA and QC are not enemies, but the partner to the quality website.

At this point, I believe that you should clearly see that ** QA (Quality Assurance) ** and ** QC (quality control) ** Not the same thing. And cannot be substituted at all

To remember easily like this:

• QA is looking forward (Forward-Looking): How can we "prevent" problems? Is our process good enough?
• QC is looking back (Backward-Looking): The result "Where are the problems"? What do we have to fix?

Creating high and high quality websites Can no longer rely on the final bake of the project But requires a systematic defense plan (QA) in parallel with intense inspection (QC) along the way, like "Ghost Ventian" and "Sorcerer" in the same team

I would like to invite you to try to explore the web process in your team. That today we have a "partner", this pair is complete, and are they working together well enough? Investment is effective to create quality processes from today. Is to lay the strongest foundation for the long -term success of your business online

It's time to change the website that "just finished" to be a "quality" website! If you need a partner or expert to help set up and create a system High quality website that drives your business Our team is ready to give advice!

Prompt for illustrations: Beautiful graphics, QA icon (defensive shield) and QC (magnifying glass) are holding hands. With a rising graph background With the message "Better Quality, Better Results"

‍