Presents: Complete Training On Testing

IBMMAINFRAMES.
com
Presents
COMPLETE TRAINING ON TESTING
IBMMAINFRAMES.com 1
INTRODUCTION
IBMMAINFRAMES.com 2
What is Testing?
 Testing is an activity that gives complete

confidence to the developing organization,
as well as to the customer.
IBMMAINFRAMES.com 3
Major Testing Objective
 According to G.J.Meyers, the primary role
of Testing is not demonstration of correct
performance.
 But, exposure of hidden defects.
IBMMAINFRAMES.com 4
Major principles of Testing
 Exhaustive input testing is not possible
 Testing is creative and difficult
 Prevention of defects –Testing early in the
life cycle reduces errors.
 Testing is risk based.
 Testing must be planned.
 Testing requires independence
IBMMAINFRAMES.com 5
Necessary constituents to
Effective testing
 Creativity.
 Sound domain knowledge.
 Testing experience.
 Sound methodology.
IBMMAINFRAMES.com 6
What is Risk?
 It is a Loss associated with an event
IBMMAINFRAMES.com 7
Some Major Risks
 Economical Risks (Banking).
 Life threatening (Air Traffic Controls).
IBMMAINFRAMES.com 8
How to minimize Risks?
 You can minimize the risk or avoid the
impact of risk by analysis and experience.
IBMMAINFRAMES.com 9
Heads under which risk
assessment can be made.
 Structural
 Technical and
 Size.
IBMMAINFRAMES.com 10
What is a Fault/Error?
 Difference between a computed, observed
or measured value or condition and the true,
specified or theoretically correct value or
condition.
What is Failure?
 The inability of a system (or component) to
perform its required functions within
specified performance requirements.
An Anomaly
 Any condition that deviates from
expectations is called an Anomaly.
 IEEE prefers to call errors, defects, fault,
bugs, incident, problem as an “Anomaly”.
What is IEEE?
 IEEE stands for Institution of Electronic
and Electrical Engineers.
Anomaly Classification
Process steps
 Recognition.
 Investigation.
 Action and
 Disposition.
Verification & Validation
 Testing whether we are building the Product
Right is Called….?
 Verification.
 Testing whether we are building the Right
product is called…?
 Validation.
Fundamental Test Process
 Test Planning.
 Test Specification.
 Test Execution.
 Test Recording.
 Test Completion.
Dynamic Testing Techniques
This is a simple exercise aimed at
introducing the basic concepts of
Dynamic Testing Techniques
Test Strategies
Black Box White Box

Test to the Spec. Test to the Code.
Design Test cases by Design Test cases by
understanding the understanding the
specifications. actual code.
Don’t look inside the Don’t look inside the
code Spec.
Domain Knowledge
essential
Testing Strategies
Black Box Testing: Testing of a system or

component whose inputs, outputs and general
functions are known, but whose contents or
implementation are unknown.
White Box/Glass Box/Structural Testing:
Testing that takes into account internal
mechanism of a system or component, types
include branch testing, path testing etc.,
Black Box Vs White Box
Black Box White Box
Tests are derived from the Tests require knowledge of
functional design the internal program
specifications structure and code.
Will fail to test “hidden Will fail to detect “missing
functions” functions”
Data driven Logic driven
Requires exhaustive Input Requires exhaustive path

testing to detect all errors testing to detect all errors
Levels of Testing
 Unit Testing: Done by developers at module
level – White box.
 Integration Testing: By integration team –
Black box.
 System Testing: By project team or by
separate team – Black Box.
 Acceptance Testing: By client (either at his
site or developer’s site)- Black box
White Box Testing
Objectives: Execution of every path in the program
Difficulties:
Number of unique logical paths will be very
high.
Such exhaustive testing might still not detect
any errors.
White Box Testing
Methodologies
 Statement coverage
 Branch/decision coverage
 Condition coverage
 Condition/Decision coverage.
 Multiple condition coverage.
 Data flow coverage.
Testing throughout the Life Cycle
This is a simple exercise aimed at introducing
the basic concepts of software testing.
Identify the document which :
Describes the scope, approach, resources and
schedule of intended activities.
It also identifies
• test items,
• the features to be tested,
• the testing tasks,
• who will do each task and
• any risk requiring contingency planning.
Answer: Test Plan
Software Test Life Cycle
Test Case Design

Test Design
Test Planning Test Execution
Test Summary Test Completion
Which part of IEEE describes about the Test Plan?
Answer: IEEE 610.12-1990
Following are salient features of which document?
Identifier Introduction
Test Items Features to be
tested
Features NOT to be tested Approach
Item pass/ fail criteria
Suspension criteria & Resumption requirements
Test Deliverables Testing Tasks
Environmental Needs Responsibilities
Staffing and Training needs Schedule
Risks & Contingencies Approvals
Answer: Test Plan Outline
Test plan describes some of the features of the
software that are to be tested. Give examples :
Answer:
•Functionality
•Security
•Efficiency
•Portability
•Recovery
Test plan describes some of the features of the
software NOT to be tested. Give examples :
Answer:
•Security.
•Particular features of functionality.
•HELP
These are mainly to appraise the testers not
to spend time on these now.
Test plan describes the Suspension criteria and
resumption requirements. Give examples :
1. Suppose within the first week of testing, 30

defects are encountered, you may suspend
testing (Criteria will be to keep minimum
number of defects).
2. In case of dependencies with other module,
which is not ready, Testing may be suspended.
All failed test cases must contain ___ report
Answer: Test Incident Report (TIR)
Some major levels of Testing
• Unit Testing
• Integration testing
• System Testing
• Acceptance Testing
Unit Testing - Salient Features
 Testing done by developers and not
by testing team.
 First test to start as soon as the code
is ready.
 Logic related problems will be tested.
 White Box testing.
Integration Testing
 Need: Each module will be working fine in

isolation, but not when they are combined.
 Objective: Interface Based testing.
 Two types: Non Incremental (Big Bang) &
Incremental.
Comparison
TOP DOWN BOTTOM UP
Functionality Tested early Functionality tested last
Stubs are created Drivers are created
Skeleton of work product Not until the last module is

could be shown to client created, demo can be given
Design flaws detected early Design flaws detected at
end
Stubs are not easy to create Drivers are easy to create
Sandwich Testing Explained
 Compromise candidate between Top-down

and Bottom-up.
 Top-down and bottom-up tests are started
simultaneously.
 Suitable for large programs like OS.
System testing is done at client’s place
(True/False)
--------
System testing uses White Box technique

(True/False)
--------
System testing is the process of demonstrating

how the program does NOT meet its objective
(True/False)
--------
Testing that a defect fix has not caused some
Regression test
other errors is called ___________
System Testing- Summary
 Objective: To validate total customer

requirement as per SRS. This is done to
check whether all the client requirements
are addressed.
 Done by: Testing team
 Location: Target hardware.
 Methodology: Black Box
Various tests in system testing
1. Facility Testing 8. Recovery Testing
2. Volume Testing 9. Procedure Testing
3. Load Testing 10. Compatible Testing
4. Stress Testing 11. Installability Testing
5. Usability Testing 12. Serviceability Testing
6. Security Testing 13. Documentation Testing
7. Storage Testing 14. Configuration Testing
Client complains that Context sensitive Help agreed
has not been provided. Suggest a Test
Answer: Facility Test.
_________test
Facility scans the objectives line by line
and compare it with the user manual.
Facility
Missing facilities are identified by _________
test?
Number of records is the main criteria in
Volume Test.
________
Which tests are done by creating virtual
users?
Answer: Load test & Stress test
Think Time is used to simulate authentic user
_________
behavior in Load test?
What is Think time?
It is the time taken by the user to respond to a

query.
Test Scenario for Load Test
Users: CEO: 1, GM: 7, Manager: 20, Clerks: 12
So, total legitimate users: 40
Performance Requirements: Say 30 seconds for a query.
The above is a typical scenario. Like this many

scenarios are to be created.
Stress test subjects the application under test to
_______
peak volume of data in a short time.
Think time is not the criteria in Stress Test

(True/False)
---------
Stress Test - Explained
 Suppose a product is intended for 1000

users at a time. As the users increase, the
breaking down of the performance is
inevitable. But, the break down has to be
graceful.
 Example: Results of TNPCE exam on net.
 Visitors to the CNN site during sept 11,
2001.
Usability Test checks for human factor
________
problems?
Salient features of Usability Test
 Tolerance of the application is very important.

 It should not take control from the user. User
must be kept informed of the status like
progress bar or appropriate messages.
 GUI standards must be followed.
 Error messages should not be too long.
 Default buttons in message boxes must be
consistent.
Test cases devised to subvert the program’s
Security test
security concerns are written in __________
Storage test is performed to detect amount of
_________
main and storage requirements of a program.
Recovery
________ test determines the ability of the
user to recover data after a failure.
Procedure
_________ test enables the user to do exactly
what the manuals have requested.
Example: Responding to paper out light on printer
_____________________
Compatible/Conversion test ensures that the
software works with all required optional
software components.
Checking whether the software favorably
responds to requests like Custom Install,
Installability Test
Partial Install is done by ____________
____________
Installability Test is to be conducted to
ensure that the current version of the software
coexist with the previous version.
Serviceability Test ensures that the software
____________
automatically goes to the maintenance
module, in case of any error/defect with the
program.
For example, in an ATM operation, if the

machine is found to be tampered with, the
software will automatically go to the
maintenance module, alert the maintenance
dept and lock itself.
Documentation
_____________ test ensures that the program
examples given in the user documentation are
working fine.
Configuration
____________ test is to be conducted to find
whether the program works with different
hardware devices with minimum and maximum
configuration.
Acceptance
__________ test is conducted to determine
whether a software satisfies its acceptance
criteria.
Acceptance test is conducted by the client /

Developer
---------------
When a software is developed for more than
one customer, then the software builders use a
Alpha & ________
process called _______ Beta Tests.
For example, a software developed for

Electricity Board could be used by TNEB,
APEB and BEST (Mumbai)
Alpha test is conducted at Developer’s/ Clients
site by Client/Developer. ----------
-------------
Alpha test is done in a controlled environment

with the developer breathing down the neck.
(True / False).
--------
Same product to be used by many clients is
Beta testing.
given to privileged customers for _____
In Beta testing, the environment is

Live / Controlled by developer.
----------------------------------
Beta Testing
Advantages Disadvantages
Many Testers Many testers reporting the
same defect.
Live Environment Potential defects found, but
not escalated.
Alpha Vs Beta Test
ALPHA TESTING BETA TESTING

Conducted at developer’s Conducted at one or
site customers’ site
Conducted in a controlled Conducted in free
environment. environment.
Test Management
This is a simple exercise aimed at
introducing the basic concepts of
software Test Management.
What is Test Management ?
Planning and monitoring the software testing

effort and controlling the testing resources
throughout software testing levels.
Why Test Management ?
Because 100% testing is not possible.
Why 100% testing is not possible?

Because
1. Domain may be too large to test.
2. Too many possible paths to test.
3. UI issues are too complex to test.
4. Limited time and Resources.
How to go about Test Management?
 Planning the test effort.

 Monitoring test effort.
 Controlling Test resources and
 Verifying implementation.
What is Strategy?
A Strategy is making plans to achieve a

Goal.
What is Test Strategy?
•Indicates how testing is to be carried out.

•Indicates where to emphasize so that best
possible use of resource and time can be
made.
•Aims to detect most important errors early,
minimizing the costs.
•Addresses most of the risk and different
types of testing.
What is Risk?
•Risk = Chance of failure * Damage

•Risk = (Probability of unwanted outcome) *
(Loss due to unwanted outcome).
Test Strategies
Black Box White Box

Test to the Spec. Test to the Code.
Don’t look inside Don’t look inside
the code the Spec.
Testing Strategies
Black Box Testing: Testing of a system or

component whose inputs, outputs and general
functions are known, but whose contents or
implementation are unknown.
White Box/Glass Box/Structural Testing:
Testing that takes into account internal
mechanism of a system or component, types
include branch testing, path testing etc.,
What are the chances of Error?
• Errors can be due to:

• Complex functions involved.
• New functions, which the testing team
is not aware of.
• Functions for which tools are applied
for the first time.
• Developer’s lack of domain knowledge.
• Insufficient QA
What is Damage?
 Damages will be in the forms of:
 Cost of re-work
 Loss of customer confidence.
 Legal consequences.
Why to assess Risk and Damages?
Outlining software risks and damages will help

the testers prioritize the test and allow them to
concentrate on tests that are more likely to fail
or have large impact on the customer, if they
fail.
Test Strategies, when there is not enough time.
1. Test for features that would have major

impact to customers, if they fail (Smoke Test).
2. Record any features not tested.
3. Record reasons for not testing certain
features.
What is a Test Plan?
a. Test planning is the process to proactively

decide what the important issues in testing
are.
b. How best to deal with the identified
important issues.
c. Artifact produced as a result of these
activities is a Test Plan.
Test Plan – When to start?
a. Begin developing test plans as soon as the

SRS and project plans are being developed.
b. Acceptance Test plan can start as soon as
the requirement definition process begins.
Measuring Test Effort
a. Statement/ Decision/ Path/ Branch

coverage.
b. Requirement coverage.
c. Types of Defects.
d. Defect density.
Testing Resources
a. Includes Test plans, test procedures, test

cases, stubs, drivers, test results. (All these
are also called Test wares).
b. Test resources are controlled to know the
version of the product in use at a given time
and ensure that changes are incorporated in a
controlled manner.
Who is responsible for Test Management?
Software Test Manager is responsible at all the

phases of life cycle.
Test Management Activities
a. Preparing Test plan.

b.Design and document functional test cases.
c. Static analysis of code. Includes checking
for dead code, unused/ uninitialized variables.
d. Performing regression tests.
e. Manage and control test resources/testware.
f. Use automated testing tools.
Test Management Tools
a. Test management tools available in the

market are Test manager, Test Director etc.,
b. Better to use “Model based testing”.
What is Model based Testing?
a. It uses a description of the application’s behaviour

to determine- what actions are possible and what
outcome is expected.
b.Test cases are prepared based on State Transitions.
For example, account opening, Closing, Suspension.
What are the Advantages?
i. Generates new test sequences endlessly.

ii. Adapts well to changes in the application.
iii. Can be run on any machines.
iv. Can be run day and night.
Methods of Testing
a. Manual testing.
b. Static scripts for regression testing.
c. Monkey Testing
- All sorts of Inputs/activities.
- Tests only for robustness of software.
- Does not fully test the functionalities.
d. Model based testing.
How to verify the Implementation?
a. Periodic review of test activities by Test

Manager.
b. Performing Regression Tests
c. Software Quality Assurance Group reviews
and Audits.
What is achieved by Test Management?
a. Early detection of defects at low cost.

b. Focussed testing effort.
c. More comprehensive testing by using
automation.
d. Satisfied customer
Test your Testing Skills
This is a simple exercise aimed at rechecking
the understanding of an individual with respect
to the basic types of software testing.
By no means comprehensive, an attempt has been
made here, to inculcate various test practices,
methods to students and practitioners of testing, so
that a revisit to the concepts could be made.
The domain has been deliberately chosen as
Banking, as banking operations, with all the
security features and exposure to a sensitive
and volatile group of clientele, provides the right
breeding ground for errors with embarrassing
consequences.
While an innocent error could pass as a defect
due to negligence, the same error runs the risk
of being viewed from the vigilance angle also
and thus requires the best of testing minds.
It is also chosen to use my familiarity with

Banking for over 25 years.
People’s Bank of India (PBI) is a commercial Bank
giving varied services to the customers both at India
and abroad.
Their services include:
• Fixed Deposits
• Loans & Advances.
• Savings Account.
• Current Account.
• Demand Drafts, Mail Transfers.
• Clearing of local and outstation cheques.
Their auxiliary services include:
- Safe Deposit Lockers
- Standing Instructions
- Money Transfers
You are in the team , which develops the Savings
Bank (called SB) module of Banking operations.
Following modules are developed in SB module:

- Maintenance of Savings Bank accounts.
- Cheque Book Master maintenance.
- SB Transaction Entry.
- Regular and Day End reports.
Other modules under preparation are Current
Account, Loans and Deposits.
As a Software Test professional, please
provide the solution that you feel would be
appropriate for the following questions.
Q-1: Your Test Manager asks you to test the
functionality of the Current account module
developed by others. What type of test will you be
undertaking, White box or Black box?
Answer: Black Box testing.
Q-2: You were asked to test a particular loop in
the code written for Savings Bank Transactions.
What type of test will you be undertaking, Black
box or White Box?
Answer: White Box testing.
Q-3. For availing Cheque book facility, a customer
must maintain a minimum balance of Rs. 5000/. In
the black box testing, which of the optimization
technique will you use to check?
Answer: Boundary Value Analysis.
Q-4: In the Cheque book maintenance problem
referred above, the program works well for test
values of 1, 2500 and 5000 but not for a value of
5001. Which particular range of the Boundary
value analysis is throwing the error here?
Answer: Epsilon
point.
Q-5: After fixing the problem of Cheque books, that
particular path works well, but a hitherto unknown
problem has crept in suddenly. After the new defect
is fixed, will you be testing all other paths with
respect to this module or only that particular path
which was giving error?
Answer: All Paths.
Q-6: If you choose to test all paths after the above
mentioned defect fix, what type of testing will you
be undertaking?
Answer:Regression Test.
Q-7: After the SB module has been tested and handed
over, the client complains that a provision called “Stop
Cheques” already discussed and agreed in the
Software Requirement Specification (SRS) has not
been provided. Which test, if done, could have avoided
this feedback from the customer.
Answer: Facility Test; As a facility requested in

SRS has not been provided.
Q-8: The knowledgeable client asks you to
conduct all software tests and then hand over
the product. Will you agree?
Answer: No, because System Testing has to

be done only with the target hardware.
Q-9: Customer complains that while accessing the
Cheque book module from SB transactions, errors
are thrown. But, Transaction module and Cheque
book maintenance are working fine individually.
Can you identify the problem as to which test
could solve this?
Answer: Integration test, because both Cheque

book maintenance and transaction belonging to
the same module are working fine independently.
Q-10: SB transaction module is designed to handle
20 transactions at a time. Client wants to know what
will happen when 22 transactions are made, on
heavy days such as, a day after 3 consecutive bank
holidays. Client says even if there is a delay in
fetching the records, it is ok. But, the record must be
accessed. Which test is to be performed?
Answer:Volume Test.
Q-11: In the above situation, if the client feels
that Time is a criterion, which test is to be
conducted?
Answer: Load / Performance Test.
Q-12: The client requires that if the transactions are
22 at a time against the stipulated 20, the first 20
transactions must run smoothly and a report must
be generated about the excess of 2 transactions
and that the system should not crash. Which test is
to be conducted?
Answer: Stress Test.
Q-13: At the end of each working day, Banks indulge
in a process called “Day End Operations”, wherein all
reports (normal, exceptional, seasonal) will be
generated, backup of day’s transactions will be taken
and the date has to smoothly roll over to the next
working day. Client complains that during Backup of
Data at the end of the day, the screen goes blank
leaving them guessing whether the intended
operations are being performed or not. Suggest a
solution.
Answer: Conduct Usability test. Give a Progress
bar or a message saying, “Backup under progress.
Please wait”.
Q-14: Client complains that ” During long
operations such as Day End activities, when
backup of data and reports are taken, there is no
provision to abort the operation. Suggest a test to
redress the grievance.
Answer: Conduct usability test. Give a “Cancel”

button and provide for an honorable exit.
Q-15: You have provided only the transaction
module to the client and asked for a feedback. The
client is in the process of computerization and has
only one stand-alone system, while others are
awaited. Will it be possible for you to accede to the
client’s request to test the software for Load?
Answer: No, before load/stress test is performed,

the hardware must be in place.
Q-16: The client complains that while initially
the user password was accepted as a 8
character string, the modification of password
is accepting only a maximum of 6 characters.
Which particular test would have pre-empted
this problem?
Answer: Security Testing.
Q-17: There is a complaint from the client that while
the software has been working fine for the first week
of the month, thereafter, a message comes about
“Insufficient Disk space”. They have also recalled
that the same error happened during the first week
of previous month also and that a software engineer
(who has since left the services) fixed it. Identify the
defect and suggest remedy .
Answer: Obviously, during the first week of any
month, the transactions are heavy but the system
was successfully passing the stress test. Where it
fails is with respect to the Storage test. The reference
to last month’s operation has to be viewed in the
context that, the particular software engineer would
have dumped data and created some free disk
space, which must be done as a systematic
procedure during every month end.
Q-18: The SB package has been so designed that
any transaction will be successful only after the
transaction Log is printed, giving all details about
the transaction carried out. There have been
frequent complaints that Run time error occurs
whenever the printer is not ready and an update
command is given. Which test will take care of this
situation?
Answer: Recovery Testing.

