You are on page 1of 32

Manual testing interview question and answer, PART 1

1. differentiate between QA and QC?


QA:It is process oriented
it evolve in entire process of software development.
Preventin oriented.
QC:
It is product oriented.
work to examin the quality of product.
Dedection orientd.

2.what is a bug?
A computer bug is an error, flaw, mistake, failure, or fault in a computer program
that prevents it from working correctly or produces an incorrect result.

3.what is a test case?


Testcase is set of input values, execution preconditions,expected results and
execution
postconditions, developed for a particular objective or test conditons, such as to
exercise a paticular program path or to verify compliance with a specific requiremnt.

4.What is the purpose of test plan in your project?


test plan document is prepared by the test lead,it contains the contents like
introduction,objectives,test stratergy,scope,test items,program modules user
procedures,features to be tested features not to tested approach,pass or fail
criteria,testing process,test
deliverables,testing,tasks,responsibilities,resources,schedu
le,environmental requirements,risks & contingencies,change management
procedures,plan approvals,etc all these things help a test manager undersatnd the
testing he should do &
what he should follow for testing that particular project.

5.When the relationship occur between tester and developer?


developer is the one who sends the application to the tester by doing all the
necessary code in the application and sends the marshal id to the tester.The tester is
the one who gives all the input/output and checks whether he is getting reqd output
or not.A developer is the one who works on inside interfacing where as the tester is
the one who works on outside interfacing

6.when testing will starts in a project?


the testing is not getting started after the coding.after release the build the testers
perform the smoke test.smoke test is the first test which is done by the testing
team.this is according to the testing team.but, before the releasing of a build the
developers will perform the unit testing.

7.If a bug has high severity then usually that is treated as high priority,then
why do priority given by testengineers/project managers and severity given
by testers?
High severity bugs affects the end users ....testers tests an application with the users
point of view, hence it is given as high severity.High priority is given to the bugs
which affects the production.Project managers assign a high priority based on
production point of view.

8.what is the difference between functional testing and regresion testing


functional testing is a testing process where we test the functionality/behaviour of
each functional component of the application...i.e.minimize button,transfer
button,links etc.i.e we check what is each component doing in that application...
regression testing is the testing the behaviour of the application of the unchanged
areas when there is a change in the build.i.e we chk whether the changed
requirement has altered the behaviour of the unchanged areas.the impacted area
may be the whole of the application or
some part of the application...

10.do u know abt integration testing,how do u intregate diff modules?


integration testing means testing an application to verify the data flows between the
module.for example, when you are testing a bank application ,in account balence it
shows the
100$as the available balence.but in database it shows the 120$. main thing is
"integration done by the developers and integration testing done by the testers"
11.do u know abt configuration management tool,what is the purpose of
maintaining all the documents in configuration manage ment tool?
It is focused primarily on maintaining the file changes in the history.
Documents are subjected to change For ex: consider the Test case document .
Initially you draft the Test cases document and place it in Version control tool(Visual
Source Safe for ex).Then you send it for Peer Review .They will provide some
comments and that document will be saved in VSS again.Similary the document
undergoes changes and all the changes history will be maintained in Version control.
It helps in referring to the previous version of a document.
Also one person can work on a document (by checking out) at a time.
Also it keeps track who has done the changes ,time and date.
Generally all the Test Plan, Test cases,Automation desgin docs are placed in VSS.
Proper access rights needs to be given so that the documents dont get deleted or
modified.

12.How you test database and explain the procedure?


Database Testing is purely done based on the requirements. You may generalize a
few features but they won't be complete. In general we look at
1. Data Correctness (Defaults)
2. Data Storage/Retreival
3. Database Connectivity (across multiple platforms)
4. Database Indexing
5. Data Integrity
6. Data Security

13.suppose if you press a link in yahooshopping site in leads to some other


company website?how to test if any problem in linking from one site to
another site?
1)first i will check whether the mouse cusor is turning into hand icon or not?
2)i will check the link is highlingting when i place the curosr on the link or not?
3)the site is opening or not?
4)if the site is opening then i will check is it opening in another window or the same
window that the link itself exitst(to check userfriendly ness of the link)
5)how fast that website is opening?
6)is the correct site is opening according to the link?
7)all the items in the site are opeing or not?
8)all other sublinks are opening or not?
14.what are the contents of FRS?
F → Function Behaviours
R → Requirements (Outputs) of the System that is defined.
S → Specification ( How, What, When, Where, and Way it behavior's.
FRS → Function Requirement Specification.
This is a Document which contains the Functional behavior
of the system or a feature. This document is also know as EBS External Behaviour
Specification. Document. Or EFS External Function Specification.

15.what is meant by Priority nad severity?


Priority means "Importance of the defect w.r.t cutomer requirement"
Severity means "Seriousness of the defect w.r.t functionality"

Manual testing interview question and answer, PART 2


16.what is meant by Priority nad severity?
Severity:
1. This is assigned by the Test Engineer
2. This is to say how badly the devation that is occuring is affecting the other
modules of the build or release.
Priority:
1. This is assigned by the Developer.
2. This is to say how soon the bug as to be fixed in the main code, so that it pass the
basic requirement.
Eg., The code is to generate some values with some vaild input conditions. The
priority will be assigned so based on the following conditions:
a> It is not accepting any value
b> It is accepting value but output is in non-defined format (say Unicode
Characters).
A good example i used some unicode characters to generate a left defined arrow, it
displayed correctly but after saving changes it gave some address value from the
stack of this server. For more information mail me i will let you know.

17.give me some example for high severity and low priority defect?
if suppose the title of the particular concern is not spelled corectly,it would give a
negative impact.eg ICICC is spelled as a tittle for the project of the concern
ICICI.then it is a high severity,low priority defect.

18.what is basis for testcase review?


the main basis for the test case review is
1.testing techniques oriented review
2.requirements oriented review
3.defects oriented review.

19.what are the contents of SRS documents?


Software requirements specifications and Functional requirements specifications.

20.What is difference between the Web application testing and Client Server
testing?
Testing the application in intranet(withoutbrowser) is an example for client -server.
(The company firewalls for the server are not open to outside world. Outside people
cannot access the application.)So there will be limited number of people using that
application.
Testing an application in internet(using browser) is called webtesting. The application
which is accessable by numerous numbers around the world(World wide web.)
So testing web application, apart from the above said two testings there are many
other testings to be done depending on the type of web application we are testing.
If it is a secured application (like banking site- we go for security testing etc.)
If it is a ecommerce testing application we go for Usability etc.. testings.

21.Explain your web application archtechture?


web application is tested in 3 phases
1. web tier testing --> browser compatibility
2. middle tier testing --> functionality, security
3. data base tier testing --> database integrity, contents

22.suppose the product/appication has to deliver to client at 5.00PM,At that


time you or your team member caught a high severity defect at 3PM.
(Remember defect is high severity)But the the client is cannot wait for long
time.You should deliver the product at 5.00Pm exactly.then what is the
procedure you follow?
the bug is high severity only so we send the application to the client and find out the
severity is preyority or not. if its preyority then we ask him to wait.
Here we found defects/bugs in the last minute of the deliveryor realese date
Then we have two options
1.explain the situation to client and ask some more time to fix the bug.
2.If the client is not ready to give some some time then analyse the impact of
defect/bug and try to find workarounds for the defect and mention these issues in
the release notes as known issues or known limitations or known bugs. Here the
workaround means remeady process to be followed to overcome the defect effect.
3.Normally this known issues or known limitations(defects) will be fixed in next
version or next release of the software

23.Give me examples for high priority and low severity defects?


Suppose in one banking application there is one module ATM Facility. in that ATM
facility when ever we are dipositing/withdrawing money it is not showing any
conformation message but actually at the back end it is happening properly with out
any mistake means only missing
of message . in this case as it is happenig properly so there is nothing wrong with
the application but as end user is not getting any conformation message so he/she
will be
confuse for this.So we can consider this issue as HIGH Priority but LOW Severity
defects..

24.Explain about Bug life cycle?


1)tester->
2) open defect->
3)send to developer
4)->if accepted moves to step5 else sends the bug to tester gain
5)fixed by developer ->
6)regression testing->
7)no problem inbuilt and signoff
8)->if problem in built reopen the issue send to step3

