2. What is a software? Computer Software, or just Software, is the collection of computer programs and related data that provide the instructions telling a computer what has to be done. What is Testing? Testing is a stage where the programmer can detect or check any errors in his/her program had made. its main purpose is to look for errors and not only to see if the program is working correctly.

3. What is software testing Software testing can be stated as the process of validating and verifying that a software program/application/product: meets the business and technical requirements that guided its design and development; works as expected; and can be implemented with the same characteristics.

4. Process of executing a program or system with the intent of finding errors. To deduct software failures Evaluating an attribute or capability of a program or system and determining that it meets its required results. Scope of Software Testing:  Examination of code (does it to)  Execution of that code in various environments and conditions (what it is supposed to do)  Examining the aspects of code (do what it needs to do).

5. Limitations of Software Testing Every method use to find bugs leaves a residue of subtler bugs.(ineffectual) Software Complexity grows to the limits of our ability to manage that complexity. E.g. Testing a simple program to add only two integer inputs of 32-bits (yielding 2^64 distinct test cases) would take hundreds of years, even if tests were performed at a rate of thousands per second. Complete testing is infeasible(possible values can be tested and verified). Eliminating previous bugs allowed another escalation of features and complexity.

6. Testing Terminology  Quality  Verification  Validation  Errors  Defect  Defect Vs Failures  Bug

7. Quality software quality measures how well software is designed (quality of design), and how well the software conforms to that design (quality of conformance) Quality is meeting the requirements expected of the software, consistently and predictably

8. Verification Have we built the software right? (i.e., does it match the specification). It is also a process of evaluating a system or component to determine whether the products of a given phase satisfy the conditions imposed at the start of that phase.

9. Validation Validation: Have we built the right software? (i.e., is this what the customer wants). It is a process of evaluating a system or a component during or at the end of the development process to determine whether it satisfies specified requirements.

10. Error, Defect, Failure and bug Error: Any mistake in a program called error. Defect: Mistakes found by tester during system testing called defect. Failure: Executing defect code, sometimes will produce wrong results, causes failure. Bug: Reported defect is accepted by developer to resolve called bug.

11. A software bug is the common term used to describe an error, flaw, mistake, failure, or fault in a computer program or system that produces an incorrect or unexpected result, or causes it to behave in unintended ways. Most bugs arise from mistakes and errors made by people in either a program's source code or its design, and a few are caused by compilers producing incorrect code. A program that contains a large number of bugs, and/or bugs that seriously interfere with its functionality, is said to be buggy

12. Testing Process

13. Organize Project involves creating a System Test Plan, Schedule & Test Approach, and requesting/assigning resources. Design/Build System Test involves identifying Test Cycles, Test Cases, Entrance & Exit Criteria, Expected Results, etc. In general, test conditions/expected results will be identified by the Test Team in conjunction with the Project Business Analyst or Business Expert. The Test Team will then identify Test Cases and the Data required. The Test conditions are derived from the Business Design and the Transaction Requirements Documents Design/Build Test Procedures includes setting up procedures such as Error Management systems and Status reporting, and setting up the data tables for the Automated Testing Tool

14. . Build Test Environment includes requesting/building hardware, software and data set-ups. Execute Project Integration Test - See Section 3 - Test Phases & Cycles Execute Operations Acceptance Test - See Section 3 - Test Phases & Cycles Signoff - Signoff happens when all pre-defined exit criteria have been achieved

15. Software Testing Life Cycle PhasesActivitiesOutcome Planning Create high level test plan Test plan, Refined Specification Analysis Create detailed test plan, Functional Validation Matrix, test cases Revised Test Plan, Functional validation matrix, test cases Designs test cases are revised; select which test cases to automate Revised test cases, test data sets, sets, risk assessment sheet Construction Scripting of test cases to automate, Test procedures/Scripts, Drivers, test results, Bug reports. Testing cycle Complete testing cyclesTest results, Bug Reports Final testing Execute remaining stress and performance tests, complete documentation Test results and different metrics on test efforts Post implementation Evaluate testing processes Plan for improvement of testing process

16. Testing embedded in SDLC Sequential Iterative RAD( rapid application Development)