Page 38 - SOFTWARE TESTING & QUALITY ASSURANCE

Unit 3: Black Box Testing

black box testing is to check for completeness or appropriateness of the product or application
developed.
The specification document not only lists the functionalities of the software, but it also provides vital
information of the software to the user or customer. The user or customer depends completely on the
specification document to know the software. Therefore, it is very important that this document is free
from bugs.
The test is more often a research, since the tester should make sure that no vital information is missed or
incorrect information is provided in the document. Another important aspect of this test is to find
confusing and misinterpreted information in the software application. Any such information is
considered as a bug. The tester must understand the customer's or end user's expectations and make
sure that the document meets these requirements.
The mobile user manual is an example of specification document. The user
needs this manual to operate the mobile applications and to know all the
features that are available in the mobile. As a tester when you test the mobile as
per manual, you need to test it with an end user perspective and make sure that
the manual meets all the quality requirements. The specification should be
correct, clear, and complete with all the information of features available in the
mobile model.
Static black box testing - High Level Specification Test Technique
Testing the specification of a document is considered static, since we do not execute a program. The
first step in testing the specification through static black box testing is not to spot on the errors and
bugs. Rather, it requires a methodical approach to view the specification from a high level. The
specification should be reviewed for the fundamental explanation. The specification should be checked
if it is complete and if there has been any omissions. Static black box testing is more research oriented
and the research helps to understand how the specification is organized and the reason behind the
organization of the specification. The first step in presenting the same is to view the specification from
the perspective of the customer who would be using the software. It is important to understand and
meet customer expectations.

An important criterion while performing static black box testing is that of following standards and
guidelines. Standards have to be mandatorily followed whereas following guidelines are subjective to
the requirements of the product. Every company follows their own standards and guidelines (along
with international and national standards and guidelines) to develop specification documents. Tests
should make sure that the document strictly follows these standards and guidelines. Any violation of
these will be treated as a bug and has to be corrected. This includes the page size, color patterns, style,
font size, and so on.
As a tester, you have to research on what should appear on the software. Standards and guidelines are
formed based on certain rules followed by software developed. Let us now examine some examples of
the various sources from where standards and guidelines can be adapted:
1. Conventions Followed by Corporates: The software should adhere to the terms and conventions
used by the company.
2. Industry Requirements: Certain Industry segments like medical, pharmaceutical, and financial
industries follow their own conventions while developing software.
3. Government Standards: Government agencies follow rules stipulated by them. For example,
Military standards are unique.
4. Graphical User Interface (GUI): Software that works under Microsoft Windows or Macintosh has
separate published standards and guidelines that dictate the look and feel of the user.
5. Security Standards: Any software developed has to meet certain security standards or levels. In
some cases, they need to be certified that they meet the necessary criteria.

LOVELY PROFESSIONAL UNIVERSITY 31