25.How can you report the defect using excel sheet?


To report the defect using excel sheet
Mention : The Feture that been effected.
mention : Test Case ID (Which fail you can even mention any other which are
dependency on this bug)
Mention : Actual Behavior
Mention : Expected Behavior as mentioned in Test Case or EFS or EBS or SRS
document with section
Mention : Your Test Setup used during Testing
Mention : Steps to Re-Produce the bug
Mention : Additional Info
Mention : Attach a Screen Shot if it is a GUI bug
Mention : Which other features it is blocking because of this bug that you are unable
to
execute the test cases.
Mention : How much time you took to execute that test case or follow that specific
TC
which leaded to bug

26.If you have executed 100 test cases ,every test case passed but apart
from these testcase you found some defect for which testcase is not
prepared,thwn how you can report the bug?

While reporting this bug into bugtracking tool you will generate the testcase imean
put the steps to reproduce the bug.

27.what is the diffn betn web based application and client server application
The basic difference between web based application & client server application is that
the web application are 3 trier & client based are 2 trier.In web based changes are
made at one place & it is refelected on other layers also whereas client based
separate changes need be installed on client machine also.

28.what is testplan? and can you tell the testplan contents?


Test plan is a high level document which explains the test strategy,time lines and
available resources in detail.Typically a test plan contains:
-Objective
-Test strategy
-Resources
-Entry criteria
-Exit criteria
-Use cases/Test cases
-Tasks
-Features to be tested and not tested
-Risks/Assumptions.
29.How many testcases can you write per a day, an average figure?
Complex test cases 4-7 per day
Medium test cases 10-15 per day
Normal test cases 20-30 per day

30.Who will prepare FRS(functional requirement documents)?


What is the importent of FRS?
The Business Analyst will pre pare the FRS.
Based on this we are going to prepare test cases.
It contains
1. Over view of the project
2. Page elements of the Application(Filed Names)
3. Proto type of the of the application
4. Business rules and Error States
5. Data Flow diagrams
6. Use cases contains Actor and Actions and System Responces

Manual testing interview question and answer, PART 3


31.How you can decide the number of testcases are enough for testing the
given module?
The developed test cases are coverd all the functionality of the application we can
say testcases are enough.If u know the functionality covered or not u can use RTM.

32.What is the difference between Retesting and Data Driven Testing?


Retesting:it is manual process in which apllication will be tested with entire new set
of data.
DataDriven Testing(DDT)-It is a Automated testing process inwhich application is
tested with multiple test data.DDT is very easy procedure than retesting because the
tester should sit and need to give different new inputsmanually from front end and it
is very tedious and boring
prodedure.

33.what is regression testing?


After the Bug fixed ,testing the application whether the fixed bug is affecting
remaining functionality of the application or not.Majorly in regression testing Bug
fixed module and it's
connected modules are checked for thier integrity after bug fixation.

34.how do u test web application?


Web applicatio testing
web application shold have the following features like
1.Attractive User Interface(logos,fonts,alignment)
2.High Usability options
3.Securiry features(if it has login feature)
4.Database(back end).
5.Perfromance(appearing speed of the application on client system)
6.Able to work on different Browers(Browser compatibility)
,O.S compatibility(technicalled called as portability)
7.Broken link testing.........etc
so we need to follow out the following test strategy.
1.Functionality Testing
2.Performance Testing(Load,volume,Stress,Scalability)
3.Usability Testing
4.User Interface Testing(colors,fonts,alignments...)
5.Security Testing
6.Browser compatibility Testing(differnt versions and different browser)
7.Brokenlink and Navigation Testing
8.Database(backend)Testing(data integrity)
9.Portability testing(Multi O.s Support)....etc

35.how do u perform regression testing,means what test cases u select for


regression
Regression testing will be conducted after any bug fixedor any functionality changed.
During defect fixing procedure some part of coding may be changed or functionality
may be manipulated.In this case the old testcases will be updated or completely re
written
according to new features of the application where bug fixed area.Here possible
areas are old test cases will be executed as usual or some new testcases will be
added to existing testcases or some testcases may be deleted.

36.what r the client side scripting languages and server side scripting
languages
client side scripting langages are
javascript,VbScript,PHP...etc
Server side Scripting languages are
Perl,JSP,ASP,PHP..etc
Clent side scipting languages are useful to validate the inputs or user actions from
userside or client side.
Server side Scripting languages are to validate the inputs at server side.
This scripting languages provide security for the application. and also provides
dynamic nature to web or client server application
cleint side scripting is good because it won't send the unwanted input's to server for
validation.from frontend it self it validated the user inputs and restricts the user
activities and guides him

37.if a very low defect (user interface )is detected by u and the developer
not compramising with that defect what will u do?
user interface defect is a high visibility defect and easy to reproduce.
Follow the below procedure
1.Reproduce the defect
2.Capture the defect screen shots
3.Document the proper inputs that you are used to get the defect in the derfect
report
3.send the defect report with screen shots,i/ps and procedure for defect
reproduction.
before going to this you must check your computer hard ware configuration that is
same as developper system configuration.and anlso check the system graphic drivers
are properly
installed or not.if the problem in graphic drivers the User interface error will come.
so first check your side if it is correct from your sidethen report the defect by
following the above method.

38.if u r only person in the office and client asked u for some changes and u
didn,t get what the client asked for what will u do?
Onething here is very important.Nobody will ask test engineer to change software
that is
not your duty,even if it is related to testing and anybody is not there try to listen
care fully if you are not understand ask him again and inform to the corresponding
people immediately.
Here the cleint need speedy service,we(our company) should not get any blame from
customer side.
39.how to get top two salaries from employee tables
Select * from emp e where 2>=(select count(*) from emp e where sal>e.sal) order
by desc sal.

40.How many Test-Cases can be written for the calculator having 0-9
buttons, Add,Equalto buttons.The testcases should be focussed only on add-
functionality but mot GUI.What are those test-cases?
Test-Cases for the calculator
so here we have 12 buttons totalie 0,1,2,3,4,5,6,7,8,9,ADD,Equalto -12 buttons
here u can press atleat 4 buttons at a time minimum for example 0+1= for zero u
should press 'zero' labled buttonfor plus u should press '+' labled buttonfor one u
should press 'one' labled buttonfor equalto u should press 'equalto' labled button
0+1=here + and = positions will not varyso first number position can be varied from
0 to 9 i.e from permutation and combinations u can fill that space in 10 waysin the
same waysecond number position can be varied from 0 to 9 i.e from permutation
and combinations u can fill that space in 10 ways
Total number of possibilities are =10x10=100
This is exhaustive testing methodology and this is not possible in all cases.
In mathematics we have one policy that the the function satisfies the starting and
ending values of a range then it can satisfy for entire range of values from starting to
ending.
then we check the starting conditions i.e one test case for '0+0=' (expected values
you know thatis '0')then another testcase for '9+9='(expected values you know
thatis '18')only two testcases are enough to test the calculator functionality.

41.what is positive and negative testing explian with example?


Positive Testing. testing the system by giving the valid data.

Negative Testing. testing the system by giving the Invalid data.


For Ex,an application contains a textbox and as per the user's Requirements the
textbox should accept only Strings.By providing only String as input data to the
textbox & to check whether its working properly or not means it is Positive Testing.If
giving the input other than String means it is negative Testing..