Q-19: A particular problem occurs only during the
last day of the month, when special reports are
generated and specified procedures with respect
to interest calculations are executed. Which test
could fix this defect?
Answer: Procedure Testing.
Q-20: The banking software was running smoothly
till an external “Address Book” package was bought
by the client and installed at the same server /
machine. Which test could have precluded this
problem?
Answer: Compatibility
Test.
Q-21: While the previous version was working
fine, an updated version of the SB module was
not working properly. Suggest a Test.
Answer: Installability Test.
Q-22: Certain modules are behaving in a different
way from the examples given in the user manuals
and documentation. Suggest a Test.
Answer: Serviceability Test.
Q-23: The client was planning to go for a Pentium
IV with 60 GB hard disk and 256 Mb RAM, at the
time of placement of the order and the software
development is proceeding under that assumption.
Client now asks whether he can go for a PIII with 20
GB hard disk and 64 Mb RAM? Which test should
the software pass to accede to this request?
Answer: Configuration Testing.
Q-24: In the menu driven SB module, screens are
displayed in a haphazard manner. For example, if
you click on the Transaction option, the Report
screen is displayed and Cheque Book
Maintenance leads to the Transaction screen.
Which test will the software be failing?
Answer: Sanity Test.
Q-25: You have completed all the modules in SB
and want the customers’ feedback. Since, banking
is a general product, you may like more than one
Banker to look into that and get back to you, so
that depending on the feedback you expect to
improve on the performance of the product. Is it a
test and if so what is this particular test called?
Answer: Yes. Beta Testing.
Q-26: You invite the customer to your site and
test the product, before it is released. What
types of test are trying to do?
Answer: Alpha Testing.
Copyright: IBMMAINFRAMES.com

Presents: Complete Training On Testing

Enviado por

Dados do documento

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Presents: Complete Training On Testing

Enviado por

Direitos autorais:

Formatos disponíveis

IBMMAINFRAMES.

COMPLETE TRAINING ON TESTING

 Testing is an activity that gives complete

Black Box White Box

Black Box Testing: Testing of a system or

Requires exhaustive Input Requires exhaustive path

Objectives: Execution of every path in the program

Test Case Design

Test Planning Test Execution

Test Summary Test Completion

Answer: IEEE 610.12-1990

Answer: Test Plan Outline

1. Suppose within the first week of testing, 30

Answer: Test Incident Report (TIR)

 Need: Each module will be working fine in

Stubs are created Drivers are created

Skeleton of work product Not until the last module is

 Compromise candidate between Top-down

System testing uses White Box technique

System testing is the process of demonstrating

 Objective: To validate total customer

Answer: Facility Test.

Answer: Load test & Stress test

What is Think time?

It is the time taken by the user to respond to a

The above is a typical scenario. Like this many

Think time is not the criteria in Stress Test

 Suppose a product is intended for 1000

 Tolerance of the application is very important.

Example: Responding to paper out light on printer

For example, in an ATM operation, if the

Acceptance test is conducted by the client /

For example, a software developed for

Alpha test is done in a controlled environment

In Beta testing, the environment is

ALPHA TESTING BETA TESTING

Planning and monitoring the software testing

Because 100% testing is not possible.

Why 100% testing is not possible?

 Planning the test effort.

A Strategy is making plans to achieve a

•Indicates how testing is to be carried out.

•Risk = Chance of failure * Damage

Black Box White Box

Black Box Testing: Testing of a system or

• Errors can be due to:

Outlining software risks and damages will help

1. Test for features that would have major

a. Test planning is the process to proactively

a. Begin developing test plans as soon as the

a. Statement/ Decision/ Path/ Branch

a. Includes Test plans, test procedures, test

Software Test Manager is responsible at all the

a. Preparing Test plan.

a. Test management tools available in the

a. It uses a description of the application’s behaviour

What are the Advantages?

i. Generates new test sequences endlessly.

a. Periodic review of test activities by Test

a. Early detection of defects at low cost.

It is also chosen to use my familiarity with

Following modules are developed in SB module:

Answer: Black Box testing.