Software Testing - Cheatsheet
05BC1502 - Software Testing
---------------------------------------------------------------------------------------------------------------
UNIT: 1
---------------------------------------------------------------------------------------------------------------
Testing : It is a process to evaluate product for any kind of defects
Errors : It’s a quality problem in software , generally identify before software deliver to client.
Defects : It’s a quality problem of software, generally identify by users after deliver it.
------------------------------------------------------------------------------------------------------------------
How do industries measure their testing process?
- CMM (Capability Maturity Model)
- TMM (Testing Maturity Model )
------------------------------------------------------------------------------------------------------------------
Define Term : Software Testing
-Testing is the process of executing a program with the intent of finding errors.
-Software testing is a process that detects important bugs with the objective of having better quality software.
------------------------------------------------------------------------------------------------------------------
Goals of Software Testing
------------------------------------------------------------------------------------------------------------------
Software Testing Terminology
1) Failure :
A failure is the inability of a software system or component to perform its required functions within specified performance requirements.
2) Fault/Defect/Bug :
Fault is a condition that in actual causes a system to produce failure. Fault is synonymous with the words defect or bug.
3)Error :
Refers to difference between Actual Output and Expected output
“A mistake in coding is called Error, error found by tester is called Defect, defect accepted by development team then it is called Bug, build does not meet the requirements then it Is Failure.”
4)Test case :
Test case is a well-documented procedure designed to test the functionality of a feature in the system.
5) Testware :
The documents created during testing activities are known as testware.
6) Incident :
When a failure occurs, it may or may not be readily apparent / visible to the user.
7)Test oracle :
An oracle is the means to judge the success or failure of a test
------------------------------------------------------------------------------------------------------------------
Life Cycle of Bug
- It should be clear that any member of the development team can make an error in any phase of SDLC.
- then it becomes a bug. In this way, errors and bugs appear and travel through various stages of SDLC, as shown in Fig.
- The whole life cycle of a bug can be classified into two phases
(i) bugs-in phase (ii) bugs-out phase.
1)Bugs-In Phase:
- This phase is where the errors and bugs are introduced in the software
2)Bugs-Out Phase:
- If failures occur while testing a software product, we come to the conclusion that it is affected by bugs.
i)Bug classification (we observe the failure and classify the bugs)
ii)Bug isolation (we locate the module in which the bug appears)
iii)Bug resolution (we back-trace the design to pinpoint the location of the error)
------------------------------------------------------------------------------------------------------------------
States of Bug
------------------------------------------------------------------------------------------------------------------
Bugs Classification based on criticality
- Bugs can be classified based on the impact they have on the software under test.
1) Critical Bugs (This type of bugs has the worst effect such that it stops or hangs the normal functioning of the software)
2) Major Bug (A functionality to fail to meet its requirements as expected)
3)Medium Bugs (outputs are not according to the standards or conventions)
4)Minor Bugs (just mild bugs which occur without any effect on the expected behaviour or continuity of the software)
------------------------------------------------------------------------------------------------------------------
Bugs Classification based on SDLC
-Bugs can appear in any phase of SDLC, they can be classified based on SDLC phases which are described below :
- Requirements and Specifications Bugs
- Design Bugs
Control flow bugs , Logic bugs , Processing bugs , Data flow bugs
Error handling bugs , Race condition bugs
Boundary-related bugs
User interface bugs
- Coding Bugs
- Interface and Integration Bugs
- System Bugs
- Testing Bugs
------------------------------------------------------------------------------------------------------------------
Testing Principles
1) Effective testing, not exhaustive testing
2) Testing is not a single phase performed in SDLC
3) Destructive approach for constructive testing
4) Early testing is the best policy
5) Probability of existence of an error in a section of a program is proportional to the number of errors already found in that section.
6) Testing strategy should start at the smallest module level and expand towards the whole program
7) Testing should also be performed by an independent team
8) Everything must be recorded in software testing
9) Invalid inputs and unexpected behaviour have a high probability of finding an error
10) Testers must participate in specification and design reviews
------------------------------------------------------------------------------------------------------------------
Software Testing Life Cycle (STLC)
Verification and Validation Activities
------------------------------------------------------------------------------------------------------------------
Comments
Post a Comment