42.How will you prepare Test plan. What are the techniques involved in
preparing the Test plan.
Test plan means planning for the release. This includes Project background
Test Objectives: Brief overview and description of the document
Test Scope: setting the boundaries
Features being tested (Functionalities)
Hardware requirements
Software requirements
Entrance Criteria (When to start testing):
Test environment established, Builder received from developer, Test case prepared
and reviewed.
Exit criteria (when to stop testing):
All bug status cycle are closed, all functionalities are tested, and all high and medium
bugs are resolved.
Project milestones: dead lines

43.What are the Defect Life Cycle?


Defect life cycle is also called as bug life cycle. It has 6stages namely
1.new: found new bug
2.assigned: bud assigned to developer
3.open : developer is fixing the bug
4.fixed : developer has fixed the bug
5.retest: tester retests the application
6.closed/reopened: if it is ok tester gives closed stauselse he reopens and sends
back to developer.

44.Expalin about metrics Management?


Metrics: is nothing but a measurement analysis.Measurment analysis and
Improvement is one of the process area in CMM I L2.

45.What is performance Testing and Regression Testing?


Performance Testing:-testing the present wroking condition of the product
Regression Testing:-Regression Testing is checking for the newly added functionality
causing any erros interms of functionality and the common functionality should be
stable
in the latest and the previous versions

Manual testing interview question and answer, PART 4


46.How do you review testcase?? Type of Review...
types of reviewing testcases depends upon company standards,viz..,
peer review,team lead review,roject manager review.
Some times client may also review the test cases reg what is approach following for
project

47.In which way tester get Build A, BUild B, ....Build Z of an application, just
explain the process..
After preparation of testcases project manager will release software release note in
that Document there will be URL path of the website link from from that we will
receive
the build In case of web server projects, you will be provided with an URL or a
92.168.***.*** (Web address) which will help you access the project using a
browser from your system.

In case of Client server, the build is placed in the VSS (Configuration tool) which will
help you get the .exe downloaded to your computer.

48.apart from bug reporting wat is ur involvement in projectlife cycle


As a Test engineer We design test cases,prepare testcases Execute Testcases, track
the bugs, analyse the results report the bugs. invovled in regression testing,
performance of system
testing system intergration testing At last preparation of Test summary Report
49.contents of test report
There are two documents,which should be prepared at particual phase.
1.Test Results document.
2.Test Report document.
Test Results doc will be preapred at the phase of each type of Testing like FULL
FUNCTIONAL TEST PASS,REGRESSION TEST PASS,SANITY TEST PASS etc...Test case
execution againest
the application.Once you prepared this doc,we will send the doc to our TL and PM.By
seeing the Test Results doc ,TL will come to know the coverage part of the
testcase.Here I
am giving you the contents used in the Test Results doc.

1.Build No
2.Version Name
3.Client OS
4.Feature set
5.Main Feature
6.Defined Testcases on each feature.
7.QA engineer Name
8.Test ecases executed.(Includes pass and fail)
9.Testcases on HOLD(Includes blocking testcases and deferred Testcases)
10.Covereage Report(Which includes the coverage ratings in % ,like % of testcases
covered,% of testcases failed)

