Black Box Testing:

• It is done by Test Engineer

• "During this test, we concentrate on functionality Validation with respect to
customer requirement.”
• BBT is classified to four categories:
i. Usability Testing
ii. Functional Testing
iii. Performance Testing
iv. Security Testing

Q. What type of testing you have involved?

 1. Usability Testing:
“During the test we validate user friendliness of screen or build.”
Usability Testing is classified into 2 categories:
I. GUI
i) Ease of use (Easy to understand as simplified as possible.
e.g. Hike has more functionality than what’s up still most of people using
what’s up because of its ease of use.
ii) Speed of interface (Less no of events to complete a task)
e.g. For what’s up while sending a existing msg. there is a option forward
it takes less no of events than copy paste option
iii) Look and feel (pleasantness & attractiveness)
GUI Defects
 1. Successful message is not getting displayed as “Green”
2. Unsuccessful message is not getting displayed as "Red"
3. Label name is not getting displayed with correct version with respect to
baseline document.

Note: What is mandatory field?

Mandatory / compulsory: without filling this user should not proceed.

Note: As a test engineer we have to work like a technical engineer but think like an
end user.

2. Functional testing (Requirement testing):

Functional Testing is classified into two categories:
1. Functionality
2. Non-functionality
It is also called as “Requirement Testing.”
During this test we validate the functionality of the application
with respect to customer requirement.

Q. What is difference between functionality and non-functionality? Where do

you involved?
→ I involved in functionality testing
a. Behavioural Coverage
b. Input domain Coverage
c. Error handling Coverage
 d. Backend Coverage
e. Service level Coverage
f. Calculation based Coverage

a. Behavioural coverage:
• Verify the objects property.
b. Input Domain coverage:
• To measure the size and type of input object.
c. Error Handling coverage:
• Preventing negative navigation.
d. Backend Coverage:
• Impact of content operation.
e. Service Level Coverage:
• Check the order of Functionality.
f. Calculation based Coverage:
• Measuring the arithmetic operations.

a. Behavioural Coverage: Verify the objects property.

Objects Property
Text box Focused / Unfocused

Radio Buttons On / Off

Buttons
Enable / Disable
 Check box
Checked / Unchecked

Drop down combo box

Select / Unselect Single Item

Drop down list box

Select / Unselect Multiple Item

Q. When you got a phone call from HR and she ask, is it good time to talk with
you?
→ Yea, Please go ahead.
b. Input Domain coverage:
• To measure the size and type of input object.

In an login application user provides user id and password to login user id accepts
4-8 characters alphanumeric and 3-8 characters alphabets.
BVA and ECP for User id:
BVA ECP
Min :4 -Pass a-z :-Valid
Max :8 -Pass A-Z :- Valid
Min-1 :3 -Fail 0-9 :- Valid
Max+1:9 -Fail Special character :-Invalid
Min+1:5 -Pass Blank :- Invalid
Max-1:7 -Pass Space :- Invalid

BVA and ECP for Password:

BVA ECP
Min :3 -Pass a-z :-Valid
Max :8 -Pass A-Z :- Valid
Min-1 :2 -Fail 0-9 :- Invalid
Max+1:9 -Fail Special character :-Invalid
Min+1:4 -Pass Blank :- Invalid
Max-1:7 -Pass Space :- Invalid

Q. Textbox allows 10 digit numbers as maximum.

BVA ECP
Min :10 -Pass 0-9 :- Valid
Max :10 -Pass A-Z :- Invalid
Min-1 :09 -Pass a-z :- Invalid
Max+1:11 -Fail Special character :- Invalid
Min+1:11 - Fail Blank :- Invalid
Max-1:09 -Pass Space :- Invalid

Q. Cell no. text box allows 10 digits only.

BVA ECP
Min :10 -Pass 0-9 :- Valid
Max :10 -Pass A-Z :- Invalid
Min-1 :09 - Fail a-z :- Invalid
Max+1:11 -Fail Special character :- Invalid
Min+1:11 - Fail Blank :- Invalid
Max-1:09 - Fail Space :- Invalid

