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
| |||||||||||
Posts