Coming to Test report,generally we will prepare Test report ,once we rolled out the
product to our client.This document will be prepared by TL and delivered to the
client.Mainly,this document describes the what we have done in the
project,chievements we have reached,our
learnings in throughout the project etc...The other name for Test report is Project
Closure Report and we will summerize the all the activities,which have taken place in
through out the project.Here I am giving your the contents covered in the Test
Report.
1.Test Environment(Should be covered the OS,Application or webservers,Mahchine
names,Database,etc...)
2.Test Methods(Types of Tests,we have done in the project like Functional
Testing,Platform Testing,regression Testing,etc..
3.Major areas Covered.
4.Bug Tracking Details.(Includes inflow and outflow of the bus in our delivered
project)
5.Work schedule(When we start the testing and we finished)
6.Defect Analasys
6.1 Defects logged in different types of tests like Funcational Test,regressiion Test as
per area wised.
6.2 State of the Defects at end of the Test cycle.
6.3 Root cause analysys for the bugs marked as NOT A BUG.
7.QA observations or learnings throught the life cycle.

50.write high level test cases


Write all the testcases under high level TC,which can be covered the main
functionalities like
creation,edition,deletion,etc....as per prescribed in the screen.
Wrtie all the testcases under low level TC,which can be covered the screen,like input
fields are displayed as per the requirements,buttons are enabled or disabled,and
testcase for low priority functionalities.
Example a screen contains two edit boxes login and password and a pust buttons OK
and Reset and check box for the label "Remember my password".Now let us write
high level TC
and low level test cases.

HIGH LEVEL TC
1.Verify that User is able to login with valid login and valid password.
2.Verify that User is not able to login with invalid login and valid password.
etc...
..
3.Verify that Reset button clears the filled screen.
4.Verify that a pop up message is displayed for blank login.
etc...
etc..

LOW LEVEL TC
1.Verify that after launching the URL of the application below fields are displayes in
the screen.
1.Login Name 2.Password.3.OK BUTTON 4.RESET button etc..
5.check box,provided for the label "remember my pwd" is unchecked.
2.Verify that OK button should be disabled before selecting login and passwrod
fields.
3.Verify that OK button should ne enabled after selecting login and password.
4.Verify that User is able to check the check box,providedfor the label "remember my
pwd".
etc..
In this way,we can categorise all the testcases under HIGH LEVEL and LOW LEVEL.

51.wat is test scenario


Test scenario will be framed on basis of the requrement,which need to be
checked.For that,we will frame set of testcases,in other terms,we can say all the
conditions,which can be determined the testing coverage againest business
requirement.
Please see the below example,which is exactly matched to my explanation.
As we know all most all the application are having login screen,which contains login
name and password.Here is the test scenario for login screen.
Scenario: USER'S LOGIN
Condtions to be checked to test the above scenario:
----------------------------------------------------
1.Test login field and Password fields indicisually.
2.Try to login with valid login and valid password.
3.Try to login with invaling login and valid pwd. etcc........................................

52.wat is build duration


it is a tine gap between old version build and new version build in new version build
some new extra features are added

53.wat is test deliverables


Test deliverables are nothing but documents preparing after testing like test plan
document testcase template bugreport templateTest deliverables will be delivered to
the client not only for the completed activities ,but also for the activites,which we are
implementing for the better productivity.(As per the company's standards).Here I am
giving you some of the Test deliverables in my project.
1.QA TestPlan
2.Testcase Docs

3.QA Testplan,if we are using Automation.


4.Automation scripts
5.QA Coverage Matrix and defect matrix.
6.Traceability Matrix
7.Test Results doc
8.QA Schesule doc(describes the deadlines)
9.Test Report or Project Closure Report.(Prepared once we rolled out the project to
client)
10.Weekly status report(sent by PM to the client)
11.Release Notes.

54.wat is ur involvement in test plan


Test lead is involved in preparing test plan test entgineers are no way related in
preparing test plan role TE is testcase design ,and execution and bugtraking and
reporting them Genarally TL is involed in preparation of the TestPlan.But it is not
mandatory only TL will take main part in the preparaion of the TP.Test engineer can
suggest to TL,if he(or) she has good understanding on project and resources,if he or
she has more exp with the project,if TL is wrongly given deadlines.If your
suggestions are valid,TL will incorporate all of them to the TestPlan.But in most of
the companies Test engineers are just audians.

55.which test cases are not to be automated


All the test cases which are related to a feature of the product, that keeps on
changing (there are always some or the other enhancements in it). Frequent
enhancements may change the UI, add/remove few controls. Hence such cases, if
automated, would involve lot of a intenance

56.if a project is long term project , requirements are also changes then test
plan will change or not?why
Yes..definitely. If requirement changes, the design documents, specifications (for
that particualr module which implements the requiremnts) will also change. Hence
the test plan would also need to be updated. This is because "REsource Allocation" is
one section in the test
plan. We would need to write new test cases,review, and execute it. Hence resource
allocation would have to be done accordingly. As a result the Test plan would change

57.explain VSS
Virtual Sourse Safe...
After complition of all phages From devolopment side devoloper store the code in
devolopment folder of VSS,Testing team copying code from that folder to testing
folder, after compliting above phages from testing, testers put the build in base line
folder.It is version contrrole Tool
Mainly useful to devoloper, to storing code and maintains version Copying a code
from VSS By devoloper is called CHECK-IN Upload the code in to VSS is called
CHECK-OUT.

58.who will assign severity & priority


the tester/dev should give the priority based on severity of the bug
Severity means: is the impact of the bug on the app.i.e seriousness of the bug
interms of the functionality.
Priority means: is how soon it should get fixed i.e importance of the bug interms of
customer

59.What is the Difference between Stub Testing and Driver Testing?


stub testing:
In top down approach,a core module is developed.to test that core module, small
dummy modules r used.so stubs r small dummy modules that test the core module.
Driver testing:
in bottom up approach, small modules r developed.to test them a dummy core
module called driver is developed.

60.What is a "Good Tester"?


Is one who tries to break the developers software and in a position to venture the
bugs. so that atleast 80% bugs free software can deliver.

Manual testing interview question and answer, PART 5


61.wat is cookie And Session testing ????
A small text file of information that certain Web sites attach to a user's hard drive
while the user is browsing the Web site. A Cookie can contain information such as
user ID, user preferences, archive shopping cart information, etc. Cookies can
contain Personally Identifiable
Information.Session is a connection between a server and client.

62.how would u do performance Testing manually for web site.


By noting the time to load apge or perform any action with stop watch. I know it
sounds funny but this is the way performance is tested manualy.

63.what is usecase? tell me the attribute of usecase?


" Use Case is desription of functionality certain features of an application interms of
Actors, actions and responibilities."
Use Case attributes are:
1. Information of Document, 2. Description, 3. Objective, 4. Actors, 5.Pre-conditions,
6.Data-element desriptions, 7.post conditions, 8.primary flow, 9. Alternative flow
and Business rules/interaction implimentations and etc....

64.What is the difference between stress, volume and load testing?


Load Testing:V gradualy increase the load and check the performance of the
application .v check at what point or maximum load application can sustain.
stress testing:In this testing v check the performance of application under extrime
condion which rarely occurs like
(1)Many concurrent user access the application for short time.
(2)extra ordinary long transction.
(3)very short transaction repeted quckly.

65.when will do the beta test?when will do the alpha test?


Alpha and Beta tests comes under User acceptance test. We will conduct these two
system being released.we are giving oppurtunity to customer to check all functiolities
covered or not.
Alpha testing conducting for software application by real customer at development
site.
Beta testing conducting for software product by model customer at customer site.

66.How do you select test cases for Regression Testing(The point is when
there is change code how do you come know which part of code or modules
it will affect).
Consider an example of a form which has a username,password and and Login
button.
There is a code change and a new button "Reset" is introduced. Regression
testing(for that build) will include testing only the "Login" button and not the Reset
button (testing Reset button will be a part of cunation testing). Hence the Regression
tester need not worry about the change in code,functionality. But he has to make
sure that the existing functionality is working as desired.Testing of "Reset" button
will be included as a part of Regression, for the next build

67.can any one explain the example of high servity and low priority, low
servity and high priority, high servity andhigh priority, low servity and low
priority
1.high severity and high priority. Database connectivity cannot be established by
multiple users.
2. low severity and low priority. Small issues like, incorrect number of decimal digits
in the output.
3. low severity and high priority. Images not updated.
4. high severity and low priority. In a module of say 2 interfaces, the link between
them is broken or is not functioning.
(1)High priority & High Severity:If u click on explorer icon or any other icon then
system crash.
(2)low prority & low severity:In login window ,spell of ok button is "Ko".
(3)Low priority & high serverty:In login window ,there is an restruction login name
should be 8 character if user enter 9 or than 9 in that case system get cresh.
(4)High priority & low severty :Suppose logo of any brand company is not proper in
their product.so it affect their business.
68.what will be the Test case for ATM Machine & Coffe Machine?
test cases for ATM Machine
1.successful insection of ATM card
2.un successful operation due to insert card in wrong angle
3.un successful operation due to invalid account Ex:other bank card or time expired
card
4.successful entry of PIN number
5.un successful operation due to enter wronr PIN number 3times
6.successful selection of language
7.successful selection of account type
8.un successful operation due to invalid account type
10.successful selection of withdral operation
11.successful selection of amount to be withdral
12.successful withdral operation
13.unsuccessful withdral operation due to wrong denominations
14. unsuccessful withdral operation due to amount is greaterthan day limit
15.unsuccessful withdral operation due to lack of money in ATM
16. unsuccessful withdral operation due to amount is greaterthan possible balance
17.unsuccessful withdral operation due to transactions is greaterthan day limit
18. unsuccessful withdral operation due to click cancel after insert card
19.unsuccessful withdral operation due to click cancel after insert card & pin number
20.unsuccessful withdral operation due to click cancel after insert card , pin number
& language
21.unsuccessful withdral operation due to click cancel after insert card , pin number ,
language &account type
22.unsuccessful withdral operation due to click cancel after insert card , pin number ,
language ,account type & withdral operation
23.unsuccessful withdral operation due to click cancel after insert card , pin number ,
language ,account type ,withdral operation &amount to be withdral

69.Tell me abuot your daily activities as a test engineer.


Role:
1.Understanding the BRS and Usecases Document
2.Giving system demo to PM, System analyst, designer, Dev lead.
3.Preparing the Test Actions in xls sheet.
4.Updating the Test Actions based on review commnets by System analyst/Business
Analyst.
5.Preparing the Testcases and Datasets(System level and global level datasets) in
word document
6.updating the Test Cases based on review comments by System analyst.
7.Installing the application-Testing environment set up.
8.Performing Functional,GUI,System,Compatibility testing(If necessary), Regression
testing based on Test cases
9.Preparing the defect report, Bug tracking list and sending daily status report to PM,
leads.

70.in sdlc process what is the rool of PM,TL,DEVELOPER,tester in each and


every phase? pelese explain me in detail?
in the sdlc we have these phases
1. initial phase
2.analysis phase
3.designing phase
4.coding phase

5.testing
6.delivery and maintainance

In the initial phase project manager can prepare a document for the requirements,
team leader will prepare a team which is having test engineers, developer will
provided by the project manager, testee will prepare test cases for that particular
project
Analysis phase all the members have a meeting to finalise the technology to develop
that project, the employee, time ,...
Designing phase the project manager like senior level management will give the
directions and source code to the team members to develop the actual code, that is
guidelines will be given in this phase
Coding phase developer will develop the actual code using the source code and they
release the application to the testee
Testing phase they deploy their test cases to that application and prepare a bug
profile document if there is any defect/bug in that application and send it back to
developer, developer may rectify and releases tha application as nezt build and if the
bug not undestand it will send to the prject lead in the delivery phase the sr test eng
can deploy the application in the client environment
Maintainance phase if the client get any prblem with the application it may solved by
the prject lead withe help of testers and developers

71.How do You Test Application with having any requirement and


Document?
If it is an existing system or if a build is available thenwe explore the system while
testing. This helps knowing thefunctional use of the system, and its usability.
By asking questions to end users and how they use it will bemore beneficial. Also,
you may work with BA to know moreabout the system.
Black box test is nothing but the same where you explore the system without having
any prior knowledge to the system.

72.what is backend testing using SQL?


Executing SQL statements to check if the data submitted by aGUI program is
updated in the database or not?Eecuting the statement the data base is connecting
to that particular changes , updations or not it will test.Backend testing is the testing
the integration between the applicationa and the database. It is checking the
changes made in the database is getting reflected in the application.
Example: A new column is added in the table. Here we test by giving values in the
application and value has to be stored in the table.

73.What are the reasons why parameterization is necessary whenload


testing the Web server and the database server?
When you test your applications, you may want to check how the application
performs the same operations with multiple sets of data. For example, suppose you
want to check how
your Web site responds to ten separate sets of data. You could record ten separate
tests, each with its own set of data. Alternatively, you can create Data Table
parameters so that your test runs ten times, each time using a different set of data.

74.difference between sretagic test plan & test plan?


srategic test is a organisational level term which is applied for all the projects in the
organisation with small customisations
test plan is project level term and which can be applied for that specific project only.
test plan is a srategic document which describes how to perfoem testing in an
efficient effective and optimsed way.Quality lead test lead can prepare this test plan
strategic test plan is a already or new test plan which can bw used in the future for
another project also with some changes in the same organisation.

75.Draw Backs of automated testing?


DRAW BACKS OF AUTMATION
Epensive,lack of epertisation,all the areas we can not automate

Manual testing interview question and answer, PART 6


76.when will u make update and modify the test object properties in the
repository?
when ever the developer may change any one of the object properties definitely we
have to change the same in the OR object repository. if new version net build
released from the devlopment department wwe the test engs must to modify or
update the same is compulsary, other wise tha test will show the bug

77.what are the document needed to create a test case?How u tell it is test
case?
System requirements specification, Use case document, Test Plan
78.in customer details form having fields like customer name,customer
address. after completion of this module, client raise the change as insert
the two radio buttons after customer address. how you can check as a
tester.
1.First we need to verify wheater the radio button are there are not?
2.Conform the radio buttons are present after the customer address or not.
3.verify the no of radio button.
4. verify only one radio button should be checked intially when we open the
Customer details form(if it is mentioned in FS )
5. verify the functionality of the radio buttons i.e if we check one ratio button
,second radio button should be unchecked.
6. verify the spell check of radio button lable name.
7. verify the allignment of radio buttons in the form.

79.at the time of testing web based applications and client server
apllications, what you absorved as a tester?
We generally check for the links,data retrieving and posting.
We perform load and stress testing especially for Web based and Client-Server
applications.

80.What are the documents required to prepare test plan?


Introduction,scope,test team and their responsibilities,test environment,S/W&H/W
reqiurements,test data preparation,levels of
testing,seviroty&priority,shedule,risk,automation
plan,features to test,bug life cycle all these are documents of test plan.

81.what is testing policy and testing methodology? and what is the


difference?
Testing policy means all types of testing or testing techniques(i.e.functional
testing,sanity testing etc).Testing methodology means white box and black box
testing.

82.What is comparison testing?


Comparison Testing means comparing your software with the beter one or your
Competitor.
While comparisan Testing we basically compare the Performance of the software.For
ex If you have to do Comparison Testing of PDF converter(Desktop Based
Application) then you will compare your software with your Competitor on the basis
of:-
1.Speed of Conversion PDF file into Word.
2.Quality of converted file.

83.What is the general testing process?


Testing Process:
1. Tesdt requirements analysis
2. Creation of Test Strategy (Which includes creation of Test Cases)
3. Creation of Test Plans (Which includes Test Cases andTest Procedures)
4. Execution of test cases
5. Anlyze the test results
6. Report the defects if any

84.What particiption a manual tester can do in documentation?Are there


any tools available for only documentation?
yes, Manual tester will do Sub Test plan documents, as of my knowledge no tool is
used to prepare documentation

85.What is the difference between low and high level test cases? examples
please..
High level Test cases are those which covers major functionality in the application
(i.e retrive, update display ,cancel (functionality related testcases) ,database
testcases ).
Low level test cases are those which are related to UI related testcases.

86.Is it mandatory to use USECASES or directly one can write test casesfrom
requirments?
Its not mandatory to write Use Cases, If the requirements are clear you can go
ahead with Test Cases. Use Cases are written to know the business flow of the
module/application.

87.how do u develop test harness?

Test Environment+Test Bed


Test Environment:S/w and H/w
Test Bed:Test Documents like TestPlan Document ,Test Case Document.
Test Environment means
• Test Bed installation and configuration
• Network connectivity’s
• All the Software/ tools Installation and configuration
• Coordination with Vendors and others

88.given nrequirement collection doc,tester can prepare which test plan?


test lead can prepare a test plan which performs testing on an aplication in an
efficient effective and in an optimised way.test development will done by the testers
using the test
plan in the test plan they prepare the test strategy

89.tester with develop ment knowledge will be more effective .justify?


If tester has experience in Development, it will be useful when testing for logical
thinking where the error occurs, what is the cause? He can guess the functionality of
component? he can easily understand the application environment? those are plus
points which people have
development experience.
Precisely he can justify that either functionality is wrong or right and can analyze the
defects

90.last testcase for project will be written in which phase?


As far as the SDLC is conerned last test case Will be written for "Maintenance Phase"
As far as the STLC is conerned last test case Will be written for "Acceptance Testing"
Manual testing interview question and answer, PART 7
91.what is test scenario and test case ?please explain detail
Test Scenario:
Test scenario is like laying out plans for testing the product, environmental condition,
number of team members required, making test plans, making test cases and what
all features are to be tested for the product. Test scenario is very much dependent
on the product to be tested.
Test scenario is made before the actual testing starts.
Test Case:
Test case is a document which provides the steps to be executed which has been
planned earlier. It also depends on the type of product to be tested. Number of test
cases is
not fixed for any product.

92.What is the difference between Project Based Testing and Product Based
Testing?
Project based is nothing but client requirements. product based is nothing but
market requirements. Ex.striching shirt is a project based and ready made shirt is
product based
93.what is testing process in related to Application testing Testing process is the one
which tells you how the application should be tested in order to minimize the bugs in
the application.
One main thing no application can be released as bug free application which
impossible.

94.What is the difference b/n Testing Methodology and Testing methods?


Testing Methodology define process, set of rules and principle which are follow by
group concerned with Testing the application. Here i explain 7 step testing
methodology:
1.Test Requirement Analysis
2.Test Plan
3.Test Design
4.Test execute
5. defect track
6. Test Automation
7. Test Maintain
Testing methods or we can say that Testing Techniques:
White Box Testing (Unit Testing, Integration Testing)
Black Box Testing (System Testing, Functional Testing, Performance Testing>Load
testing>stress testing>volume testing & Security Testing)UAT (done by user/client
with actual/live data)

95.What are starting link to test while website testing?


Web based systems are those using the internet,intranet and extranets Web based
testing only needs be done once for any applications using the web.Web based
testing are as follows:
1.Functional correctness
2.Integration
3.Usability
4.Security
5.Performance
6.Verification of code
96.How GUI testing will be done in manual testing for a website?
For any testing there should be some set of standards to be followed.Particularly in
GUI testing,look and feel should be good. We should follow the requirements
specification documents for GUI testing.
There should be some screen shots (given by client) which we should follow as it is.
And for button sizes, font,font size ,colours used,placing of links,objects and the
placing of the objects in the page should be followed some standards.If we take a
button in the page that should be some standard size. if the size of that button is
more or less the client feel bad about that.So we should have miimum common
sence while tesing GUI testing. some time there may be some mistakes in the screen
shots provided by the client also,but that is our responsibility to raise those issues.

97.What thing should be tested in regresson testing?


While doing Regression Testing a tester must check that any New updation or
Modification or Change in Functionality of a Particular Component or Module does not
create any disorder and any negative affects on the functionality of the Application

98.What are the document required to prepare during testing?


Normally Test engineers are responsible for any release of a project.Even the release
is for staging environment or change request release or production release
The minimum documents are
1.Test Plan
2.Test Cases
3.Test Case Report
4.Bug report.
5.Release notes(which contains known issues).
6.installation document.

99.What is Test data ?Whrere we are using this in testing process?


what are the importance of this data?
to execute test cases we shold have test data.this test data should be for positive
and negative testings.for winrunner we can get this test data from keyboard,excel
sheets or from data base

100.what is the difference between test case and test script?


Test case is a descrption what data to be tested and what data to be inserted what
are the actions to be done to check actual result against expected resultWhat are the
actual inputs we will use? What are the expected results? is called test script
Test Script: Is a short program written in a programming language used to test part
of the functionality of the software system. a written set of steps that should be
performed manually
can also be called a test script,however this is more correctly called a test case.

101.What is the difference between bug,error,defect.


At the time of coding mistake error,when the mistake noticed by the tester
defect,tester sends this defect to development team if the developeragrees then it is
bug

102.what is the diffrence between qualityassurance and systemtesting


explain in detail with an example?
Quality Assurance: It is nothing but building an adequate confidence in the customer
that the developed software is accoding to requirements.Entire SDLC comes under
QA. It is process oriented.
System Testing: It is the process of executing entire system ie checking the s/w as
well as parts of system.

103.How do you decide when you have 'tested enough?'


When the 90% of requirements are covered , Maximum defects are rectified except
(some)low level defects are not covered , customer satisfy that project and time is
less, then we are closing the testing.

104. What is the difference between Build Management and Release


Management ?
When will conduct build verification and end to end testing?
Build Management is managing the issue fixture tasks in the bulds whereas Release
anagment is managing the functionality to be incorporated in the Release.
Build Verification Test(BVT)is done when the build is first received by the testers. The
basic functionality is checked with valid data. This is done to check whether the build
is testable or not. This is done by testers.
End to End testing is also called system testing. Done by Senior test engineers or
Test lead.

105.what is boudarary value analysis? what is the use of it?


boundry value analusis is a technique for test data selection.Test engineer chooses
the values that lie along the data extreems.It includes max,mim,justinside,justout
side,typicalvalues and errorvalues.
Boundary Value Analysis is a technique used for writing the test cases..for
example:If a particular field accepts the
values from 1 to 1000, then we test that field by entering only 1, 1000, 0, 1001,
999,2.
i.e we check on the boundaries and then
minimum-1 , minimum +1 and maximum+1, maximum-1.

Manual testing interview question and answer, PART 8


106.what is equivalence partition? what is the use of it?
Equalance nothing but select the valid and valid clases example as per client
requirement the edit box access onaly
3-5 capital alphabets then we divided in ecp like vaid values only A-Z invalid values
are a-z and special characters like ^,8<%

107.If there is no sufficent time for testing & u have to complete the testing
then what will u do?
When I have less time to test the Product then I will take these following steps---
1) Sanity or smoke testing
2) Usabilty Testing
3) Formal Functionaltyand GUI Testing
4) Walkthrough with the Prduct