c. Error Handling Coverage: Application should prevent negative navigation.

i.e. application should stop the user if invalid data is inserted.
e.g. Cell no is mandatory and should contain only numeric.
Then if user try to enter data except numeric then it should show error msg.
‘This field contains only numbers’
If user has miss cell number field and he tries to proceed without filling this
then it should show error ‘This field is required’
After completion of form filling there is checkbox of agree all terms and
conditions. If user has not clicked on check box and click on next then it
should show error msg ‘Please click on agree terms and conditions’
d. Service Level Coverage: Check on the order of Functionality.
i.e. functionality execution should be in proper sequence.
e.g.
a. If user has entered wrong user id and password and click on ok then
application should display an error msg ‘User id and Password is wrong’
In some cases if user has entered wrong credentials and user get logged and
then it is showing error msg ‘User id and Password is wrong’. It should not
be the case.

b. If there is a application form and user has entered all info. But textbox no.
D, B and A info entered by user is wrong then it should show an error msg
with sequentially
 A-x D-x
B-x B-x
D-x but it is showing A-x

e. Calculation based Coverage: Validate the arithmetic logic of an application.

Q. Which backend you are using?

Q. Which database utility tool you are using?
Q. Where you write query?
→ SQL Developer(Version) [This is Oracle’s product]
Toad (Version) [This is Dell’s product]
SQL Developer is database utility tool.

Q. What is normalization?
→ It checks redundancy.

f. Backend Testing / Database Testing:

In this we test impact of content operation.
 1. Data manipulation
2. Data Validation
3. Table structure Validation

During database testing we are going to check impact of content operation.

i.e. We have to check impact in database with respect to user front end operation.
In this we test data mapping:
Data Manipulation: Two different databases but having cone neon factors,
parameters, attributes, features.

Suppose we want to find no of females working in Capgemini, whose branches are

in pune and Chennai.
In Pune branch database female denoted as ‘F’ and in Chennai branch database
female denoted as ‘Female’
Table Structure Validation:
In this we test- Data Type
Data Type Size
Mandatory
Null
Range
Flag
Data duplication

Non-Functional Testing: A complex level in system testing during which the

testing team concentrates on extra characteristics of the software.

i. Recovery Testing/Reliable Testing

ii. Compatibility Testing
iii. Configuration Testing
iv. Inter system Testing
v. Installation Testing
vi. Load Testing
vii. Stress Testing
viii. Data Volume Testing
ix. Parallel Testing

i. Recovery Testing/Reliable Testing:

During this test we validate whether the application recover from abnormal
situation to normal.
i.e. Application functionality should work properly when application recover from
abnormal situation to normal situation.

e.x. of abnormal situation:-

Server down
Response not received
System Crash
Dependent application under process

• Normal-Need not be executed

• Abnormal-Stick to be executed
Example of recovery testing:-
Customer Requirement: Request should be processed in FIFO manner and waiting
time for request is 2 min.

Two components are integrated with single database. What it means when Rc1d is
under process so time will be 2 min.
Then Rc2d is get processed. (Rc1d will wait for 2 min to complete the Rc1d.)
(R𝑐1 1 → Request of component 1
R𝑐1 2 → Second Request of component 1
R𝑐2 1 →First request of component 2)

Condition to be executed:-
i. >2 It should work normally.
ii. <2 Session should timeout.
iii. =2 It should take 2 min. (Work normally)
iv. When first request of component 2 is in process at the same time request of
component 2 and request of component 1is get at the same time. Then R𝑐1 1
is get executed.
(R𝑐1 1 → R𝑐1 2 ) R𝑐1 1 should execute first.
v. R𝑐1 1 = R𝑐2 1
 By default R𝑐1 1 should get executed.
2 min waiting is recovery.

Q. How you test it?

→ We sit along with component 1 and component 2 develops and we executed the
scenario.
Example:
Response from server is not getting so transaction is rollback.

ii. Compatibility Testing / Portability Testing:

During this test basically we validate/check Compatibility of our application with
other customer expected Platforms i.e. check whether our application runs with
different OS, browser or any system software’s.

Compatibility Testing is classified into:

a. Forward Compatibility
b. Backward Compatibility

When build is ok and there is problem in OS or browser then it is called forward

Compatibility.
If there is problem in application and OS or browser is ok then it is called backward
Compatibility.

Practically we get backward Compatibility defect as maximum.

Q. Which compatibility testing you involved?
→ In browser compatibility testing.

Basically browser compatibility testing is again divided into two parts:

a. Cross Browsing: IE Vs Chrome
b. Version Comparison: I7 Vs I8
Q. Suppose you want to test your application on different version of browser or
single machine. How you do version compatibility testing?
→ VMware (Virtual Machine)

Q. Difference between Oracle 9I, 10E, 12C.

→ Oracle 9I Oracle 10E Oracle 12C
I-Internet E-End C-Cloud

Q. What are things you covered in browser compatibility testing?

→ This testing used for front end validation
In this backend is absolutely zero we don’t touch backend
1. Functionality validation in terms of GUI
 2. Hyperlink accessibility
3. Page navigation
4. Tab validation

Q. What types of defect during browser compatibility?

→ In general we get environmental related defects and GUI related defects as
maximum
Examples of environment related defects –
• 404 not found
• Run time errors
• DLL file missing

iii. configuration testing/hardware compatibility testing:

It is also called as hardware compatibility testing

“During this testing we validate whether our app is support different types of
hardware devices and topologies.”
Topologies means stand alone, ring structure, mesh tree topologies
Topologies simply defines network infrastructures designed depends on
environmental factors and geographical factors.
LAN:local area network
WAN:wide area netwark
MAN:metropolition area network
e.g. Windows 8 supports laser printer
Hardware equipment (Router) supports ring structure.
Q. If HR ask about your company id and extension?
→ How does this question is related to my interview?
Practical example of compatibility testing:

It is used IE8 and Canada used mostly firebox and opera.

Compatibility of our application with IE8 and chrome this is cross browsing
My client want to launch the application in Canada then I have tested this by using
cross browsing and version compatibility testing mostly Canada people uses firebox
and opera that’s why I tested it on IE8 with opera and its version using VMware
Defect:
1) ‘Hyperlink’ is not getting accessible
2) ‘Run time error’ is getting displayed after click ok or ‘next’ hyperlink is customer
info page.
(what → when → where)

vi. Inter system testing:

x=y+5 → (when you get value of y then only you get value of x)
1. Basically we test co-existence of application with other existing software to
share the resources
2. Yes my application deals with multiple component’s I have involved in inter
testing . I involved in 2-3 components
3. Customer select mobile from flipkart i.e. main module then while making
payment that ordered send to payment domain. payment domain send respond
whether payment is successful or not. After successful payment request is
send to logistics module that deliver the mobile to customer. This is inter
system testing. i.e. until and unless payment domain send response ‘y’(i.e.
successful)then inly request (ordered)send to logistics module that deliver it
to customer.
Paytm is integrated with multiple components like light bill, water bill, telephone
bill…..etc.

v. Installation testing: (I never got chance but I know the concept)

‘During this test we validate installation of our application with other existing
software on customer expected performance.’
During installation testing we validate below factor:

i. Setup program execution before installation i.e. all file are available or not.
ii. Should have easy interface during installation.
iii. Check occupied space after installation.
iv. Check it should get easily uninstalled.

vi. Sanitation testing/garbage testing: (Yes I have involved in this)

During this testing we remove extra feature from application
i.e. In the future / enhancement phase, if customer faces any difficulty, we implement
the new functionality by demanding extra money
Example:
Successful req—file is uploaded successfully
Unsuccessful req—file is not uploaded
As per SRS success msg should be displayed but unsuccessful msg is not present
hence later it is considered as customer requirement.
Example:
Customer requirement is pdf, doc, excel, text, jpeg files should get uploaded but he
don’t tell us to add jpg format then feature you can demand extra money for adding
this feature
The conclusion of sanitization testing is even if the functionality or feature is correct
the extra thing should be recovered.

