Question Answers

Module 3
1 mark

1. What is Black Box Testing?

Black Box Testing is a software testing method in which the functionalities of
software applications are tested without having knowledge of internal code
structure, implementation details and internal paths.
2. What is requirement based testing?
Requirements-based testing is a testing approach in which test cases, conditions
and data are derived from requirements. It includes functional tests and also
non-functional attributes such as performance, reliability or usability.

3. What is Positive Testing?

Positive Testing is a type of testing which is performed on a software application by
providing the valid data sets as an input.

4. What is Negative Testing?

Negative Testing is a testing method performed on the software application by providing

invalid or improper data sets as input

5. What are the Testing Technique used for Positive and Negative Testing?
Following techniques are used for Positive and negative validation of testing is

1. Boundary Value Analysis

2. Equivalence Partitioning

6. What is decision table?

A Decision Table is a tabular representation of inputs versus rules /cases /test conditions.
It is a very effective tool used for both complex software testing and requirements
management.

7. What is State Based Testing?

State Based means change from one state to another. State based Testing is useful to
generate the test cases for state machines as it has a dynamic behavior (multiple state) in
its system.
8. What are the ways to represent state transition?
There are two main ways to represent or design state transition
1) State transition diagram
2) State transition table.
9. What is Compatibility Testing?

Compatibility Testing is a type of Software testing to check whether your software is

capable of running on different hardware, operating systems, applications, network
environments or Mobile devices.
10. What is User Documentation Testing?

User Documentation covers all the manuals, user guides, installation guides, setup
guides, read me files, software release notes, and online help that are provided along with
the software to help the end user to understand the software system.

11. What is Domain Testing?

It is a software testing technique where minimum numbers of inputs are used to access
appropriate output of a system, to ensure the system does not accept invalid input values.

12. What is Domain Knowledge?

Domain knowledge is the good understanding of particular sphere i.e. a person is acquainted
with particular term of discipline. It helps to minimize delivery cycle, improve customer
service and reduce development time

2 marks

1. How to do BlackBox Testing

The generic steps followed to carry out any type of Black Box Testing are

1.Initially, the requirements and specifications of the system are

examined.
2. Tester chooses valid inputs (positive test scenario) to check whether
SUT processes them correctly. Also, some invalid inputs (negative test
scenario) are chosen to verify that the SUT (System Under Test) is able
to detect them.
3. Tester determines expected outputs for all those inputs.
4. Software tester constructs test cases with the selected inputs.
5. The test cases are executed.
6. Software tester compares the actual outputs with the expected outputs.
7. Defects if any are fixed and re-tested.
2. What are the types of Black Box Testing?
There are many types of Black Box Testing but the following are the prominent
ones –
 1. Functional testing – This black box testing type is related to the
functional requirements of a system; it is done by software testers.
2. Non-functional testing – This type of black box testing is not related to
testing of specific functionality, but non-functional requirements such as
performance, scalability, usability.
3. Regression testing – Regression Testing is done after code fixes, upgrades
or any other system maintenance to check the new code has not affected
the existing code

3. Black Box Testing Techniques

Following are the prominent Test Strategy amongst the many used in Black box
Testing

1. Equivalence Class Testing: It is used to minimize the number of possible

test cases to an optimum level while maintains reasonable test coverage.
2. Boundary Value Testing: Boundary value testing is focused on the values
at boundaries. This technique determines whether a certain range of values
are acceptable by the system or not. It is very useful in reducing the
number of test cases. It is most suitable for the systems where an input is
within certain ranges.
3. Decision Table Testing: A decision table puts causes and their effects in a
matrix. There is a unique combination in each column.

4. What is Positive Testing?

Positive Testing is a type of testing which is performed on a software
application by providing the valid data sets as an input.

For example

Enter Only Numbers

Positive Testing

There is a text box in an application which can accept only numbers.

Entering values up to 99999 will be acceptable by the system and any
other values apart from this should not be acceptable. To do positive
testing, set the valid input values from 0 to 99999 and check whether
the system is accepting the values.
5. What is Negative Testing?

Negative Testing is a testing method performed on the software application by

providing invalid or improper data sets as input

For example

Negative testing can be performed by entering characters A to Z or from a to z.

either software system should not accept the values or else it should throw an error
message for these invalid data inputs.

6. What is Boundary Value Analysis?

This is one of the software testing technique in which the test cases are designed
to include values at the boundary. If the input data is used within the boundary
value limits, then it is said to be Positive Testing. If the input data is picked
outside the boundary value limits, then it is said to be Negative Testing.

For example –

A system can accept the numbers from 0 to 10 numeric values. All other numbers
are invalid values. Under this technique, boundary values -1,0,1 and 9,10,11 will
be tested.

7. What is Equivalence Partitioning?

This is a software testing technique which divides the input data into many
partitions. Values from each partition must be tested at least once. Partitions with
valid values are used for Positive Testing. While partitions with invalid values are
used for negative testing.
For example-

Numeric values Zero to ten can be divided into two (or three) partitions. In our
case, we have two partitions -10 to -1 and 0 to 10. Sample values (5 and -5) can be
taken from each part to test the scenarios.

8. What are the Advantages of Decision Table Testing?

1. When the system behavior is different for different input and not same for a
range of inputs, both equivalent partitioning, and boundary value analysis
won’t help, but decision table can be used.
 2. The representation is simple so that it can be easily interpreted and is used for
development and business as well.
3. This table will help to make effective combinations and can ensure a better
coverage for testing
4. Any complex business conditions can be easily turned into decision tables

9. What are the Parts Of State Transition Diagram?

There are 4 main components of the State Transition Model as below

1) States that the software might get

2) Transition from one state to another

3) Events that origin a transition like closing a file or withdrawing money

4) Actions that result from a transition (an error message or being given the
cash.)

10. What are the different types of version checking in compatibility testing

There are two types of version checking in Compatibility Testing

1. Backward Compatibility Testing
2. Forward Compatibility Testing

Backward Compatibility Testing

Backward Compatibility Testing is a technique to verify the behaviour and

compatibility of the developed hardware or software with their older versions of the
hardware or software. Backward compatibility testing is much predictable as all the
changes from the previous versions are known.

Forward Compatibility Testing

 Forward Compatibility Testing is a process to verify the behaviour and compatibility
of the developed hardware or software with the newer versions of the hardware or
software. Forward compatibility testing is a bit hard to predict as as the changes that
will be made in the newer versions are not known.

11. How to do Compatibility Testing.

1. The initial phase of compatibility testing is to define the set of environments or

platforms the application is expected to work on.
2. The tester should have enough knowledge of the platforms/software/hardware to
understand the expected application behavior under different configurations.
3. The environment needs to be set-up for testing with different platforms, devices,
networks to check whether your application runs well under different configurations.
4. Report the bugs. Fix the defects. Re-test to confirm Defect fixing.

12. What is the Structure of Domain Testing ?

The process is quite similar everywhere when it comes to build the strategy, where the
following step-by-structure is used that suits most of the scenarios

1. Think what can go wrong.

2. Find a solution to handle each case.
3. Pick several points to test each error.
4. Take one test point to examine adjacent domains
5. Then start running the test
6. Check if the boundaries are faulty in nature
7. Inspect boundaries of all domains

13. Is domain knowledge required for Domain testing?

It is difficult for someone to perform effectively in a field where the person is not familiar. So
a domain tester should to have basic domain knowledge. It is important because:
1. Online banking

A tester must have to be an expert in the online banking activities like login, bill payment,
transfers.

2. Retail domains

To successfully run a domain test, testers have to recognize how things work flow at
different levels. Some examples of retail domains are warehouse management, in-store
solutions etc.
 3. Healthcare

A tester with proper understanding of domain knowledge should handle a healthcare

system. It is a huge risk to someone’s life when someone with zero knowledge handles
the system.

14. What is Domain Testing Strategy?

