Types of Software Testing?
Types of Software Testing
1. Black Box Testing
2. White Box Testing
1- Black Box Testing-:
Black Box Testing in this type of Testing, Black box Testing without Knowledge of internal Part working of the code, or item. The Tester will be only know the valid input and Expected output should be. it is known as Black box Testing.
Example-:
Types of Black Box Testing-:
1- Functional Testing
2- Non- Functional Testing
3- Regression Testing
1-Functional Testing-:
Functional Testing is a Testing Technique it is Manual Testing or automation tool can be used Functional Testing.The Functional Testing Feature and functionality of the system of Software should be cover all the scenarios including failure path boundary cases.
Functional Testing Technique-:
1- Black box Testing Technique
2- White Box Testing Technique
Types of Functional Testing-:
There are many types of functional Testing
1- Unit Testing
2- Integration Testing
3- System Testing
4- User Acceptance Testing
5- Regression Testing
6- Smoke Testing
7- Sanity Testing
8- Black Box Testing
9- White Box Testing
2- Non Functional Testing-:
Non Functional Testing is a Testing Technique are should be performed after functional Testing.Non Functional Testing verifying performance of the application, using tool will be effective for this testing.Non functional requirement like performance, usability, load, factor are also requirement.
Types of Non Functional Testing-:
There are many types of Non Functional Testing
1- Performance Testing
2- Stress Testing
3- Load Testing
4- Spike Testing
5- Volume Testing
6- Security Testing
7- Installation Testing
8- Penetration Testing
9- compatibility Testing
9- Migration Testing
Black Box Design Testing Technique-:
1- Equivalence Partitioning/Equivalence Classes
2- Boundary Value Analysis(BVA)
3- Decision Table Testing
1- Equivalence Partitioning/Equivalence Classes-:
Data Factors-:
i- Type (Alpha bytes, Numeric , Alpha-Numeric, Alpha-Numeric and Special Characters).
ii- Size (10 digits Phone Number or any fixed Number).
iii- Range of Data (20 Years to 30 Years), (1 To 2 Years, 5 To 7 Years).
Example-: Data Range
Ticket Field in a Reservation System accepts 1 To 10 Tickets only.
Example-:Data Type
Customer Identification Number Field Accepts Only Number.
Example-: Data Size
Phone Number Field Accepts 10 digits Numeric Data Only.
Boundary Value Analysis(BVA)-:
Boundary Value Analysis is the Maximum and Minimum Value of a Partition are it's boundary
value. behavior at edge of each equivalence is more likely to be incorrect than behavior within
the partition.
Boundary Value Analysis can be applied at all level of testing.
like Unit Testing, Integration Testing, System Testing, User Acceptance Testing.
It is Test design Technique.
Related to equivalence Partitioning.
Example-:
Ticket Field in a Reservation System accepts 1 To 10 Tickets only.
BVA-:
1- Minimum/Maximum - 0 (Fail)
2- Minimum = 1
(Pass)
Maximum = 10
3- Minimum = 11
(Fail)
Maximum = 99
Decision Table Testing-:
Way to document.(Complicated) Logic and Help Test all Combination of Condition. Contain Condition And Action.
basically used the Test Scenario and Test Cases.
White Box Testing Tool-:
Software Testing Tools
The following tools can be used for automation testing:
1-Selenium
2-HP Quick Test Professional
3-IBM Rational Functional Tester
4-Silk Test
5-Test Complete
6-Testing Anywhere
7-Win Runner
8-Load Runner
9-Visual Studio Test Professional etc.
1. Black Box Testing
2. White Box Testing
Black Box Testing in this type of Testing, Black box Testing without Knowledge of internal Part working of the code, or item. The Tester will be only know the valid input and Expected output should be. it is known as Black box Testing.
Example-:
Types of Black Box Testing-:
1- Functional Testing
2- Non- Functional Testing
3- Regression Testing
1-Functional Testing-:
Functional Testing is a Testing Technique it is Manual Testing or automation tool can be used Functional Testing.The Functional Testing Feature and functionality of the system of Software should be cover all the scenarios including failure path boundary cases.
Functional Testing Technique-:
1- Black box Testing Technique
2- White Box Testing Technique
Types of Functional Testing-:
There are many types of functional Testing
1- Unit Testing
2- Integration Testing
3- System Testing
4- User Acceptance Testing
5- Regression Testing
6- Smoke Testing
7- Sanity Testing
8- Black Box Testing
9- White Box Testing
2- Non Functional Testing-:
Non Functional Testing is a Testing Technique are should be performed after functional Testing.Non Functional Testing verifying performance of the application, using tool will be effective for this testing.Non functional requirement like performance, usability, load, factor are also requirement.
Types of Non Functional Testing-:
There are many types of Non Functional Testing
1- Performance Testing
2- Stress Testing
3- Load Testing
4- Spike Testing
5- Volume Testing
6- Security Testing
7- Installation Testing
8- Penetration Testing
9- compatibility Testing
9- Migration Testing
Black Box Design Testing Technique-:
1- Equivalence Partitioning/Equivalence Classes
2- Boundary Value Analysis(BVA)
3- Decision Table Testing
1- Equivalence Partitioning/Equivalence Classes-:
Equivalence Partitioning/Equivalence Classes can be found for both valid data and invalid data.
In Equivalence Partitioning,input to the software are divided into group that are
expect exhibit similar behavior. it can be apply any level of Testing.
Data Factors-:
i- Type (Alpha bytes, Numeric , Alpha-Numeric, Alpha-Numeric and Special Characters).
ii- Size (10 digits Phone Number or any fixed Number).
iii- Range of Data (20 Years to 30 Years), (1 To 2 Years, 5 To 7 Years).
Example-: Data Range
Ticket Field in a Reservation System accepts 1 To 10 Tickets only.
Example-:Data Type
Customer Identification Number Field Accepts Only Number.
Example-: Data Size
Phone Number Field Accepts 10 digits Numeric Data Only.
Boundary Value Analysis(BVA)-:
Boundary Value Analysis is the Maximum and Minimum Value of a Partition are it's boundary
value. behavior at edge of each equivalence is more likely to be incorrect than behavior within
the partition.
Boundary Value Analysis can be applied at all level of testing.
like Unit Testing, Integration Testing, System Testing, User Acceptance Testing.
It is Test design Technique.
Related to equivalence Partitioning.
Example-:
Ticket Field in a Reservation System accepts 1 To 10 Tickets only.
BVA-:
1- Minimum/Maximum - 0 (Fail)
2- Minimum = 1
(Pass)
Maximum = 10
3- Minimum = 11
(Fail)
Maximum = 99
Decision Table Testing-:
Way to document.(Complicated) Logic and Help Test all Combination of Condition. Contain Condition And Action.
basically used the Test Scenario and Test Cases.
White Box Testing Tool-:
Software Testing Tools
The following tools can be used for automation testing:
1-Selenium
2-HP Quick Test Professional
3-IBM Rational Functional Tester
4-Silk Test
5-Test Complete
6-Testing Anywhere
7-Win Runner
8-Load Runner
9-Visual Studio Test Professional etc.
What is Bug Life Cycle or Defect Life Cycle?
Step By Step defined as bug life cycle-:
1. New-:
When a new bug or defect are logged and Posted for the first time. it is assigned a status New. it is known as New.
2.Assigned-:
The bug is posted by the tester, the lead of the tester approves the bug and assigns the bug to developed team. it known as Assigned.
3.Open-:
The developer start analyzing or find the error, and work on the bug fix.
4.Fixed-:
When the developer make or find error, necessary code change and verifies the change.the status is fixed.
5.Pending Retest-:
Once the defect or bug is fixed the developer gives particular code for retesting the code to the tester.so since the testing remains pending from the tester end, the status is assigned is pending retest.
it is known as pending retest.
6.Retest-:
The Tester does the resting of the code or functionality at this stage to check whether is fixed by the developer. and change the status is Retest.
7.Verified-:
The Tester retest the bug or defect after it got fixed by the developer. if there are no bug or defect in the software, application then bug or defect is fixed and the status assigned is verified.
8.Reopen-:
Reopen that means if the bug persist's even after the developer has fixed the bug or defect, once again the bug goes through the life cycle. the tester change the status to reopened.
9.Closed-:
Closed that means, if the bug or defect is no longer exits then tester assign.and change the status is Closed.
10.Duplicate-:
If the Defect or bug is repeated twice or bug corresponds the same concept of the bug.So status is changed to duplicate.
11.Rejected-:
If the developer feel the bug or defect is not a genuine bug, then change the bug to Rejected.
12.Deferred-:
Deferred that means if the bug or defect is not a prime priority, if it is expected to get fixed in the next release, then status is deferred.
13.Not a bug-:
If it does not effect the functionality of the Application or Software. Then the status is Not a bug.
nice Abhay keep continue
ReplyDeleteThank you very much for appreciate bhaiya
Delete