Test Types – G, H, I

Test Type
A particular type of testing that has an approach, goal and/or use of oracle(s) that provides information that is typical to that test type.

This is the fourth post in a (sub) series on Test Types. Please add any additions or remarks in the comment section.

Glass box testing
Testing or test design using knowledge of the details of the internals of the program (code and data) (BBST definition)
Too many this might sound familiar to White box testing. I think however that the perspective is quite different. Here the perspective is from a tester rather than a developer.

Gorilla testing
Gorilla testing is testing on particular module, component or functionality heavily and with large variety.

Grey box testing
Grey box testing is testing with, limited, knowledge and access to the code and internal structure and details of the software.
It is my opinion that most testers, safe pure programmers and pure black box tester, are doing grey box testing. As such they stand somewhere on a scale between the two extremes. Their place is sometimes determined by (enforced) choices of role or scope but more often by their programming and design knowledge and capabilities.

GUI testing
Graphical User Interface testing is testing the application’s user interface to detect if the functionality of the interface itself and the functionality that is directly influenced or dependent by the user interface functions correctly.
With the current growing attention to automated testing, and especially to testing on API level, the GUI is quick to be overlooked in its importance. It remains however know more than ever the first point of contact of any user with the system.

Incremental integration testing
Incremental integration testing is an approach in which you first test each module of component individually and then add them one by one together and test the integration. You can do this top down, bottom up or functionally incremental.

Installation testing
One side of installation testing is aimed at ensuring that all the necessary components are installed properly and are working as required once installed. The other side of installation testing focusses on what users need to do to install and set up new software successfully.

Integration testing
Integration testing is testing where, previously tested, individual modules and components are combined and tested as a group. It tests not only interactions between individual components but also between different sets of components and parts of the system within its direct environment. Integration testing focusses on different aspects such as functionality, performance, design and reliability.

Inter systems testing
Inter systems testing focusses at testing on interconnection and integration points of separate systems but working together.

Interface testing
Interface Testing is performed to evaluate whether systems or components pass data and control correctly to one another. It is to verify if all the interactions between these modules are working properly and errors are handled properly.

Internationalization testing
Internationalization is designing software systems in such a way that they can be adapted to different languages and regions without engineering changes, loss of functionality, loss of data or integrity issues. Internationalization testing is aimed at uncovering these potential problems.


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s