vii. Parallel testing/comparison: (I never got a chance to do parallel testing but

I know the concept)
It is also known as comparison testing.
It is only applicable for product.
During this testing we compare our application with other existing application in the
market in terms of feature
Paytm Paytm
5 rs per transition 4 rs per transition
Target amazon Target flipkart
e.g. Suppose we are testing one of e-commerce app then we should compare it with
amazon and flipkart.

3. Globalization testing/language compatibility:

when it deals with international language like Chinese, French, Russian is known as
nationalization testing.
when it deals with local language like Marathi, Hindi, Gujarati, Kannada, Telegu is
known as localization testing.
This is also known as language compatibility testing.
“During this test language compatibility of our application, i.e. we have to check
whether our application supports with multi-language characters.”

Application: Designed for specific client

Product: Product is made for multiple clients
Example: HDFC website is the application designed for only HDFC bank
Paytm, Bhim, Billdesk, Phonepay is a product because everybody can use it.

Live example of globalization:

Req. is for 3 months
Note: During globalization testing we don’t touch backend i.e. Backend testing cant
be performed. i.e. validation should be performed only on front end.
During globalization testing we perform:
1) Functionality
2) Page navigation
3) GUI validation
4) Tab validation
5) Hyperlink accessibility /line validation
Live requirement: (3 months)
Which language is compatible with us:-Epsanol(Spanish language)
Customer requirement:-
1)when we access BOA site epsanol should be hyperlinked by default
2)account values should be in English but label get changed according to language

Q. During globalization testing whether you want to know about other

language? (e.g. Spanish)
→ Yes I need to concentrate whether it is getting changed or not. We should not
focus on what is exact meaning.

Practical implementation of globalization:

Req is 3 months.
Compatibility with English with French.
My client want to deploy application in Canada in Canada some people speak
English as well as French so required application should compatible with English
and French.
Testing Terminology:

1. Monkey Testing:
It is also called as Gorilla, Chimpanji, speed testing.
“During this test we validate conduct test on basic or core functionalities of the
application w.r.t customer requirement.”
i.e. we have to concentrate on high priority test cases.

- Practically maximum no. of text cases need to be execute & w.r.t minimum time
period. Through which we cover all core functionalities.

Q. If you have pro test cases needs to be executed and tomorrow is delivery.
What will be your approach?
→ Yes. I think we need to execute high priority test cases to cover the core
functionality.
 2. Exploratory testing:
Level by level functionality coverage is called as exploratory testing.
E.g. Study unknown project step by step and performance the testing.

Q. If you act aware about functionality or application, what is your approach?

→ Yes in this situation we have to cover one by one functionality coverage, i.e. we
can call it exploratory testing.
E.g. If you have experience in telecom domain and how you are working banking
domain then exploratory testing is used.

3. Adhoc testing:
Q. If you are aware about functionality but you don’t have into about test data then
what will be your approach
→ As I am aware about functionality and with the help of my past experience, I am
going to test the application functionality.
e.g.

Same functionality but difficult test data (In this you know about the NEFT
functionality and how in INPS is added, its functionality is same but we don’t have
to test data to test the INPS functionality in this case we can use adhoc testing.)
Let new functionality comes or new application comes, we are aware about the
functionality of requirement, but we don’t have sufficient test data to test it.

Q. Difference between exploratory and adhoc testing.

1. Big Bang Testing
( I never got a chance in this test.)
Big bang means one big test.
i.e. During big bang testing we concentrate on a major functionality from start to
end.
After completion of entire software development, testing team concentrate on a
single stage instead of multiple Stages.
It is also called as informal testing
Q. what is inspection / walkthrough / Informal test / Big bang Test .
→ Practical example:
Customer registration
A/C view
ADD beneficiary
Transaction

In this we only test major functionality i.e. transaction, no need to test customer
requirement, account view, add beneficiary as these functionality are dependent i.e.
transaction is working fine then all other functionality are also working.

Just test billing then no need to test Network, TIBCO and CRM.
As CRM, TIBCO, Network and billing is interdependent i.e. billing is working fine
then CRM, TIBCO and Network working fine.