Product Testing and Quality Assurance

🧪 QC vs QA in a GMP Lab — What’s the Difference? In a GMP-regulated lab, both Quality Control (QC) and Quality Assurance (QA) are essential — but they focus on different parts of the quality journey. 🔹 Quality Control (QC) = Detection QC checks the final product and materials to detect any issues. ✅ They run tests, analyze data, and make sure everything meets specifications. Examples: • Testing pH, cell viability, or sterility • Inspecting incoming raw materials • Verifying lot release data • Investigating out-of-spec results (OOS) 🔍 QC asks: “Is this product or component meeting the required standards?” 🔹 Quality Assurance (QA) = Prevention QA focuses on the systems and processes that ensure everything is done correctly from the start. ✅ They ensure documentation is followed, processes are validated, and teams are trained. Examples: • Reviewing SOPs and batch records • Monitoring deviations and CAPAs • Validating procedures • Auditing GMP practices 🛡️ QA asks: “Did we follow the right process to ensure consistent quality?” 📌 In short: QC = Tests the product 🧪 QA = Protects the process 🛡️ Both are critical for maintaining compliance, consistency, and trust in regulated environments like biotech and pharma.

If I had to start my QA career all over again in 2025... I’d do it completely differently. When I started, I thought QA was just about “breaking things.” Now I know — it’s really about understanding how things break, and why. So here’s exactly how I’d begin today 👇 🔹 Step 1: Learn what “Quality” actually means It’s not about perfection — it’s about trust. Learn validation vs verification. Ask: “Does it work?” Then ask: “Would I use it?” — that’s the real test. 🔹 Step 2: Get your toolkit right Forget trying to learn everything. Start with: 🧠 Jira / Confluence — for structure 🧪 Postman — for APIs 🧰 Git & GitHub — for collaboration 🌐 Cypress / Playwright — for automation (you’ll thank yourself later) 🔹 Step 3: Understand Testing Types Manual ➡️ Integration ➡️ Regression ➡️ E2E Then peek into TDD and BDD — it’s like learning how devs think (and argue 😅). 🔹 Step 4: Design isn’t “extra” Learn Figma. The best QA engineers don’t just click buttons — they question user logic. (“Wait… why is the ‘Cancel’ button red?” 🤔) 🔹 Step 5: Grow with advanced tools Appium → Mobile testing JMeter → Performance Docker → Environment setup Cucumber → BDD Zephyr → Test management ✨ Bonus wisdom: Anyone can test features. But real QA engineers test assumptions. That’s where true product quality begins. 💬 If I were mentoring a fresher today, I’d tell them — Don’t chase tools. Chase clarity, communication, and critical thinking. Those are the skills AI can’t replace.