108.What is meaning by protype in SDLC ?


This is a cyclic version of the linear model. In this model, once the requirement
analysis is done and the design for a prototype is made, the development process
gets started.Once the prototype is created, it is given to the customer for evaluation.
The customer tests the package and gives his/her feed back to the developer who
refines the product according to the customer's exact expectation. After a finite
number of iterations, the final software package is
given to the customer. In this methodology, the software is devolved as a result of
periodic shuttling of information between the customer and developer. This is the
most popular development model in the contemporary IT industry. Most of the
successful software products have been developed using this model. as it is very
difficult (even for a whiz kid!)
to comprehend all the requirements of a customer in one shot. There are many
variations of this model skewed with respect to the project management styles of the
companies.
New versions of a software product evolve as a result of prototyping.

109.what is difference between desktop and web application?


The biggest d/f b/w Desktop and web application is- Desktop App (DA) is the
machine independent, hence evry change has only reflects at the machine level.
Where as Web App (WA) is the Internet dependent program, hence any change in
the program reflects at every where, where it becomes use. EX......
Suppose there are 5 machines in DA, 5 time installedindividually at every machine
and if there is any change made in DA then at every machine change has to be
made. In WA where the program or Application at the Server or at the one common
machine, then if changes made at only central or server or common machine all the
changes get reflected at
every client machine.