We know that every domain has a boundary from which it is been defined, points near the
boundaries are checked during tests. A testing process every time begins with a question. The
domain testing strategy is an experiment by a QA specialist to find the solutions to these
answers

1. What domain should be tested?

2. How to group values into classes?
3. What value should I test?
4. How am I going to get the results?

15. Example of Domain testing

Let there be a group of students in a study tour. For entertainment purpose they have been
given a ticket to perform a specific activity based on gender and age inputs. Here the
entertainment facility act as the test, age groups will be boundary values with numerous
possible scenarios. Students perform activities in following manner:

1. Children less than 5 years old are to tell a poem

2. Boys 5>=10 are to draw
3. Girls 5>=10 are to sing a song
4. Boys >10 are to compete in a sport
5. Girls >10 are to participate in quiz
6. Remaining children >15 are to participate in essay competition

On the basis of given algorithm, specialist groups the values into classes i.e. age groups, then
boundary values is picked i.e. highest and lowest age value in a group. Then different
scenarios are built with expected results for each.
16. What are the Skills required for Domain testing?
To be a good domain tester, one must have the following skills

1. Quick learner
2. Domain knowledge
3. Can work under pressure
4. Technical and Programming skill
5. Automation skill
6. Bug hunting skill
7. Communication skill

4 marks

1. Differences between Black Box Testing vs White Box Testing

Black Box Testing White Box Testing

It is a way of testing the software

It is a way of software testing in in which the tester has knowledge
which the internal structure or the about the internal structure or the
program or the code is hidden code or the program of the
and nothing is known about it. software.

It is mostly done by software It is mostly done by software

testers. developers.

No knowledge of implementation Knowledge of implementation is

is needed. required.
It can be referred as outer or It is the inner or the internal
external software testing. software testing.

It is functional test of the

software. It is structural test of the software.

This testing can be initiated on This type of testing of software is

the basis of requirement started after detail design
specifications document. document.

No knowledge of programming is It is mandatory to have

required. knowledge of programming.

It is the behavior testing of the It is the logic testing of the

software. software.

It is applicable to the higher It is generally applicable to the

levels of testing of software. lower levels of software testing.

It is also called as clear box

It is also called closed testing. testing.

It is least time consuming. It is most time consuming.

It is not suitable or preferred for

algorithm testing. It is suitable for algorithm testing.

Can be done by trial and error Data domains along with internal
ways and methods. boundaries can be better tested.

Example: search something on Example: by input to check and

google by using keywords verify loops
 Types of Black Box Testing: Types of White Box Testing:

● A. Functional Testing ● A. Path Testing

● B. Non-functional testing ● B. Loop Testing

● C. Regression Testing ● C. Condition testing

2. Stages in Requirements based Testing

1. Defining Test Completion Criteria

Testing is completed only when all the functional and non-functional testing is
complete.

2. Design Test Cases

A Test case has five parameters namely the initial state or precondition, data
setup, the inputs, expected outcomes and actual outcomes.

3. Execute Tests
Execute the test cases against the system under test and document the results.

4. Verify Test Results

Verify if the expected and actual results match each other.

5. Verify Test Coverage

Verify if the tests cover both functional and non-functional aspects of the
requirement.

6. Track and Manage Defects

Any defects detected during the testing process goes through the defect life cycle
and are tracked to resolution. Defect Statistics are maintained which will give us
the overall status of the project.

3. Requirement traceability Matrix (RTM)

Requirements tracing, a process of documenting the links between the requirements

and the work products developed to implement and verify those requirements. The
RTM captures all requirements and their traceability in a single document delivered at
the conclusion of the life cycle.
 RTM - WorkFlow
The Matrix is created at the very beginning of a project as it forms the basis of the
project's scope and deliverables that will be produced.
The Matrix is bi-directional, as it tracks the requirement forward by examining the
output of the deliverables and backward by looking at the business requirement that
was specified for a particular feature of the product.

Requirement traceability Matrix - Parameters:

1. Requirement ID
2. Risks
3. Requirement Type
4. Requirement Description
5. Trace to Design Specification
6. Unit Test Cases
7. Integration Test Cases
8. System Test Cases
9. User Acceptance Test Cases
10. Trace to Test Script

4. Difference between Positive Testing and Negative Testing.

Positive Testing Negative Testing

 It is performed only for It is performed for unexpected
expected conditions. conditions.

It doesn’t cover all possible

cases. It covers all possible cases.

It doesn’t ensure a good

quality product. It ensures a good quality product.

It is less important as It is more important as compared

compared to Negative testing. to Positive testing.

It can be performed by people It can only be performed by

having less knowledge. professionals.

It takes less time. It takes more time.

It is performed on every It is performed where are chances

application. of unexpected conditions.

It ensures 100% defect free

It ensures software is normal. software.

5. How to make Decision Base Table for Login Screen.

Let’s create a decision table for a login screen.

The condition is simple if the user provides correct username and password the user
will be redirected to the homepage. If any of the input is wrong, an error message will
be displayed.
Conditions Rule 1 Rule 2 Rule 3 Rule 4
Username (T/F) F T F T
Password (T/F) F F T T
Output (E/H) E E E H

Legend

1. T – Correct username/password
2. F – Wrong username/password
3. E – Error message is displayed
4. H – Home screen is displayed

Interpretation

1. Case 1 – Username and password both were wrong. The user is shown
an error message.
2. Case 2 – Username was correct, but the password was wrong. The user
is shown an error message.
3. Case 3 – Username was wrong, but the password was correct. The user
is shown an error message.
4. Case 4 – Username and password both were correct, and the user
navigated to homepage

While converting this to test case, we can create 2 scenarios,

1. Enter correct username and correct password and click on login, and the
expected result will be the user should be navigated to homepage

And one from the below scenario

1. Enter wrong username and wrong password and click on login, and the
expected result will be the user should get an error message
2. Enter correct username and wrong password and click on login, and the
expected result will be the user should get an error message
3. Enter wrong username and correct password and click on login, and the
expected result will be the user should get an error message

As they essentially test the same rule.

6. Draw state transition diagram and state transition table

Let’s consider an ATM system function where if the user enters the invalid password
three times the account will be locked.
In this system, if the user enters a valid password in any of the first three attempts the user
will be logged in successfully. If the user enters the invalid password in the first or second try,
the user will be asked to re-enter the password. And finally, if the user enters incorrect
password 3rd time, the account will be blocked.

State transition diagram

In the diagram whenever the user enters the correct PIN he is moved to Access granted state,
and if he enters the wrong password he is moved to next try and if he does the same for the
3rd time the account blocked state is reached.

State Transition Table

Correct PIN Incorrect PIN

S1) Start S5 S2

S2) 1st attempt S5 S3

S3) 2nd attempt S5 S4

S4) 3rd attempt S5 S6

S5) Access Granted – –

S6) Account blocked – –

In the table when the user enters the correct PIN, state is transitioned to S5 which is Access
granted. And if the user enters a wrong password he is moved to next state. If he does the
same 3rd time, he will reach the account blocked state.

7. What are the types of testing documents?

Types of Testing
Description
Documents
It is a high-level document which describes principles, methods
Test policy
and all the important testing goals of the organization.
A high-level document which identifies the Test Levels (types)
Test strategy
to be executed for the project.
A test plan is a complete planning document which contains the
Test plan
scope, approach, resources, schedule, etc. of testing activities.
Requirements
This is a document which connects the requirements to the test
Traceability
cases.
Matrix
Test scenario is an item or event of a software system which
Test Scenario
could be verified by one or more Test cases.
It is a group of input values, execution preconditions, expected
Test case execution post conditions and results. It is developed for a Test
Scenario.
Test Data is a data which exists before a test is executed. It used
Test Data
to execute the test case.
Defect report is a documented report of any flaw in a Software
Defect Report
System which fails to perform its expected function.
Test summary report is a high-level document which
Test summary
summarizes testing activities conducted as well as the
report
test result.

