Skip to main content

WHITE BOX TESTING...a transparent way to test!!

        WHITE BOX TESTING





            White box testing is a type a testing used in software development life cycle testing phase. White box testing also called as glass box testing, transparent box testing, and structural testing
         
            In white box testing, the internal structure of the product is transparent to the tester. This testing is a method of testing the application at the level of source code. The overall point of white box testing is the ability to know that which part or line of code is being executed also through white box testing we are able to find out that what should be the correct output of the product.


   LEVEL OF WHITE BOX TESTING

ü UNIT TESTING: White box testing is done during unit testing to check that whether the code is working as our requirements.

ü INTEGRATION TESTING: At this level the white box testing is done in order to test the interactions of different interfaces.

ü REGRESSION TESTING:  White box testing in this level is done to check whether the testing cause any side effect to the code or not.
              
            White box testing is very beneficial and one of the two great methodologies used in the testing phase of software development lifecycle (SDLC). It has many advantages and several disadvantages that need to be looked upon once.

Ø We can optimize the code easily as errors are efficiently revealed in white box testing
Ø These tests are more easily to automate
Ø White box testing does not relate to the functionality of the product.

White box testing involves test cases that are derived through the use of design techniques namely data flow testing, statement coverage, and decision coverage, path testing, and control flow testing.
            White box testing uses these above-mentioned techniques as guidelines so that it can provide us an error free environment.

WHITE BOX TESTING IS DONE BY:

White box testing is done by developers as they have deep knowledge of the programming language in which a particular product/software is designed or coded.

But if software tester also has up to mark knowledge of  that programming language in which software is designed or coded then he or she can also participate in white box testing.

STEPS TO PERFORM WHITE BOX TESTING:

There are actually 2 main steps or stages in which white box testing is performed. Let us understand these steps.

STEP1  The first and most important step of white box testing is to understand  the functionality of the application through its source code. For that case, the tester should be aware of the coding environment, programming languages and other related tools and techniques that are used for the development  of the particular product.

STEP2
 In the second step, we have to create the test cases and execute them.


The above blog enables you to understand white box testing a bit. For deeper knowledge of testing, stay tuned with our very own SCOPIDEA.


                         

Comments

Popular posts from this blog

Why Driven Testing Important for every Software Tester

Context driven testing, Tester have to set their own path to complete their testing objectives, Test product, test documentation and test deliverable. The meaning of context-driven testing is project capture application of skill and opinion. Tester start testing with context driven testing it is very easy to understand and test application, therefore testing is a human activity that involves a great deal of skill to do well. The context-driven software testing methodological analysis indicates for continuous and creative valuation of testing opportunities. A tester always wants to do testing with context driven testing. It’s a very good practice to hands of explore and able to be proud of that work.   Why we need context driven testing- Context driven methodology like as agile process. Agile methodology generally depends on all-inclusive of unit tests. But in context driven testing, tester have to knowledge on unit testing as well testers will change, In context driven te...

Want to know about Mobile Application Testing? Came to right place

What is Mobile Application Testing ? Mobile Application Testing is a phenomenon of testing functionality, usability and consistency of application software designed for mobiles. It is done in two ways: Automated and Manually. When you buy a new mobile, various applications came pre-installed and some you install as per your need from mobile software distribution platforms such as Google Play, Nokia Store etc. In the recent years, mobile devices had shown a rapid growth rate .  Factors that give an open challenge to Mobile application Testing : 1. Mobile devices models : Different models have different hardware configurations, input methods (some are QWERTY, some are touch while others are normal). 2. Several different operating systems (OS) : Market  is full of availability of different operating  systems  (   Android , IOS, BREW, BREWMP, Symbian,   Windows Phone , and   BlackBerry   (RIM)).Each operating system is unique in ...

SELENIUM TESTING: SELENIUM IDE (& its installation)

In our previous post of selenium testing, we discussed selenium testing briefly. But it was just an introduction about that. And the selenium is much wider in its own. In today’s article, we are going to discuss the selenium, IDE Tool. What is Selenium IDE?? In selenium testing, selenium IDE (Selenium Integrated Development Environment) is a simple tool present in selenium suite Selenium IDE has an inbuilt record and playback functionality that allow us to create tests very quickly, easily and efficiently. Selenium IDE is very easy to install and use. As selenium IDE is a Firefox plugin, it aims to support Firefox browser only. Therefore, we can execute our created test scripts on Firefox only. Selenium IDE supports auto complete mode which allows the user to: * Enter commands more quickly *Restricts the user to enter invalid commands. The most impressive thing about the Selenium IDE in selenium testing that the user need not to have any prior knowledge of pr...