1. Software Testing
Prasad G

2. The Software Development Life Cycle
Software Requirement Specification
Requirement Analysis
Design
Coding
Testing
Implementation
Design Specification
Test Strategy
Test Plan
Prasad G

3. Understanding Testing
Analyzing
Review
Verifying
Validating
Testing
Manual
Automated

4. Determine specified Requirements are met
Testing Objectives
Testing activity is performed to find defects in the software
Detect Defects
Testing activity is performed to check if the software meets the specified requirements
Determine specified Requirements are met
Testing activity is performed to test the performance of the application.
Test the Performance

5. Testing Principles Testing shows presence of defects
Exhaustive testing is impossible
Early Testing
Defect Clustering
Pesticide paradox
Testing is context dependent
Absence of errors fallacy

6. Software Testing Life Cycle
Test Planning
Testing Objectives are defined
Test Case designing
Identifying the Test Data
Identifying the environment, Infrastructure and Tools
Test Analysis and Design
Test Executing
Test Results
Logging Defects
Re-testing
Test Implementation and Execution
Verify if more testing is required
Test Summary Report
Evaluating Exit Criteria and Reporting
Test Closure Activities
Test Archive

7. Non Functional Testing
Test Types
Test Type
Functional Testing
Non Functional Testing
Confirmation Testing
Regression Testing
Testing the functionality against the software
Testing the behavioral characteristic of the software
Retesting
No new defects are introduced in the process of fixing the earlier identified defects
Black Box

8. Test Plan Test Plan Test Plan describes
Scope
Approach
Resources
Schedule
Test Plan describes
Assign mitigation and contingencies to the identified risks
Decide scope of testing according to level of risk
Features to be tested
Features not to be tested
Tasks to be performed
The environment in which testing is to be done
Test Schedule
Test Execution

9. Test Case = Actual Result Expected Output
A test case is a document that contains detailed instructions for testing the functionality of a software application
A Robust Test case should be
Independent to meet specific requirements
Easily understandable during testing
Free from spelling and grammatical mistakes.
Able to cover at least one functionality or requirement
Able to uncover bugs
Test Components
Test Case Name
Objectives
Test Case ID
Prerequisites
Actions
Expected Result
Actual Result
Status
General Remarks

10. Equivalence partitioning Boundary Value Analysis
Black Box Test Design Technique
Equivalence partitioning
Represents a set of valid and invalid conditions
Test condition which give similar results are grouped under one partition
Number of test cases is reduced considerably
Boundary Value Analysis
Identifies bugs around the boundaries.
Takes into account output specifications when deriving test cases
Used to test the behavior of the application where the bug is most likely to occur
Error Guessing
ADHOC method to identify tests that are likely to expose bugs.
Enables to make guess about bugs that are likely to be present in the application
Test Activities based on areas that are not covered by formal design techniques.
State Transition
Enables you to test the transition from one state to another
Identifies the events which causes the transition and specifies Actions that result from the transition
Syntax Testing
Used to design test cases for software applications based on the syntax of the input.
Test the application with different set of input values
Cause effect Graphic
Used to identify possible causes of a problem by using the cause effect diagram
Analyze Cause of the problem
Identify the source of bugs and Observe the effects of the problem.

11. Execute a Test Case Test Log Pass Fail Blocked Attributes of Test Log
Test log identifier
Test Description
Test Case ID
Execution Description
Actual Result
Status
Environmental Information
Anomalous Events
Incident Identifier
Name of Tester
Date of testing
General Comments

12. Test Summary Report Parameters of Report
Number of Modules tested
Number of test cases passed or failed
Number of bugs identified
Precondition of Test Summary Report
Test Log to be completed
Testing activities should to be completed
Testing execution should be completed
Benefits of Test Summary Report
Effectiveness of testing effort
Quality of application
Test Coverage
Decide any change
Reference to lessons learned

13. New
Open
Assigned
Resolved
Verified
Closed
Defect
Defects are events that occurred during text execution and require investigation.
Defect Report
Defect ID
Defect Summary
Actual Result
Expected Result
Date and Time
Supporting Evidence
Potential Impact (Severity & Priority)
Found By
Assigned To
Status
Defer
Reopen
Reject

14. Test Tools Functional Testing Tools Used mainly for regression testing
Software Requirement Specifications
Software Functionality
Used mainly for regression testing
E.g. QTP, Winrunner
Load
Performance Testing Tools
Speed
Effectiveness
Stress
Features of Performance Test Tool
Generating Load
Measuring timing of transactions
Measuring average response time
Creating graphs and charts
E.g. Load Runner,

15. Test Management Tool Test Case Management Test Schedule
Requirement Analysis
Design
Coding
Testing
Implementation
Test Case Management
Test Schedule
Managing Test effort
Traceability
Test report
Defect Management
Test Management Tool
E.g. HP Quality Center

16. For any QA training and support related discussion, mail me at easylearn9@gmail.com