8. What are the Types of Compatibility Tests?

1. Hardware: It checks software to be compatible with different hardware

configurations.
2. Operating Systems: It checks your software to be compatible with different
Operating Systems like Windows, Unix, Mac OS etc.
3. Software: It checks your developed software to be compatible with other
software. For example, MS Word application should be compatible with other
software like MS Outlook, MS Excel, VBA etc.
4. Network: Evaluation of performance of a system in a network with varying
parameters such as Bandwidth, Operating speed, Capacity. It also checks
application in different networks with all parameters mentioned earlier.
5. Browser: It checks the compatibility of your website with different browsers like
Firefox, Google Chrome, Internet Explorer etc.
 6. Devices: It checks compatibility of your software with different devices like USB
port Devices, Printers and Scanners, Other media devices and Blue tooth.
7. Mobile: Checking your software is compatible with mobile platforms like
Android, iOS etc.
8. Versions of the software: It is verifying your software application to be
compatible with different versions of the software. For instance checking your
Microsoft Word to be compatible with Windows 7, Windows 7 SP1, Windows 7
SP2, Windows 7 SP3.

9. What is Graph Based Testing?

Graph based testing is useful to represent a transaction or work flows. Consider an example
of a leave application by an employee. A typical leave application process can be visualized
as being made up of the following steps

1. He applies leave application form

2. HR verify eligibility for leave
3. If it is eligible manager ensures feasibility
1. If it is feasible manager approve leave
2. If it is not feasible manager rejects leave

E
15 marks

1. How to make Decision Table for Upload Screen.

Now consider a dialogue box which will ask the user to upload photo with certain conditions
like –
1. You can upload only ‘.jpg’ format image
2. File size less than 32kb
3. Resolution 137*177.

If any of the conditions fails the system will throw corresponding error message stating the
issue and if all conditions are met photo will be updated successfully

Let’s create the decision table for this case.

Conditions Case 1 Case 2 Case 3 Case 4 Case 5 Case 6 Case 7 Case 8

Format .jpg .jpg .jpg .jpg Not .jpg Not .jpg Not .jpg Not .jpg
Less than Less than Less than Less than
Size >= 32kb >= 32kb >= 32kb >= 32kb
32kb 32kb 32kb 32kb
Not Not Not
resolution 137*177 Not 137*177 137*177 137*177 137*177
137*177 137*177 137*177
Error
Error
Error Error Error message
Error Error message
message message message for
Photo message message format
Output size size and for format format,
uploaded resolution for format and
mismatc resolution and size size, and
mismatch mismatch resolution
h mismatch mismatch resolution
mismatch
mismatch

For these conditions, we can create 8 different test cases and ensure complete coverage based
on the above table.

1. Upload a photo with format ‘.jpg’, size less than 32kb and resolution 137*177 and
click on upload. Expected result is Photo should upload successfully
2. Upload a photo with format ‘.jpg’, size less than 32kb and resolution not 137*177 and
click on upload. Expected result is Error message resolution mismatch should be
displayed
3. Upload a photo with format ‘.jpg’, size more than 32kb and resolution 137*177 and
click on upload. Expected result is Error message size mismatch should be displayed
4. Upload a photo with format ‘.jpg’, size more than equal to 32kb and resolution not
137*177 and click on upload. Expected result is Error message size and resolution
mismatch should be displayed
5. Upload a photo with format other than ‘.jpg’, size less than 32kb and resolution
137*177 and click on upload. Expected result is Error message for format mismatch
should be displayed
6. Upload a photo with format other than ‘.jpg’, size less than 32kb and resolution not
137*177 and click on upload. Expected result is Error message format and resolution
mismatch should be displayed
7. Upload a photo with format other than ‘.jpg’, size more than 32kb and resolution
137*177 and click on upload. Expected result is Error message for format and size
mismatch should be displayed
8. Upload a photo with format other than ‘.jpg’, size more than 32kb and resolution not
137*177 and click on upload. Expected result is Error message for format, size and
resolution mismatch should be displayed