110.diffrence between application testing and product testing?


Product testing means when any company does testing for their own (company's)
product ex... Nortan AntVirus is the Symantec's product; if Symantec test the Nortan
ie. called
as the Product testing. Where as if any company take some projects from some
other
companies like ABC company takes projects from IBM and test that project on some
charges ie called as Application Testing.

111.what is a broken link in web testing and how test it.


When we clicked on Hyperlink if it opens Page can't be displayed then that Hyperlink
is called as Broken link.

112. What are test case formats widely use in web based testing?
A. Web based applications deal with live web portals. Hence the test cases can be
broadly classified as. front end , back end, security testing cases, navigation based,
field validations, database related cases. The test cases are written based on the
functional specifications and wire-frames.

113. How to prepare test case and test description for job application?
A. Actually the question seems to be vague,... see naukri is one of biggest job site
globally and it has is own complex functionality normally a Test case is derived from
a SRS (or) FRS basically and test description is always derived from a Test case. Test
description is nothing but the steps which has to be followed for the TC what u
wrote. And the TC is nothing which compares the expectation and the
actual(outcome)result.

114. What is the difference between Functional and Technical bugs? Give an
example for each.?
Functional Bugs : Bugs found when Testing the Functionality of the AUT.
Technical bugs: Related to Communication which AUT makes.Like H/W,DB ! where
these could not be connected properly.

115. Give proper Seq. to following testing Types Regression, Retesting,


Funtional, Sanity and Performance Testing.?
A. The proper sequence in which these types of testing are performed is. Sanity,
Functional, Regression, Retesting, Performance.

116. How u test MS- Vista without any requirement Doc.?


Know what change is being made from the older verison of Windows to the newer
version with the help of User Release notes thats released with Windows Vista. Based
on that, formulate the test cases and execute the same.

117. What is verification? validation?


Verification typically involves reviews and meetings to evaluate documents, plans,
code, requirements, and specifications. This can be done with checklists, issues lists,
walkthroughs, and inspection meetings. Validation typically involves actual testing
and takes place after verifications are completed. The term 'IV & V' refers to
Independent Verification and Validation.

118. How can new Software QA processes be introduced in an existing


organization?
A lot depends on the size of the organization and the risks involved. For large
organizations with high-risk (in terms of lives or property) projects, serious
management buy-in is required and a formalized QA process is necessary.

Where the risk is lower, management and organizational buy-in and QA


implementation may be a slower, step-at-a-time process. QA processes should be
balanced with productivity so as to keep bureaucracy from getting out of hand.

For small groups or projects, a more ad-hoc process may be appropriate, depending
on the type of customers and projects. A lot will depend on team leads or managers,
feedback to developers, and ensuring adequate communications among customers,
managers, developers, and testers.

The most value for effort will often be in (a) requirements management processes,
with a goal of clear, complete, testable requirement specifications embodied in
requirements or design documentation, or in 'agile'-type environments extensive
continuous coordination with end-users, (b) design inspections and code inspections,
and (c) post-mortems/retrospectives.

119. Why is it often hard for management to get serious about quality
assurance?
Solving problems is a high-visibility process; preventing problems is low-visibility.
This is illustrated by an old parable: In ancient China there was a family of healers,
one of whom was known throughout the land and employed as a physician to a great
lord.

120. What's an 'inspection'?


An inspection is more formalized than a 'walkthrough', typically with 3-8 people
including a moderator, reader, and a recorder to take notes.
The subject of the inspection is typically a document such as a requirements spec or
a test plan, and the purpose is to find problems and see what's missing, not to fix
anything. Attendees should prepare for this type of meeting by reading thru the
document; most problems will be found during this preparation. The result of the
inspection meeting should be a written report.

Manual testing interview question and answer, PART 9


121. What is a 'walkthrough'?
A 'walkthrough' is an informal meeting for evaluation or informational purposes.
Little or no preparation is usually required.

122. What makes a good test engineer?


A good test engineer has a 'test to break' attitude, an ability to take the point of view
of the customer, a strong desire for quality, and an attention to detail. Tact and
diplomacy are useful in maintaining a cooperative relationship with developers, and
an ability to communicate with both technical (developers) and non-technical
(customers, management) people is useful. Previous software development
experience can be helpful as it provides a deeper understanding of the software
development process, gives the tester an appreciation for the developers' point of
view, and reduce the learning curve in automated test tool programming. Judgment
skills are needed to assess high-risk areas of an application on which to focus testing
efforts when time is limited.

123. What makes a good Software QA engineer?


The same qualities a good tester has are useful for a QA engineer. Additionally, they
must be able to understand the entire software development process and how it can
fit into the business approach and goals of the organization. Communication skills
and the ability to understand various sides of issues are important. In organizations
in the early stages of implementing QA processes, patience and diplomacy are
especially needed. An ability to find problems as well as to see 'what's missing' is
important for inspections and reviews.

124. What is agile testing?


Agile testing is used whenever customer requirements are changing dynamically
If we have no SRS, BRS but we have test cases does you execute the test cases
blindly or do you follow any other process.
Test case would have detail steps of what the application is supposed to do.
1) Functionality of application.
2) In addition you can refer to Backend, is mean look into the Database. To gain
more knowledge of the application.

