View RSS Feed


Functional Testing Simplified: The Process, Approach, Techniques and Examples

Rate this Entry
An overview of Functional Testing:

Testing and Quality Assurance are the huge part of the SDLC process. As testers, we need to be well aware of all types of testing, even if we’re not directly involved with them on a daily basis. Since testing is such an ocean and the scope of it is so vast, we have dedicated testers perform different kinds of testing. Many of you are probably already familiar with most concepts, but it wouldn’t hurt to organize it all here. So let’s get back to some basics.

On the broadest level, there are two kinds or classes of testing.

#1 ) Black box testing:

This kind of testing is exactly what it sounds like! Picture a black colored box. Let’s ask ourselves some basic questions so that we can derive a technical definition.

1. Can you see the box’s external characteristics?
2. Can you see what lies within the box?

If you now try to answer these fundamental questions, it’ll give you a perfect idea of what this entails. The answer to the above question is yes and no respectively. Therefore, black box testing can be defined as the type of testing where you view the system under test as a black box and observe how it reacts to various situations.

#2 ) White box testing:

White box testing, on the other hand, is almost the opposite of the black box testing. Let us assume that the same black box is a transparent box.

Again let’s ask some questions to derive its meaning:

1. Can you see the box’s internal characteristics?
2. Should you be testing the code?

The answer to both these questions is an affirmative “yes”. Commonly known synonyms for white box testing are glass box testing, transparent box testing, or structural testing. Therefore white box testing is a mechanism where a tester has access to the internal code of the system and executes tests to check the robustness of the code. He doesn’t have to get into the actual functionality of the application. Examples of white box testing are Unit testing, API testing, Integration and Regression testing also extend into this category based on scope. Sometimes even functional tests require the usage of white box testing. You don’t need to get into the system’s internals like its implementation, code or internal characteristics. The tester will derive the different inputs to this system based on the requirements, record the outputs for each of them and make sure they are consistent with the expectations. Examples of black box testing are: Functional testing, System testing, Acceptance testing, Regression testing, Beta testing and sometimes Integration testing also comes under this category.

All the details will be completed in next airticle
Attached Thumbnails Attached Thumbnails Type Casting a WINDOW to a STRING?-testing-classes-jpg  


Search Engine Optimisation provided by DragonByte SEO v2.0.40 (Pro) - vBulletin Mods & Addons Copyright © 2018 DragonByte Technologies Ltd.
Resources saved on this page: MySQL 11.11%
vBulletin Optimisation provided by vB Optimise v2.7.1 (Pro) - vBulletin Mods & Addons Copyright © 2018 DragonByte Technologies Ltd.
User Alert System provided by Advanced User Tagging v3.3.0 (Pro) - vBulletin Mods & Addons Copyright © 2018 DragonByte Technologies Ltd.
vBNominate (Lite) - vBulletin Mods & Addons Copyright © 2018 DragonByte Technologies Ltd.
Username Changing provided by Username Change (Free) - vBulletin Mods & Addons Copyright © 2018 DragonByte Technologies Ltd.
BetaSoft Inc.
Digital Point modules: Sphinx-based search
All times are GMT -8. The time now is 02:11 AM.

Copyright BetaSoft Inc.