![](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjrmqpTNEhcliTYidf5DYsBZM4HzAahClMxe1L6ep48a7bxuke-7c5XNgaahFIuLVFVmqRyuQLUJXt7Oqi_0kFfVNUd1smzUkhAIiNKbjRp0AI-FsDLVkgjnwifhn_lq_4xJvm4FGV4bWk/s400/integrationtesting.jpg)
NOTE : CLICK ON IMAGES FOR LARGE VIEW.
LEVELS OF TESTING
I) UNIT TESTING
In this phase, the programmers check the internal logic of each program structured by using White Box Techniques (WBT) techniques.
II) INTEGRATION TESTING
After Unit testing, the programmers integrate all the individual modules to make it has a complete software or Application.
They are following below approaches to integrate all the modules that are completed.
TOP-DOWN APPROACH
![](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiivogFSuPXGE7RehIpEWX9fqADSypeiAWvY4D5VYcQADJjocnuE6zpLDcmqyn4DJyjrIyCL0Dz__pJlQ3FsSEQKlVjZojhI8RcU2BN7NDqVTZR4oDj8zfCMKxMch29n-CxabJuwbs_lk4/s400/untitled.jpg)
In this approach testing is conducted from main module to sub module. if the sub module is not developed a temporary program called STUB is used for simulate the sub module. STUB is also known as CALLED program.
BOTTOM-UP APPROACH
![](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgQh0XOksYmMl7QH_uGHGsqEd4v7lXIAkhZ_WX4B4KkbhPWAuCRBO8WzoXwMH2Tbvl4cOzlhyphenhyphen8b6AxVS1A8P4G-ElGgDXyqjJxORNybxZ7VP2FaAMCPRcnNZZB6zAAqLNwOUN7nb8qIhXA/s400/Top+down+approach.jpg)
In this approach testing is conducted from sub module to main module, if the main module is not developed a temporary program called DRIVERS is used to simulate the main module. This Driver is also known as CALLING program.
BI-DIRECTIONAL (Or) SANDWICH (Or) HYBRID APPROACH
Combination of Top down and Bottom up Approach.
SYSTEM APPROACH (Or) BIG-BANG THEORY
Grouping all the main and sub modules to make it as complete software or Application.
III) SYSTEM TESTING:
After Integration testing the developers delivers the Software build to the testers to detect the defects. Such a Software build is called as “AUT”.
AUT APPLICATION UNDER TEST.
Then the test engineers apply system testing on AUT in 3-ways:
1. USABILITY TESTING
2. FUNCTIONAL TESTING
3. NON- FUNCTIOANL TESTING
USABILITY TESTING
1. USER INTERFACE TESTING Or COSMETIC TESTING
2. MANUAL SUPPORT
USER INTERFACE TESTING Look & Feel (Attractiveness)
Easy to Use (Understandable)
Speed in Interface (Short Navigation)
The purpose of Functional & Non Functional Testing is to check the
Requirements
Correctness
Completeness
After completion of User Interface Testing on every screen of our application. The test engineers concentrate on requirements, Correctness and Completeness by using BBT (Black Box Testing) techniques.
WHAT IS BBT TECHNIQUES?
1. Boundary Value Analysis (BVA)
2. Equivalence Class Partition(ECP)
3. Error Guessing
4. Decision Table
5. State Transition Diagram
Functional Test is done in 2 – ways:
1. Functionality Testing
2. Sanitation Testing
Functionality Testing:
In general test engineers start functional testing with functionality testing by following below approaches.
1. GUI Coverage/ Behavioral Coverage
The Valid Changes in the properties of objects in a window.
2. Error handling
The Prevention of wrong operations with meaningful errors.
3. Input Domain Coverage
The range & type of input in terms of VALID/INVALID
4. Manipulation Coverage
The Correctness of existing output.
5. Order of Functionality – Eg) TAB BUTTON
The Correctness of existing order with respect to customer requirement.
6. Database Coverage/Backend Coverage
The impact of front end screen operations on backend table content.
SANITATION TESTING
During this testing, the testers are finding extra functionalities which are not in customers specifications/BRS.
This Testing is also called as “GARBAGE TESTING”
Eg)
User Name Field
Password Field
Ok button Submit button
In the above example, there is no need of extra button called Submit or OK..
NON – FUNCTIONAL TESTING:
After completing of functional testing, the test engineers concentrate on Non-Functional testing. It is also an important testing phase in system testing.
But, It is very complex to conduct and it is expensive.
1. Platform Independent
2. Reliable/Scalability.
3. Compatibility/Portability.
4. Installation/Uninstallation.
5. Data Volume(Storage Testing)
6. Performance -> Load (How many concurrent users are using) Stress, Efficiency.
7. Security (For Authentication) – Eg. Encryption and Decryption.
Encryption -- @#$njg$#$#
Decryption -- ABCDEF
IV) UAT (USER ACCEPTANCE TESTING)
After system testing, the software developers concentrate on UAT in 2-ways:
(α)Testing (Alpha-Testing) During this testing, the developers invites the customer to organization/firm & conducts training sessions & get the feedback.
(β) Testing (Beta-Testing) During this testing, the developers or responsible team will go to customer place and they will explain about the product and get the feedback.
Wow its a very good post. The information provided by you is really very good and helpful for me. Keep sharing good information.
ReplyDeleteSoftware Testing Services
Software Testing Company
Software Testing Companies
QA Testing Services
Functional Testing Services
Test Automation Services
Functional Testing Company
Performance Testing Services
Security Testing Services
API Testing Services
i am glad to discover this page : i have to thank you for the time i spent on this especially great reading !! i really liked each part and also bookmarked you for new information on your site.
ReplyDeleteQA Companies
Automation Testing Companies
Mobile App Testing Companies
Performance Testing Companies
Security Testing Companies
Nice Blog, When I was read this blog, I learnt new things & it’s truly have well stuff related to developing technology, Thank you for sharing this blog. If Someone wants to know about Top Big Data Companies this is the Right place for you!
ReplyDelete