125. When would you perform regression testing?


This depends on the requirements and the lifespan of a product, but there are many
other factors that influence whether regression testing needs to be done.
An example would be a product that is at certain stage in it's life cycle, and there is a
requirement for a new version to replace the old version.
In theory the ideal scenario would be that the new version of the software fully
supports the legacy functions of the previous version and is able to add new
functionality to the product without compromising the functional integrity of the
overall product.
With that in mind, this is where regression testing would be done, as you would now
want to ascertain whether the new version of the product does not add new defects
into the system.

126. Describe your QA experience (emphasis on Telecom)


Only QA can Prevent the software from Defects and moniter whether the software
meet the requirement and by Testing only we can find defect in the software. so if u
have QA experience u can tell that.

127. What testing tools have you used? How long?


If u r using any tool u can tell that.. other wise tell no.. in manual testing we wont
use any tools. except test directors. u can tell about test director (or QC).

128. What is white box, black box?


White Box:- White box testing is based on knowledge of the internal logic of an
application's code. Tests are based on coverage of code statements, branches, paths
and conditions.
Black Box:- Black box testing is functional testing, not based on any knowledge of
internal software design or code. Black box testing are based on requirements and
functionality.

128. What testing phases have you participated in?


Functional Testing, Regression Testing. or u can say System Testing. System
Integration Testing.

129. What’s the difference between functional testing, system test, and
UAT?
Functional Testing:- testing that ignores the internal mechanism of a system or
component and focuses solely on the outputs generated in response to selected
inputs and execution conditions. this is a black box testing.
System Testing:- System testing is black box testing, performed by the Test Team,
and at the start of the system testing the complete system is configured in a
controlled environment. The purpose of system testing is to validate an application's
accuracy and completeness in performing the functions as designed. System testing
simulates real life scenarios that occur in a "simulated real life" test environment and
test all functions of the system that are required in real life. System testing is
deemed complete when actual results and expected results are either in line or
differences are explainable or acceptable, based on client input.
UAT:- Acceptance testing is black box testing that gives the client/ customer/ project
manager the opportunity to verify the system functionality and usability prior to the
system being released to production. The acceptance test is the responsibility of the
client/customer or project manager, however, it is conducted with the full support of
the project team. The test team also works with the client/customer/project manager
to develop the acceptance criteria.

130. When would you perform regression testing?


Regression testing is verifing that previously passed tests are still OK after any
change to the software or the environment, usually to verify that a change in one
area doesn't affect other or unrelated areas.
131. What would you base your test cases on?
A test case is a document that describes an input, action, or event and its expected
result, in order to determine if a feature of an application is working correctly. A test
case should contain particulars such as a...
· Test case identifier;
· Test case name;
· Objective;
· Test conditions/setup;
· Input data requirements/steps, and

· Expected results.
Test cases will be prepared by the tester based on BRD & FS.

132. How do you make sure the results are as expected?


In Functional or System testing we will test with real time data. and realtime
scenarious with client approved test cases, so that we will know what is correct
result.

133. What’s more important: Positive or Negative testing?


Both are important, but most of the test cases will be returned for Positive, for some
applications Negetive cases also important.

134. Have you used SQL? For what purposes?


the answer is up to u.

134. What tools did you use to log defects?


U can say Test Director or Quality Center or excel sheet.

135. What other groups did you interact with (developers, users, analysts)
Who would you rather work with?
Analysts

Manual testing interview question and answer, PART 10


136. When you realize the load you have cannot be done in the time given,
how would you handle?
Use risk analysis to determine where testing should be focused.based on some
consideration we can come up with task of completing complete testing.some are
Which functionality is most important to the project's intended purpose?
Which functionality is most visible to the user?
Which functionality has the largest safety impact?
Which functionality has the largest financial impact on users?
Which aspects of the application are most important to the customer?
Which aspects of the application can be tested early in the development cycle?
Which parts of the code are most complex, and thus most subject to errors?
Which parts of the application were developed in rush or panic mode?
Which aspects of similar/related previous projects caused problems?
Which aspects of similar/related previous projects had large maintenance expenses?
Which parts of the requirements and design are unclear or poorly thought out?
What do the developers think are the highest-risk aspects of the application?
What kinds of problems would cause the worst publicity?
What kinds of problems would cause the most customer service complaints?
What kinds of tests could easily cover multiple functionalities?
Which tests will have the best high-risk-coverage to time-required ratio?

137. How do u give the severity and priority of a bug?


ANS: based on test plan and bug. Severity is based on functionality and priority is
based on test proceedings or business req.

138. One example for limitation bug?


ANS: When you open a webpage in 1024X768 resolutions which was designed in
800X600, you may see white border on both sides of a webpage which can be
considered as a bug. but because of design, it will be a limitation.

139. How do u test the usability of an installer?


Ans: Short cuts, Default Folder Locations, Restart of system etc.

140. What is the difference b/w unique key and primary key?
ANS: Unique allows single Null, Primary Key doesn't allow Null. Primary key only
allows Foreign Key mapping.

141. What r the five main elements of a bug?


ANS: STEPS< EXP RE< ACT RES< STATUS< SEVEITY

142. What is the process for implementing change requests?


ANS: CR docs-> Impact Analysis->Design and develop-> Test->Release.

143. When do u go for automation?


ANS: Whenever more retesting is required or precise test results are required. Re
testing is seen for SANITY CHECKS, Critical Functionality Checks, Workflow related
req, data driven requirements etc..

144. What type of testing u perform first while doing BLACK BOX testing ?
ANS: It depends on the project and time availability. If it is a normal project with
comfortable time lines, we start the testing with UI and validations. These are also
called as Unit Level checks.

145. What is soap,AIS,CAT testing ?


ANS: SOAP is Simple Object Access Protocol . It is a technique which we generally
observe while working with Webservices. Its a lightweight messaging protocol with
Envolop, Encoding Rules and Conversion etc.
AIS. There are some software with this name, but I am not sure what do you mean.
CAT. Computer Aided Test. It is generally the automation.

146. what is a incident logging system ?


ANS: It will be a tool like testDirector where observations can be logged. This can be
used by developers or testers or end users depending upon the application.

147 – Different b\w UAT&CAT?


ANS: UAT. User Acceptance Testing for high priority business req and customer
acceptance testing.
148. What is the need of integration testing?
ANS: To test the interfaces or dependencies betweens different modules/
components of teh system. if they are not tested at individual components, they can
trouble many functionalities after system integration or system testing.

149. What are the diff. types of joins in DB?


ANS: There are many classifications for this. But one common one is
A. SelfJoin
B.Inner Join
C. Outer Join

150. What types of testcases u will automate?


ANS: Sanity Checks, critical Functionality checks, data driven tests.

Manual testing interview question and answer, PART 11


151. How do you write the TCs and what are the i/p for writing TCs?
ANS: inputs are Req docs(SRS/Usecases) and Design docs (UI Design, DB Design
etc)