Good V&V testing is boring V&V testing! At least that’s what I’ve found in many development projects for new medical devices. In other words, if the product team wants formal V&V testing to go smoothly (to be boring with no exciting surprises), they need to spend a lot of time on the informal testing preceding it (AKA pre-DVT, engineering testing, characterization testing, etc.). Thinking about product testing in the broad categories of informal versus formal, each with its own goals and methods, will help the team be both more efficient and avoid some of the biggest problems in V&V testing. Here are the key differences between the two categories of testing: ➡️ Informal testing:   -Goals: learn about the product, discover and correct design flaws, develop new test methods and test tools   -Includes broad, open-ended test methods   -Lots of test failures means lots of learning and improvement (beyond “meeting the spec”) ➡️ Formal testing:   -Goals: demonstrate to others that the product design is sound   -Testing performed per detailed test methods and test protocols under change control    -Devices built under controlled conditions   -Expect to pass all of the tests (you should already know the answers before beginning); test failures mean big, expensive delays in the project Treating formal V&V as a way to discover the defects in a new medical device is a very expensive approach to completing the product design. Instead, product teams should maximize the effort put into informal testing to flush out defects as early as possible in development. Then completing formal V&V becomes predictable and efficient. Informal testing should be part of each project’s design and development planning to ensure that sufficient time and resources are provided to these crucial activities (don't wait until the “V&V Phase” of the project). This approach also enables development of new test methods and test tools. Do product teams at your company make informal testing part of their project planning? What approaches have you found valuable to get through the challenges of medical device V&V testing? What tips do you have to make V&V more boring?

🚨 The Two Pillars of Modern QA: From Error Prevention to Error Detection 🚨 In traditional Quality Assurance (QA), the main job is Error Prevention. This means finding and fixing bugs before the software is used by real people. This step is very important to make sure the software works well in controlled settings. Here are the main methods used in this phase: ✅ Manual Testing: Even though we use automation, manual testing is still necessary for complicated tasks and special situations. ✅ Automated Testing: Tools like Selenium and Cypress help run tests that can be repeated, making sure that new changes in code do not break old features. ✅ API and UI Testing: This checks that the back-end (server side) and front-end (user side) of the software work well together. ✅ Static Code Analysis and Coverage: Using tools like SonarQube helps ensure that the code is of good quality and reduces problems in the future. Error Prevention has been the main focus of QA for many years, but it cannot find every problem that happens in real life. 📍 The New Role of QA: Error Detection (Post-Release Monitoring) Once the software is live, Error Detection becomes very important. Even with good testing before release, real-life use can show new bugs. In modern QA, monitoring after the product is released is crucial. This part focuses on finding and fixing problems as they happen. Here are key practices: ✅ Log Management: Tools like Datadog help QA teams watch the system logs and find problems quickly. ✅ Error Tracking: Tools like Sentry catch and track errors in real-time, allowing for fast fixes. ✅ Real User Monitoring (RUM) & Session Replay: This gives insights into how real users interact with the software, helping find issues they face. ✅ Dashboards and Alerts: Monitoring important numbers and getting alerts on serious errors help the team act quickly. By using post-release monitoring, QA changes from being passive testers to active protectors of product quality. This way, we can fix issues that pre-release testing might miss.

MULTI-LEVEL QUALITY CHECKLIST: DAILY TASKS FOR INSPECTION, CONTROL, AND ASSURANCE LEVEL 1: Operator / Technician Level Focus: Task Execution & Self-Inspection Conduct equipment/tool pre-checks before starting work Verify correct raw materials or components are used Perform visual inspection for defects (scratches, contamination, etc.) Carry out first article inspection at the start of production Record process data and inspection results accurately Report any abnormalities, deviations, or non-conformities immediately LEVEL 2: Supervisor / Line Leader Level Focus: Process Monitoring & Quality Control Perform random spot checks on product quality throughout the shift Verify machine settings and process parameters at shift start Review and validate operator logs for completeness Monitor for trends or recurring defects Initiate corrective actions for any process or product issues Provide regular feedback and quality reminders to team members LEVEL 3: Quality Control (QC) / Inspection Team Focus: Product Verification & Defect Prevention Inspect incoming raw materials or components against specifications Conduct in-process inspections during production runs Perform final product inspections before packaging or shipping Check calibration status of measuring and inspection equipment Log and escalate all non-conformances using NCR forms Analyze daily quality data for trends or high-risk issues LEVEL 4: Quality Assurance (QA) / Management Level Focus: System Oversight & Continuous Improvement Audit production and QC records for compliance Review daily quality performance metrics (e.g., defect rates, yield) Track and address customer complaints and feedback Review process data to identify improvement opportunities Follow up on CAPAs to ensure resolution and effectiveness Confirm training and certification status of staff is up to date

#From raw materials to finished product—as handled by Quality Control (QC) and Quality Assurance (QA): 1. Raw Materials Testing (QC Stage) Sampling: Raw materials (e.g., APIs, excipients) are sampled as soon as they arrive. ✓Testing: QC analysts perform tests like: =Identification (FTIR, UV-Vis, HPLC) =Purity and potency (Titration, HPLC, GC) =Microbial limits (for certain materials) #Approval/Quarantine: If results meet specifications, the material is released for production; otherwise, it's quarantined or rejected. 2. In-Process Testing (QC Stage) ✓During manufacturing, QC monitors the production steps to ensure everything is within control: =pH, temperature, and reaction times =Tablet hardness, weight, and friability (in solid forms) =Viscosity or clarity (in liquids) ✓These checks help prevent deviations before the final product is made. 3. Finished Product Testing (QC Stage) ✓After production, the final product undergoes =Assay (to check active content) =Dissolution (for tablets/capsules) =Sterility/microbial testing (for injectables/liquids) =Uniformity and physical appearance ✓Results are recorded in a Certificate of Analysis (CoA). 4. Documentation and Review (QA Stage) ✓QA reviews all QC data and batch production records to verify: =Compliance with Good Manufacturing Practices (GMP) =No deviations or out-of-spec results =All procedures were followed correctly ✓QA also ensures traceability and data integrity. 5. Final Product Release (QA Decision) ✓QA has the final say on whether a batch can be: =Released to the market =Held for further investigation =Rejected due to non-compliance

Quality Control (QC) plays a crucial role in pharmaceutical companies by ensuring that products meet the required standards of quality, safety, and efficacy. Here are some key responsibilities and functions of QC in this industry: 1. Testing and Analysis: QC is responsible for testing raw materials, in-process samples, and finished products to ensure they meet specified quality standards. This includes physical, chemical, and microbiological testing. 2. Compliance with Regulations: QC ensures that all products comply with regulatory requirements set by agencies such as the FDA, EMA, and other relevant authorities. This includes adherence to Good Manufacturing Practices (GMP). 3. Method Validation: QC develops and validates analytical methods to ensure they are reliable and reproducible for testing pharmaceutical products. 4. Documentation and Record Keeping: QC maintains comprehensive records of all testing and analysis performed, ensuring traceability and accountability. This documentation is essential for regulatory inspections and audits. 5. Stability Testing: QC conducts stability studies to determine the shelf life of products and ensure they maintain their efficacy and safety over time. 6. Deviation Management: QC investigates any deviations from established protocols or specifications, identifying root causes and implementing corrective actions to prevent recurrence. 7. Training and Development: QC is involved in training staff on quality standards, testing procedures, and regulatory requirements to ensure a culture of quality within the organization. 8. Collaboration with Other Departments: QC works closely with other departments, such as Research and Development (RD), Production, and Regulatory Affairs, to ensure quality is integrated throughout the product lifecycle. 9. Risk Management: QC assesses potential risks to product quality and implements strategies to mitigate these risks throughout the manufacturing process. 10. Continuous Improvement: QC is involved in initiatives aimed at improving processes, enhancing product quality, and increasing operational efficiency. Overall, the role of QC in pharmaceutical companies is integral to ensuring that products are safe for consumers and effective in treating medical conditions.

What’s the difference between testing and Quality Assurance? Many use the terms interchangeably, but testing and QA play different roles in the software development lifecycle. Testing is about detecting defects—it ensures that the product functions as expected. Quality Assurance, on the other hand, is a preventative measure, focusing on establishing processes to avoid defects from the start. By implementing shift-left approaches, like SQA²’s QA 2.0 methodology, QA begins at the requirements phase, ensuring that quality is built in from day one. A common cause of defects lies in incomplete or unclear requirements; QA involvement early on ensures that specifications are clear, accurate, and comprehensive. In startups or agile environments, where speed and adaptability are crucial, integrating QA from the beginning minimizes costly rework, accelerates delivery, and improves product quality. Partnering with a QA organization like SQA² allows companies to maintain high standards, even in fast-paced settings. How early do you involve QA in your projects, and how has it impacted your development process?