Common Interview question for manual testing

 Common Interview question for manual testing 

1. Differentiate between QA and QC?

QA: It is process oriented

        it involve in entire process of software development.

        Prevention oriented.

QC:

       It is product oriented.

       work to examine the quality of product.

       Detection oriented.

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?

               Test case is set of input values, execution preconditions, expected results and execution post conditions, developed for a particular objective or test conditions, such as to exercise a particular program path or to verify compliance with a specific requirement.

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 strategy ,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,schedule,environmental requirements, risks & contingencies, change management 

procedures, plan approvals,etc all these things help a test manager understand 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 requirement 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 test engineers/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 regression testing?

Functional testing is a testing process where we test the functionality/behavior of each functional component of the 

application...minimize button,transfer button,links etc.i.e we check what is each component doing in that application... 

regression testing is the testing the behavior of the application of the unchanged areas when there is a change in the build .i.e we check 

whether the changed requirement has altered the behavior of the unchanged areas. the impacted area may be the whole of the 

application or 

some part of the application...

9.do u know about integration testing,how do u integrate difference 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 balance it shows the 100$as the available balance. But in database it shows the 120$. main thing is "integration 

done by the developers and integration testing done by the testers"

10.do u know abt configuration management tool,what is the purpose of maintaining all the documents in configuration 

management 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 x).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.

11.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/Retrieval

3. Database Connectivity (across multiple platforms)

4. Database Indexing

5. Data Integrity

6. Data Security

12.suppose if you press a link in yahoo shopping 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 cursor is turning into hand icon or not?

2)i will check the link is highlighting when i place the cursor 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 exist(to check user friendliness 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 opening or not?

8)all other sub links are opening or not?

13.what are the contents of FRS?

F → Function Behaviors

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 Behavior Specification - Document. Or EFS External 

Function Specification.

14.what is meant by Priority and severity?

Priority means "Importance of the defect w.r.t customer requirement"

Severity means "Seriousness of the defect w.r.t functionality"

15.what is meant by Priority and severity?

Severity:

1. This is assigned by the Test Engineer

2. This is to say how badly the deviation that is occurring 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 valid 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.

16.give me some example for high severity and low priority defect?

if suppose the title of the particular concern is not spelled correctly,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.

17.what is basis for test case review?

the main basis for the test case review is

1.testing techniques oriented review

2.requirements oriented review

3.defects oriented review.

18.what are the contents of SRS documents?

Software requirements specifications and Functional requirements specifications.

19.What is difference between the Web application testing and Client Server testing?

Testing the application in intranet(without browser) 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 web testing. The application which is accessible 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 e- commerce testing application we go for Usability etc.. testings.

20.Explain your web application architecture?

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

21.suppose the product/application 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 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 priority or not. if its priority then we ask him to wait.

Here we found defects/bugs in the last minute of the delivery or release 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 analyses 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 remedy 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 .

22.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 depositing/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 happening 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..

23.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 sign off

8)->if problem in built reopen the issue send to step3

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

To report the defect using excel sheet

Mention : The Feature 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

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

While reporting this bug into bug tracking tool you will generate the test case I mean put the steps to reproduce the bug.

26.what is the differ between 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 reflected on other layers also whereas client based separate changes need be installed on client machine also.

27.what is test plan? and can you tell the test plan 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.

28.How many test cases 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

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

What is the impotent of FRS?

The Business Analyst will prepare 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. Prototype of the of the application

4. Business rules and Error States

5. Data Flow diagrams

6. Use cases contains Actor and Actions and System Responses

30.How you can decide the number of test cases are enough for testing the given module?

The developed test cases are covered all the functionality of the application we can say test cases are enough. If u know the functionality covered or not u can use RTM.

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

Retesting: it is manual process in which application will be tested with entire new set of data.

Data Driven Testing (DDT)-It is a Automated testing process in which 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 inputs manually from front end and it is very tedious and boring procedure.

32.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 their integrity after bug fixation.

33.how do u test web application?

Web application testing

web application should have the following features like

1.Attractive User Interface(logos,fonts,alignment)

2.High Usability options

3.Security features(if it has login feature)

4.Database(back end).

5.Performance(appearing speed of the application on client system)

6.Able to work on different Bowers(Browser compatibility) ,O.S compatibility(technical 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(different versions and different browser)

7.Broken link and Navigation Testing

8.Database(back end)Testing(data integrity)

9.Portability testing(Multi Os Support)....etc

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

Regression testing will be conducted after any bug fixed or any functionality changed. During defect fixing procedure some part of coding may be changed or functionality may be manipulated. In this case the old test

cases 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 test cases will be added to existing test cases or some test cases may be deleted.

35.what r the client side scripting languages and server side scripting languages

client side scripting languages are

JavaScript,Vb Script,PHP...etc

Server side Scripting languages are Perl,JSP,ASP,PHP..etc

Client side scripting languages are useful to validate the inputs or user actions from user side 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 client side scripting is good because it won't send the unwanted input's to server for validation. from front end it self it validated the user inputs and restricts the user activities and guides him

36.if a very low defect (user interface )is detected by u and the developer not compromising 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 defect 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 developer system configuration and also 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 side then report the defect by following the above method.

37.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?

One thing 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 client need speedy service,we(our company) should not get any blame from customer side.

38.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.

39.How many Test-Cases can be written for the calculator having 0-9 buttons, Add,Equal buttons. The test cases should be

focused only on add-functionality but mot GUI. What are those test-cases?

Test-Cases for the calculator

so here we have 12 buttons total ie 0,1,2,3,4,5,6,7,8,9,ADD,Equal -12 buttons

here u can press at least 4 buttons at a time minimum for example 0+1= for zero u should press 'zero' labeled button for plus u should

press '+' labeled button for one u should press 'one' labeled button for equal to u should press 'equal to' labeled button 0+1=here + and =

positions will not vary so first number position can be varied from 0 to 9 i.e from permutation and combinations u can fill that space in

10 ways in the same way second 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 that is '0')then another test case for

'9+9='(expected values you know that is '18')only two test cases are enough to test the calculator functionality.