152. How can u identify by seeing the web page that it is a security?
ANS: when we open the any security site , it automatically use the HTTPS protocol
(HYPER TEXT TRANSFER PROTOCAL secure) HTTPS is an encrypted form of HTTP
used for sending sensitive data like credit card numbers between the browser and
the web server. This is also sometimes called Secure HTTP or SSL (which stands for
Secure Sockets Layer).

153. What is database integration?


ANS: having connection between Db and application of other DB. This need to be
tested as part of DB integration. In general we see DB connection with Application
Servers. But few applications will have multiple databases involved. Then integration
is required b/w databases.

154 – Test process of your company?


ANS: Start from Req Analysis using Usecases/SRS- >Testcases prep- >review-> test
bed Setup including data->Diff testing based on project->acceptance and Rel &
maintenance.
This is a very imp question and just answer is not sufficient. You need to maintain
the flow and able to discuss one of your project as example.

155 – What is the Architecture for your project?


ANS: Architecture means how we are going to maintain/distribute the application
components. It can be 1-Tier/ 2-Tier/ 3 tier.
A. Generally client server is seen as 2 tier like VB&oracle appl. It is alos possible to
have 3-tier in client server. Eg. SAP
B. Generalli Webbased are seen as 3 tier like ICICIBANK.com. But we can also see
them like 2 tier like news papers/ portals.

156. What do you mean by process engineering related to QA?


ANS: Analyzing the different activities involved, identify the existing process, identify
the gaps in the process, and define a new process which would be smooth and
complete.

157. Who can be called as a good tester?


ANS: A tester who tests all the clients’ requirements when time is permitting or a
tester who tests the business critical requirements
When time constraints are there.
A tester who has good enthu,
Who is diplomatic,
A team player.
A tester who has OUT OF BOX thinking.
A tester who has good analytical skills.

158. What is the best test case that you have written in your project till
now?
ANS: Pls pick a testcases which has data dependency b/w two different projects.

159. Do you use any tool for writing test cases?


ANS: MS-Excel or Test Director or any internal tool.

160. Who raises the CR's?


ANS: Client/endures raises the CRs. But they will be passed by Business/leads and a
decision will be made on whether to accept it or not. If accepting, the schedules etc
will also be decided. This tasks are carried using IMPACT ANALYSIS approach.

161. What are the concepts a test engineer should have knowledge of?
ANS: Windows/Database/ Web/ManualTesting (TestPlan,TestCases, diff phases of
testing, Bug)/One automation tool.

162 – What is use case?


ANS: A use case is a set of scenarios that describing an interaction between a user
and a system. A use case diagram displays the relationship among actors and use
cases. The two main components of a use case diagram are use cases and actors. It
is nothing but pictorial representation.

163. What is Functional requirement?


ANS: It is a written document represents the functionality of the application.

164. Why do we go for system testing if we are through with integration


testing?
ANS: In integration testing is used when we combine the Low level component to
High level Units but after combined the hole system , we use system testing to test
the hole system.(Application ).

165. What are the different testing’s we perform in system testing?


GUI Testing
Validation
Usability.
Performance
Regression testing
Retesting
compatibility( for web applications) . etc.

Manual Testing Interview Questions and Answers.


Q - What are test case formats widely use in web based testing?
A - Web based applications deal with live web portals. Hence the test cases can be broadly
classified as - front end , back end, security testing cases, navigation based, field validations,
database related cases. The test cases are written based on the functional specifications and
wire-frames.

Q - How to prepare test case and test description for job application?
A - Actually the question seems to be vague,... see naukri is one of biggest job site globally and it
has is own complex functionality normally a Test case is derived from a SRS (or) FRS basically
and test description is always derived from a Test case. Test description is nothing but the steps
which has to be followed for the TC what u wrote. And the TC is nothing which compares the
expectation and the actual(outcome)result.

Q - What is the difference between Functional and Technical bugs? Give an example for
each.?
Functional Bugs : Bugs found when Testing the Functionality of the AUT.
Technical bugs: Related to Communication which AUT makes.Like H/W,DB ! where these could
not be connected properly.

Q - Give proper Seq. to following testing Types Regression, Retesting, Funtional, Sanity
and Performance Testing.?
A - The proper sequence in which these types of testing are performed is - Sanity, Functional,
Regression, Retesting, Performance.

Q - How u test MS- Vista without any requirement Doc.?


Know what change is being made from the older verison of Windows to the newer version with
the help of User Release notes thats released with Windows Vista. Based on that, formulate the
test cases and execute the same.

Q - What is verification? validation?

Verification typically involves reviews and meetings to evaluate documents, plans, code,
requirements, and specifications. This can be done with checklists, issues lists, walkthroughs,
and inspection meetings. Validation typically involves actual testing and takes place after
verifications are completed. The term 'IV & V' refers to Independent Verification and Validation.

Q - How can new Software QA processes be introduced in an existing organization?

A lot depends on the size of the organization and the risks involved. For large organizations with
high-risk (in terms of lives or property) projects, serious management buy-in is required and a
formalized QA process is necessary.

Where the risk is lower, management and organizational buy-in and QA implementation may be a
slower, step-at-a-time process. QA processes should be balanced with productivity so as to keep
bureaucracy from getting out of hand.

For small groups or projects, a more ad-hoc process may be appropriate, depending on the type
of customers and projects. A lot will depend on team leads or managers, feedback to developers,
and ensuring adequate communications among customers, managers, developers, and testers.

The most value for effort will often be in (a) requirements management processes, with a goal of
clear, complete, testable requirement specifications embodied in requirements or design
documentation, or in 'agile'-type environments extensive continuous coordination with end-users,
(b) design inspections and code inspections, and (c) post-mortems/retrospectives.

Q - Why is it often hard for management to get serious about quality assurance?

Solving problems is a high-visibility process; preventing problems is low-visibility. This is


illustrated by an old parable: In ancient China there was a family of healers, one of whom was
known throughout the land and employed as a physician to a great lord.

Q - What's an 'inspection'?

An inspection is more formalized than a 'walkthrough', typically with 3-8 people including a
moderator, reader, and a recorder to take notes.

The subject of the inspection is typically a document such as a requirements spec or a test plan,
and the purpose is to find problems and see what's missing, not to fix anything. Attendees should
prepare for this type of meeting by reading thru the document; most problems will be found during
this preparation. The result of the inspection meeting should be a written report.

Q - What is a 'walkthrough'?
A 'walkthrough' is an informal meeting for evaluation or informational purposes. Little or no
preparation is usually required.

Q - What makes a good test engineer?


A good test engineer has a 'test to break' attitude, an ability to take the point of view of the
customer, a strong desire for quality, and an attention to detail. Tact and diplomacy are useful in
maintaining a cooperative relationship with developers, and an ability to communicate with both
technical (developers) and non-technical (customers, management) people is useful. Previous
software development experience can be helpful as it provides a deeper understanding of the
software development process, gives the tester an appreciation for the developers' point of view,
and reduce the learning curve in automated test tool programming. Judgment skills are needed to
assess high-risk areas of an application on which to focus testing efforts when time is limited.

Q - What makes a good Software QA engineer?


The same qualities a good tester has are useful for a QA engineer. Additionally, they must be
able to understand the entire software development process and how it can fit into the business
approach and goals of the organization. Communication skills and the ability to understand
various sides of issues are important. In organizations in the early stages of implementing QA
processes, patience and diplomacy are especially needed. An ability to find problems as well as
to see 'what's missing' is important for inspections and reviews.
Q - What is agile testing?
Agile testing is used whenever customer requirements are changing dynamically
If we have no SRS, BRS but we have test cases does you execute the test cases blindly or do
you follow any other process.
Test case would have detail steps of what the application is supposed to do.
1) Functionality of application.
2) In addition you can refer to Backend, is mean look into the Database. To gain more knowledge
of the application.