Difference between QA and QC and Software Testing

Quality Assurance  1. QA is process related
2. QA focuses on building in quality and hence preventing defects
3. QA: Deals with process
4. QA: for entire life cycle
5. Quality Assurance makes sure you are doing the right things, the right way.
6. QA is preventive process.
Quality Control
1. QC is the actual testing of the software
2. QC focuses on testing for quality and hence detecting defects
3. QC: Deals with product
4. QC: for testing part in SDLC
5. Quality Control makes sure the results of what you've done are what you expected
6. QC is corrective process.
Testing
1.The process of executing a system with the intent of finding defects
2.Software testing is a planned process that is used to identify the correctness, completeness, security and quality of software.
3.Testing is generally done to demonstrate that the software is doing what it is supposed to do as well as the software is not doing what it is not supposed to do.
4.The goal of testing or software tester is to locate defects and make sure that they get fixed.

Error Guessing

• Why can one Tester find more errors than another Tester in the same piece of software?
• More often than not this is down to a technique called ‘Error Guessing’. To be successful at Error Guessing, a certain level of knowledge and experience is required. A Tester can then make an educated guess at where potential problems may arise. This could be based on the Testers experience with a previous iteration of the software, or just a level of knowledge in that area of technology. This test case design technique can be very effective at pin-pointing potential problem areas in software. It is often be used by creating a list of potential problem areas/scenarios, then producing a set of test cases from it. This approach can often find errors that would otherwise be missed by a more structured testing approach.
• An example of how to use the ‘Error Guessing’ method would be to imagine you had a software program that accepted a ten digit customer code. The software was
  designed to only accept numerical data.
  
  Here are some example test case ideas that could be considered as Error Guessing:
  1. Input of a blank entry
  2. Input of greater than ten digits
  3. Input of mixture of numbers and letters
  4. Input of identical customer codes
  
  

#KvEjwpLK7F#

Ad-hoc Testing or Informal Testing

• In general, every testing team conducts planned testing, but testing team adopts informal testing sometimes due to some challenges or risks.
• E.g : Lack of time, lack of resources, lack of team size, lack of skill, etc.
• There are different ways of Ad-hoc testing.
  Ways of Adhoc Testing
• Monkey Testing
  Due to lack of time, the testing team concentrates on some of the main activities in the software build for testing. This style of testing is known as “Monkey testing” or “Chimpanzee testing” or “Gorilla testing”.
• Buddy Testing
  Due to lack of time, the management groups programmers & testers as “Buddies”. Every buddy group consists of programmers & testers.
  E.g.: 1:1 (or) 2:1 (or) 3:1 (preferable)
• Exploratory Testing
  Due to lack of proper documentation of the software being built, the test engineers depend on past experience, discuss with others, browse the Internet or Operate similar projects and contact customer side people if possible. This style of testing is called “Exploratory Testing”.
• Pair Testing
  Due to lack of knowledge on project domain the management groups a senior tester & a Junior Programmers and conducted testing, these all are called Pair testing.
• Defect Seeding
  To estimate the efficiency of test engineers, the programmers add some bugs to the build. This task is called defect seeding / debugging.

How to create a Test Plan without docs?

1. Try to break up your huge application into modules that are functionally independent.
2. Within each module you start with the functions one by one.
3. For a simple function write all possible test cases that arise to be tested, while using the application as there are no specs.
4. In this way you could complete one function and in turn whole application.
5. To prepare test cases or plan make use of Excel sheet. Each sheet will define each function within the module. This is best way to organize the test cases. 

Priority and severity

1) Severity is the seriousness of the problem.
2) Priority is the urgency of fixing a problem.
Examples of Severity and Priority
• High severity and high priority
  System crashes in Log-in Page
• High severity and Low priority
  System crashes on clicking a button. The page on which the button is located is part of next release.
• Low severity and high priority
  Spelling mistake in any company name web site.
• Low severity and Low priority
  Location of button in any web based application

#rgAliZ#

Defect life cycle

• New : Tester found new bug and report it to test lead.
• Open : Test lead open this bug and assign it to the developer.
• Assign : Developer has three choices after assigning the bug.
• Reject :He can say that this is not a bug because of some hardware or other problems you might getting defect in application..
• Differed : He can postpone bug fixing according to priority of bug.
• Duplicate : If the bug is repeated twice or the two bugs mention the same concept of the bug, then one bug status is changed to “DUPLICATE”.
• Fixed : If there are no such conditions like reject, duplicate the developer has to fix the bug.
• Testing : Test the whole application to find the defects if the defect is still there they will re-open the bug and if bug is not there it will move to verify.
• Re-open : If defect raised during testing we re-open bug.
• Verify : Retest whole application.
• Close : Close the application.   

#uPUJOTBonP#