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

Steps To Hunt the Bugs Successfully

The testers should catch the bugs in software that they’re testing. Testers should try to catch as several vital bugs as soon as possible. Catching the crucial bug earlier on Product-Life-Cycle can save the Projects from financial losses & mitigate the risks as compared for catching the same at a later stage in SDLC. Steps to hunt the bugs: Sometimes it’s useful to break the rules: The following test cases, which were predefined a tester can miss the bugs so it makes it impossible’s to provide the product i.e. 100 percent bug free. If you-follow pre-determined test cases you risks becoming blind to outside the bugs. A first secret is to check the functionality under the test. It’ll be an effective channel to discover the more bugs, because functionality is not generally covered by the test cases. Examine the patterns: You might have noticed that the bugs can be often met in the groups, one can call them-gregarious. The testing a new but the similar functionality...

Cross browser testing Tools

Cross Browser testing It is a process to test the web apps across multiple browsers. It involves the checking compatibility of the app across multiple web browsers & ensures that your web app’s works correctly across different web browsers. Tools for Cross Browser Testing Browser shots: The browser shots might be most exhaustive cross browser-testing tool that exists. Browser Shots includes all of most popular-browsers, like Firefox, Chrome, & Safari, along with the tons of another browser’s that might sound unfamiliar, like Sea Monkey, Flock, & Iceape. You can adjust the resolution, color-settings, & even Flash and JavaScript settings. Cross Browser Testing: It allows users to test their websites with over the hundred resolution or browser and Operating System combinations. This also has support to mobile web-browsers, which is crucial because the web traffic is making shift from the primarily desktop computer users to primarily mobile ...

Mobile Application Testing: Strategy for Development

There are a huge number of demands and lots of competitions in the mobile application industries. In that demands and competitions, the mobile application testing has become more important. The testing phase of the mobile application testing looks like evil between the creative process and excitement of new products in the market. According to the survey, “In US, on an average 2-3 hours per day people spends their time on smartphones and tablets. On that time, they spent 80% on mobile application and remaining 20% on web applications.” Few list of key factors for successful mobile application testing strategies are: Selection of Device for Testing : Before introducing the mobile application test activities, first select the devices for testing the application. Selection decision is very important because only devices can help to targets maximum numbers of the customers for accessing the application. There are two parts for device selection: §   Device Model ...