Software Testing Methods

Software Testing Methods

Black Box TestingDefinition.

Black box testing method is named so because in this method, while testing the software tester can not see the internal structure of the source code and program. While performing this test, tester just focuses on the inputs and the expected outputs without knowing how the application works and these inputs are processed.

The purpose of this method is to check the functionality of the software to make sure that the software is working correctly according to the requirements and if it is meeting user demands.

This testing method can be applied to most of the software testing level: unit testing, system testing, integration testing and user acceptance testing.

Advantage

Knowledge of programming languages and implementation is not required, thus everyone can perform black box testing. Testers can work on black box tests in isolation, thus avoiding having a bias in favour of developer’s view. Furthermore, working on black box tests from tester’s point of view can help identify discrepancies in the specifications. It’s especially efficient when using on large system. Test cases can be designed as soon as the functional specifications are done.

Disadvantage

It could be challenging to design the test case if the functional specifications are contradictory and vague. It’s impossible to identify all the inputs, thus having unidentified paths is inevitable. There is a high probability of repeating tests already performed by the programmer. Identifying tricky inputs could be difficult if the test cases are not developed based on specifications.

White Box Testing Definition

In contrast with Black box testing, White box testing is a software testing method which tester can see the internal system code. White box testing is also known as Clear box testing, Glass box testing or Open box testing, . Unlike black box testing, White box testing requires tester to have knowledge of How the software is implemented and how it works, thus software developers are generally responsible for this process. This method can applicable for all levels of testing but it is mainly used in unit testing and integration testing.

Advantage

White box testing helps optimize the code by identifying hidden errors. Tests cases can be automated easily. Testing is more thorough as all code paths are usually covered. Testing can start early in Software development life cycle even if graphical user interface is not available.

Disadvantage

White box testing can be quite costly and complex. Developers who usually execute white box test cases detest it. The white box testing by developers is not detailed can lead to production errors. It requires professional resources, with an in depth knowledge of programming and implementation. It is time-consuming, especially the big applications.

Agile Testing

Agile Testing is a software testing practice that follows the principles of agile software development. In other words, agile testing means testing software for defects or any other issues quickly or within the context of agile and give quick feedback for better and faster development of the project. Agile testing focuses on finding defects or any issues quickly or within the context of agile and then giving feedback to develop the project faster and better.

Advantage

Saves time and money. Less DocumentationRegular feedback from the end user

Daily meetings can help to determine the issues well in advance

Grey-Box Testing

Grey box testing is a form of software testing which is the combination of White box testing and Black box testing. In this method, tester has partially knowledge of the internal structure and he or she will base on this knowledge to design test cases but test at the user, or black-box level. This method is mainly applicable Integration testing.

Ad-Hoc Testing

Ad hoc Testing is a software testing method without any planning and documentation. The tests are conducted informally and randomly without any formal expected results. The tester improvises the steps and arbitrarily executes them (like a monkey typing while dancing). Though defects found using this method are more difficult to reproduce (since there are no written test cases), sometimes very interesting defects are found which would never have been found if written test cases existed and were strictly followed. The success of ad hoc testing depends on the creativity and tenacity of the tester (and, of course, luck).