Types of Software Testing – G

Glass-Box Testing:

This is otherwise called White-Box Testing or Structural Testing. This testing is based on an analysis of internal workings and structure of a piece of software. This includes techniques such as Branch Testing and Path Testing.

Globalization (G11N) Testing:

This detects problems within the application design, related to usage of different languages and different character sets. The term “G11N” is coined because there are 11 letters between the “G” and “N” in the word “Globalization”.

Golden Path Testing:

This is also known as Happy Path Testing, this focuses on selective execution of tests that do not exercise the software for negative or error conditions.

Gorilla Testing:

This is testing one particular module and/or functionality heavily or exhaustively.

Green Box Testing:

Primarily for Hardware – People that work with data centers, communications and enterprise networking equipments (routers, switches, server chasis etc) know well the method of green-box testing (GB testing). This technique is used to check multi-gigabit serial links and is a procedure that determines the settings for the optimum transmitter equalization.

In order to test the systems with hundreds of high-speed channels, green-box testing is applied. It defines the transmitter settings which ensure that the system will meet BER (bit error rate). Nowadays, this technique is necessary as it ensures a successful data transmission over different channel media.

An equalization circuit includes a transmitter and a receiver. They both have their own special components that ensure the successful data transition. Usually, receivers implement:
CTLE – continuous-time linear equalizer,
DFE – decision-feedback equalizer (automatically accept the incoming signals).

Transmitters typically utilize FIR (finite-impulse-response filter) that has one pre-cursor and one post-cursor tap.

For Software – It is a Release Testing Technique exercising a software system’s coexistence with other systems or sub-systems by taking multiple integrated systems that have passed system testing as input and test their required interactions to ensure it is environment friendly and meets its functional requirements.

Grey Box Testing:

A combination of Black Box and White Box testing methodologies: testing a piece of software against its specification but using some knowledge of its internal workings.

Grey Box testing is a technique to test the application with limited knowledge of the internal workings of an application. In software testing, the term the more you know the better carries a lot of weight when testing an application.

Mastering the domain of a system always gives the tester an edge over someone with limited domain knowledge. Unlike black box testing, where the tester only tests the application’s user interface, in grey box testing, the tester has access to design documents and the database. Having this knowledge, the tester is able to better prepare test data and test scenarios when making the test plan.

Advantages Disadvantages
  • Offers combined benefits of black box and white box testing wherever possible.
  • Grey box testers don’t rely on the source code; instead they rely on interface definition and functional specifications.
  • Based on the limited information available, a grey box tester can design excellent test scenarios especially around communication protocols and data type handling.
  • The test is done from the point of view of the user and not the designer.
  • Since the access to source code is not available, the ability to go over the code and test coverage is limited.
  • The tests can be redundant if the software designer has already run a test case.
  • Testing every possible input stream is unrealistic because it would take an unreasonable amount of time; therefore, many program paths will go untested.

GUI Testing:

The software’s GUI is tested against the specification as in the GUI Mockups or Wireframes and also as in detailed design document. This ensures the GUI elements are meeting its expectations as per UI Specifications and Functional Specifications.

Blog at WordPress.com.

Up ↑

%d bloggers like this: