Date post: | 22-Dec-2015 |
Category: |
Documents |
Upload: | christal-hines |
View: | 226 times |
Download: | 2 times |
The Software Development Life Cycle
Software Requirement Specification
Design Specification
Test Strategy Test Plan
Understanding Testing
Testing
Analyzing
Review
Verifying
Validating
Testing
Manual Automated
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
Software Testing Life Cycle
Test Planning
Test Analysis and Design
Test Implementation and Execution
Evaluating Exit Criteria and Reporting
Test Closure Activities
Testing Objectives are defined
Test Case designing Identifying the Test Data Identifying the environment,
Infrastructure and Tools
Test Executing Test Results Logging Defects Re-testing
Verify if more testing is required Test Summary Report
Test Archive
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
Test Plan
Test Plan describesAssign mitigation and contingencies to the identified risksDecide scope of testing according to level of riskFeatures to be testedFeatures not to be testedTasks to be performedThe environment in which testing is to be doneTest ScheduleTest Execution
Test Plan
Scope ResourcesApproach Schedule
Test Case
Expected Output Actual Result=
A test case is a document that contains detailed instructions for testing the functionality of a software application
A Robust Test case should beIndependent to meet specific requirementsEasily understandable during testingFree from spelling and grammatical mistakes.Able to cover at least one functionality or requirementAble to uncover bugs
Test Components Test Case Name Objectives Test Case ID
Prerequisites Actions Expected Result
Actual Result Status General Remarks
Black Box Test Design Technique
Boundary Value Analysis
Equivalence partitioning
Error Guessing
State Transition
Syntax Testing
Cause effect Graphic
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
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
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.
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
Used to design test cases for software applications based on the syntax of the input. Test the application with different set of input values
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.
Execute a Test Case
Test Log
Pass BlockedFail
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
Test Summary ReportParameters of Report
Number of Modules testedNumber of test cases passed or failedNumber of bugs identified
Precondition of Test Summary Report
Test Log to be completedTesting activities should to be completedTesting execution should be completed
Benefits of Test Summary Report
Effectiveness of testing effortQuality of applicationTest CoverageDecide any changeReference to lessons learned
DefectDefects are events that occurred during text execution and require investigation.
Defer
Reject
ReopenDefect Report
Defect IDDefect SummaryActual ResultExpected ResultDate and TimeSupporting EvidencePotential Impact (Severity & Priority)Found ByAssigned ToStatus
Test Tools
Functional Testing Tools
Software Functionality
Software Requirement Specifications
Used mainly for regression testing
Performance Testing Tools
Speed Effectiveness
Load
Stress
Features of Performance Test ToolGenerating LoadMeasuring timing of transactionsMeasuring average response timeCreating graphs and charts
E.g. QTP, Winrunner
E.g. Load Runner,
Test Management Tool
Test Management
Tool
Test Case Management
Test Schedule
Managing Test effort
Traceability
Test report
Defect Management
E.g. HP Quality Center