Sunday 2 June 2013

QA – Introduction To Testing

Leave a Comment


QA – Introduction To Testing
Let’s get started

You would be able to learn the following, at the end of this chapter

o   What are the advantages of Testing?
o   How do we Test?
o   Who are needed Testing?
o   What is a Defect / Bug?
o   Explain in detail about Testing Process

Introduction to Testing

o     Testing is the process of executing a program with the intention of finding errors
o     Testing is the process of verifying an application to check if the application is behaving as per the requirements / specifications.
o     Testing is the process of executing test cases on the application to differentiate between expected and actual results.
o     Testing is the process of V and V ( Verification and Validation)
o     Testing is obviously concerned with finding bugs, defects, errors, faults, failures and incidents with the applications.
o     Testing is the process of verifying customers’ needs with respect of the designed software/application
o     Testing is the combined process of Analyzing / Understanding the Reqs, Designing  Test Cases, Executing Test Cases, Reporting Test Status, Supporting Application



You can learn the following:



Let’s go on… 

What is Software

o   Software is a set of programs
o   Software represents the process of transforming BRS into FRS , FRS into SRS and SRS into Application
o   Software is the designed application or program that resembles the customer requirements

What is a Program
o   Program is a set of instructions that performs some action



Why do we need Testing : 

§  For Customer Satisfaction
§  To give a QUALITY  Project to Customer
§  > Bug Free
§  > On Time
§  > Process Followed
§  Dev team thinks in point of code, loops, conditions (Structural testing)
§  There should be someone else to Validate the App (Tester, QA)
§  Tester is a mediator between Dev and Customer
§  Tester thinks in point of Customer
o   External Focus
o   Functional Tests
o   No Code at all
§  Tester thinks in point of Functional approach


o   Benefits of Testing.
o   Consistent and Accurate Quality of Software / Project
o   Cost Effective and Efficient Process
o   Reduces Overall Development Cycle Time
o   Process Oriented
o   Gain Customer Satisfaction
o   Retains company’s name and fame


Why does software have defects in it.. : 
o   Poor Requirements (Unclear Reqs)
o   Programming errors
o   Software complexity
o   Changes in Requirements
o   Time pressure
o   Inefficient Dev (Poorly coded modules)
o   Poor Management
o   Poor Documentation
o   Poor Quality Assurance
o   Other reasons



When do we start Testing :

          Right from the beginning of the Requirements
          Reqs / BRS / SRS / Use Cases / wire frames are clear / understandable / testable / transformable into application
          When Test Plan, Test Cases , Test Environment is ready
         When Application is ready , stable and is in our QA hands







When do we stop Testing :

          Reqs / BRS / SRS / Use Cases / wire frames are covered in the Application and are working fine
          Application is bug free
          When Quality Indicators, QA Metrics represent the  100% quality of the application
          Application is handed over / delivered to Client/ Customer
          Maintenance / Support is successful






Who are needed for Testing :

          Developers (White Box testing > Unit Testing , Integration Testing)
          Clients / Customers (Grey Box Testing  > Code , Functional , UAT)
          Testers (Black Box Testing > Smoke , Functional, Integration , System , Regression Testing)
          Users (Functional , UI Testing)
          Tester is the right MAN of all to validate Application.

Developers point of view:
·         Does my code work??
·         Are my code loops, conditions, functions … working good??
·         Understands the system but, will test "gently”
·         and, is driven by "delivery"

Testers Point of view:
·         Does the application work well?
·         Are the requirements covered in the application?
·         Must learn about the system,
·         but, will attempt to break it
·         and, is driven by quality

What are needed for Testing :

·         Requirements/ Specifications / wire frames
·         Good understanding of BRS/SRS/ wire frames
·         QATP (Test Plan), QATC (Test cases)
·         Test Set up (Environment, Software & Tools)
·         Resources (Machines, Testers, Lab)
·         Application, Integration Tools, etc


How do we Testing:
·         We Test the applications / software in two ways
·         Manual Testing
·         Automation Testing



Manual Testing:

         Sanity Testing
         Functional Testing
         Integration Testing
         System Testing
         UI Testing
         Regression Testing
         Bug Verification / Bug Tracking
         Compatibility Testing
         UAT ( Alpha and Beta)

Automation Testing:

         Sanity Testing
         Functional Testing
         Regression Testing
         Load Testing
         Performance  Testing
         Stress Testing















0 comments:

Post a Comment

Sunday 2 June 2013

QA – Introduction To Testing



QA – Introduction To Testing
Let’s get started

You would be able to learn the following, at the end of this chapter

o   What are the advantages of Testing?
o   How do we Test?
o   Who are needed Testing?
o   What is a Defect / Bug?
o   Explain in detail about Testing Process

Introduction to Testing

o     Testing is the process of executing a program with the intention of finding errors
o     Testing is the process of verifying an application to check if the application is behaving as per the requirements / specifications.
o     Testing is the process of executing test cases on the application to differentiate between expected and actual results.
o     Testing is the process of V and V ( Verification and Validation)
o     Testing is obviously concerned with finding bugs, defects, errors, faults, failures and incidents with the applications.
o     Testing is the process of verifying customers’ needs with respect of the designed software/application
o     Testing is the combined process of Analyzing / Understanding the Reqs, Designing  Test Cases, Executing Test Cases, Reporting Test Status, Supporting Application



You can learn the following:



Let’s go on… 

What is Software

o   Software is a set of programs
o   Software represents the process of transforming BRS into FRS , FRS into SRS and SRS into Application
o   Software is the designed application or program that resembles the customer requirements

What is a Program
o   Program is a set of instructions that performs some action



Why do we need Testing : 

§  For Customer Satisfaction
§  To give a QUALITY  Project to Customer
§  > Bug Free
§  > On Time
§  > Process Followed
§  Dev team thinks in point of code, loops, conditions (Structural testing)
§  There should be someone else to Validate the App (Tester, QA)
§  Tester is a mediator between Dev and Customer
§  Tester thinks in point of Customer
o   External Focus
o   Functional Tests
o   No Code at all
§  Tester thinks in point of Functional approach


o   Benefits of Testing.
o   Consistent and Accurate Quality of Software / Project
o   Cost Effective and Efficient Process
o   Reduces Overall Development Cycle Time
o   Process Oriented
o   Gain Customer Satisfaction
o   Retains company’s name and fame


Why does software have defects in it.. : 
o   Poor Requirements (Unclear Reqs)
o   Programming errors
o   Software complexity
o   Changes in Requirements
o   Time pressure
o   Inefficient Dev (Poorly coded modules)
o   Poor Management
o   Poor Documentation
o   Poor Quality Assurance
o   Other reasons



When do we start Testing :

          Right from the beginning of the Requirements
          Reqs / BRS / SRS / Use Cases / wire frames are clear / understandable / testable / transformable into application
          When Test Plan, Test Cases , Test Environment is ready
         When Application is ready , stable and is in our QA hands







When do we stop Testing :

          Reqs / BRS / SRS / Use Cases / wire frames are covered in the Application and are working fine
          Application is bug free
          When Quality Indicators, QA Metrics represent the  100% quality of the application
          Application is handed over / delivered to Client/ Customer
          Maintenance / Support is successful






Who are needed for Testing :

          Developers (White Box testing > Unit Testing , Integration Testing)
          Clients / Customers (Grey Box Testing  > Code , Functional , UAT)
          Testers (Black Box Testing > Smoke , Functional, Integration , System , Regression Testing)
          Users (Functional , UI Testing)
          Tester is the right MAN of all to validate Application.

Developers point of view:
·         Does my code work??
·         Are my code loops, conditions, functions … working good??
·         Understands the system but, will test "gently”
·         and, is driven by "delivery"

Testers Point of view:
·         Does the application work well?
·         Are the requirements covered in the application?
·         Must learn about the system,
·         but, will attempt to break it
·         and, is driven by quality

What are needed for Testing :

·         Requirements/ Specifications / wire frames
·         Good understanding of BRS/SRS/ wire frames
·         QATP (Test Plan), QATC (Test cases)
·         Test Set up (Environment, Software & Tools)
·         Resources (Machines, Testers, Lab)
·         Application, Integration Tools, etc


How do we Testing:
·         We Test the applications / software in two ways
·         Manual Testing
·         Automation Testing



Manual Testing:

         Sanity Testing
         Functional Testing
         Integration Testing
         System Testing
         UI Testing
         Regression Testing
         Bug Verification / Bug Tracking
         Compatibility Testing
         UAT ( Alpha and Beta)

Automation Testing:

         Sanity Testing
         Functional Testing
         Regression Testing
         Load Testing
         Performance  Testing
         Stress Testing















No comments:

Post a Comment