Category Archives: Software Testing


Some companies usually interchange the term QA and QC, so many people think QA and QC are same and interchangeable but this is not true.
Both are tightly linked and sometimes it is very difficult to identify the differences.
Fact is both are related to each other but they are different in origins.

In my current project, QA is acting like Process QA. My role is automation QC, it is like Software QA which aims to identify and fix defects.

Typically , PQA will work with the whole software development team and audit how the team followed the process every sprint (2 weeks per sprint) , some specific projects will be audited quarterly.

Quality Assurance vs Quality Control

Quality Assurance Quality Control
It is a process which deliberate on providing assurance that quality request will be achieved. QC is a process which deliberates on fulfilling the quality request.
A QA aim is to prevent the defect. A QC aim is to identify and improve the defects.
QA is the technique of managing the quality. QC is method to verify the quality.
QA does not involve executing the program. QC always involves executing the program.
All team members are responsible for QA. Testing team is responsible for QC.
QA e.g. Verification. QC e.g. Validation.
QA means Planning for doing a process. QC Means Action for executing the planned process.
Statistical Technique used on QA is known as Statistical Process Control (SPC.) Statistical Technique used on QC is known as Statistical Quality Control (SPC.)
QA makes sure you are doing the right things. QC makes sure the results of what you’ve done are what you expected.
QA Defines standards and methodologies to followed in order to meet the customer requirements. QC ensures that the standards are followed while working on the product.
QA is the process to create the deliverables. QC is the process to verify that deliverables.
QA is responsible for full software development life cycle. QC is responsible for software testing life cycle.

Key Points

  • In QA, processes are planned to evade the defects.
  • QC agreements with discovery the defects and modifying them while making the product.
  • QA detects weakness.
  • QC detects defects.
  • QA is process oriented
  • QC is product oriented.
  • QA is failure prevention system.
  • QC is failure detection system.

Reference links:


Useful links to learn Automation (updating)

These are my favorite web sites:



Guru99 Java Tutorial for Beginners

Selenium WebDriver With Java – Novice To Ninja + Interview

Guru 99 Selenium Tutorials

Appium tutorial




Software QA Quotes

Below are my favorite quotes related to Software Quality Assurance. some of them are funny 🙂

  • “In God we trust, and for everything else we test.— this is my favorite one.

  • “Trust, But Verify”

  • “The only certainties in life are death, taxes and bugs in code”

  • “All code is guilty, until proven innocent”

  • “Life is too short for manual testing”

  • “No amount of testing can prove a software right, a single test can prove a software wrong.”— Amir Ghahrai

  • “To an optimist, the glass is half full. To a pessimist, the glass is half empty. To a good tester, the glass is twice as big as it needs to be.”

  • “The bitterness of poor quality remains long after the sweetness of meeting the schedule has been forgotten.”

  • “You can be a great tester if you have programming skills. You can also be a great tester if you have no programming skills at all. And, you can be a lousy tester with or without programming skills. A great tester will learn what skills she needs to continue to be great, in her own style.”— Jerry Weinberg

  • “More than the act of testing, the act of designing tests is one of the best bug preventers known. The thinking that must be done to create a useful test can discover and eliminate bugs before they are coded – indeed, test-design thinking can discover and eliminate bugs at every stage in the creation of software, from conception to specification, to design, coding and the rest.” – Boris Beizer

  • “You must be a constructive schizophrenic. Be clear about the difference between your role as a programmer and as a tester. The tester in you must be suspicious, uncompromising, hostile, and compulsively obsessed with destroying, utterly destroying, the programmer’s software. The tester in you is your Mr. Hyde – your Incredible Hulk. He must exercise what Gruenberger calls ‘low cunning.” – Boris Beizer

  • “The Definition of an Upgrade: Take old bugs out, put new ones in”

  • “Blame doesn’t fix bugs.”

  • “Fast, good, cheap: pick any two.”

  • “Lots of methodologies have come and gone, paradigms have changed but the requirements are always the same; Make it good and make it fast.”

  • “Discovering the unexpected is more important than confirming the known.“— George E. P. Box

  • “I do believe it’s important for testers to know the market that their client or their employer is in and the reason for that is if you understand what risks your client is facing and you understand what the competing products are and where the challenges lie in the market, you can plan your testing accordingly.”— Karen N. Johnson

  • “It’s not at all important to get it right the first time. It’s vitally important to get it right the last time.”— Andrew Hunt and David Thomas

  • “Walking on water and developing software from a specification are easy if both are frozen.”— Edward V. Berard

  • “Software and cathedrals are much the same: first we build them, then we pray.”

  • “Just like with everything else, tools won’t give you good results unless you know how, when, and why to apply them. If you go out and you buy the most expensive frying pan on the market it’s still not going to make you a good chef.”— Christin Wiedemann

  • “I remember the days when QA testers were treated almost as second-class citizens and developers ruled the software world. But as it recently occurred to me: we’re all testers now.” —Joe Colantonio

  • “Only conducting performance testing at the conclusion of system or functional testing is like conducting a diagnostic blood test on a patient who is already dead.”— Scott Barber