Manual Testing Interview Questions

7/17/2019 Manual Testing Interview Questions

http://slidepdf.com/reader/full/manual-testing-interview-questions-568c9f963c99a 1/74

Manual Testing Interview Questions

1.differentiate between QA and QC? QA:It is process oriented

it envolve in entire process of software developement. 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 itfrom working correctly or produces an incorrect result.

3.what is a test case? Testcase is set of input values, execution preconditions,expected results and executionpostconditions, 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 likeintroduction,objectives,test stratergy,scope,test items,program modules userprocedures,features to be tested features not to tested approach,pass or fail criteria,testingprocess,test deliverables,testing,tasks,responsibilities,resources,schedu le,environmental requirements,risks & contingencies,change management procedures,planapprovals,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 theapplication 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 insideinterfacing 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 smoketest.smoke test is the first test which is done by the testing team.this is according to the testingteam.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 prioritygiven 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.Projectmanagers 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 functionalcomponent of the application...i.e.minimize button,transfer button,links etc.i.e we check what is eachcomponent doing in that application... regression testing is the testing the behaviour of the application of the unchanged areas when there isa change in the build.i.e we chk whether the changed requirement has altered the behaviour of theunchanged areas.the impacted area may be the whole of the application orsome 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.forexample, when you are testing a bank application ,in account balence it shows the100$as the available balence.but in database it shows the 120$. main thing is "integration done bythe 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 forex).Then you send it for Peer Review .They will provide some comments and that document will besaved in VSS again.Similary the document undergoes changes and all the changes history will bemaintained 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 butthey won't be complete. In general we look at 1. Data Correctness (Defaults)2. Data Storage/Retreival3. Database Connectivity (across multiple platforms) 4. Database Indexing5. Data Integrity 6. Data Security

13.suppose if you press a link in yahooshopping site in leads to some other companywebsite?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 thelink 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 BehavioursR → 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"

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 orrelease. 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 basicrequirement.

Eg., The code is to generate some values with some vaild input conditions. The priority will beassigned so based on the following conditions: a> It is not accepting any valueb> 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 displayedcorrectly but after saving changes it gave some address value from thestack 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.egICICC is spelled as a tittle for the project of the concern ICICI.then it is a high severity,low prioritydefect.

18.what is basis for testcase review? the main basis for the test case review is1.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 companyfirewalls for the server are not open to outside world. Outside people cannot access theapplication.)So there will be limited number of people using that application.

Testing an application in internet(using browser) is called webtesting. The application which isaccessable 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 bedone 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 compatibility2. 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 oryour team member caught a high severity defect at 3PM.(Remember defect is highseverity)But the the client is cannot wait for long time.You should deliver the product at5.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 ispreyority 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 tofind workarounds for the defect and mention these issues in the release notes as known issues orknown limitations or known bugs. Here the workaround means remeady process to be followed toovercome the defect effect. 3.Normally this known issues or known limitations(defects) will be fixed in next version or next releaseof 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 everwe are dipositing/withdrawing money it is not showing any conformation message but actually at theback end it is happening properly with out any mistake means only missingof message . in this case as it is happenig properly so there is nothing wrong with the application butas end user is not getting any conformation message so he/she will beconfuse 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 developer4)->if accepted moves to step5 else sends the bug to tester gain

5)fixed by developer -> 6)regression testing-> 7)no problem inbuilt and signoff8)->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 sheetMention : The Feture that been effected. mention : Test Case ID (Which fail you can even mention any other which aredependency on this bug) Mention : Actual Behavior Mention : Expected Behavior as mentioned in Test Case or EFS or EBS or SRSdocument 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 thesetestcase you found some defect for which testcase is not prepared,thwn how you can reportthe bug? While reporting this bug into bugtracking tool you will generate the testcase imean put the steps toreproduce 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 webapplication are 3 trier & client based are 2 trier.In web based changes are made at one place & it isrefelected on other layers also whereas client based separate changes need be installed on clientmachine 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 resourcesin 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 dayNormal 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

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 areenough.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 multipletest data.DDT is very easy procedure than retesting because the tester should sit and need to givedifferent new inputsmanually from front end and it is very tedious and boringprodedure.

33.what is regression testing? After the Bug fixed ,testing the application whether the fixed bug is affecting remaining functionality ofthe application or not.Majorly in regression testing Bug fixed module and it'sconnected modules are checked for thier integrity after bug fixation.

34.how do u test web application?

Web applicatio testingweb 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 bemanipulated.In this case the old testcases will be updated or completely re writtenaccording to new features of the application where bug fixed area.Here possible areas are old testcases 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 clientside. 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 webor client server application cleint side scripting is good because it won't send the unwanted input's to server for validation.fromfrontend 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 notcompramising 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 report3.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 asdevelopper 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 whatthe client asked for what will u do? Onething here is very important.Nobody will ask test engineer to change software that isnot your duty,even if it is related to testing and anybody is not there try to listen care fully if you arenot 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,Equaltobuttons.The testcases should be focussed only on add-functionality but mot GUI.What arethose 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 buttonforequalto u should press 'equalto' labled button 0+1=here + and = positions will not varyso firstnumber position can be varied from 0 to 9 i.e from permutation and combinations u can fill that spacein 10 waysin the same waysecond number position can be varied from 0 to 9 i.e from permutationand 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 arange 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 areenough 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 acceptonly Strings.By providing only String as input data to the textbox & to check whether its workingproperly or not means it is Positive Testing.If giving the input other than String means it is negativeTesting..

42.How will you prepare Test plan. What are the techniques involved in preparing the Testplan. 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 areresolved. 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 application6.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 theprocess 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 errosinterms of functionality and the common functionality should be stablein the latest and the previous versions

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 Documentthere will be URL path of the website link from from that we will receivethe build In case of web server projects, you will be provided with an URL or a 92.168.***.*** (Webaddress) 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, analysethe results report the bugs. invovled in regression testing, performance of systemtesting 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 TESTPASS,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 TestResults doc ,TL will come to know the coverage part of the testcase.Here Iam 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 ourclient.This document will be prepared by TL and delivered to the client.Mainly,this document describesthe what we have done in the project,chievements we have reached,ourlearnings in throughout the project etc...The other name for Test report is Project Closure Report andwe will summerize the all the activities,which have taken place in through out the project.Here I amgiving your the contents covered in the Test Report. 1.Test Environment(Should be covered the OS,Application or webservers,Mahchinenames,Database,etc...)



2.Test Methods(Types of Tests,we have done in the project like Functional Testing,PlatformTesting,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 likecreation,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 aredisplayed as per the requirements,buttons are enabled or disabled,and testcase for low priorityfunctionalities. 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 TCand 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 willframe set of testcases,in other terms,we can say all the conditions,which can be determined thetesting 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 andpassword.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 extrafeatures are added

53.wat is test deliverables Test deliverables are nothing but documents preparing after testing like test plan document testcasetemplate bugreport templateTest deliverables will be delivered to the client not only for the completedactivities ,but also for the activites,which we are implementing for the better productivity.(As per thecompany'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 planrole TE is testcase design ,and execution and bugtraking and reporting them Genarally TL is involed inpreparation of the TestPlan.But it is not mandatory only TL will take main part in the preparaion of theTP.Test engineer can suggest to TL,if he(or) she has good understanding on project and resources,ifhe or she has more exp with the project,if TL is wrongly given deadlines.If your suggestions arevalid,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 arealways 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?whyYes..definitely. If requirement changes, the design documents, specifications (for that particualrmodule which implements the requiremnts) will also change. Hence the test plan would also need tobe updated. This is because "REsource Allocation" is one section in the testplan. We would need to write new test cases,review, and execute it. Hence resource allocation wouldhave 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 folderof 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 Bydevoloper 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 thefunctionality. 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 rused.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 isdeveloped.

60.What is a "Good Tester"? Is one who tries to break the developers software and in a position to venture the bugs. so thatatleast 80% bugs free software can deliver.

What is Database testing? Data bas testing basically include the following. 1)Data validity testing. 2)Data Integrity testing 3)Performance related to data base. 4)Testing of Procedure, triggers and functions. for doing data validity testing you should be good in SQL queries For data integrity testing you should know about referential integrity and different constraint. For performance related things you should have idea about the table structure and design. for testing Procedure triggers and functions you should be able to understand the same.

What we normally check for in the Database Testing? In DB testing we need to check for, 1. The field size validation 2. Check constraints. 3. Indexes are done or not (for performance related issues) 4. Stored procedures 5. The field size defined in the application is matching with that in the db.

How to Test database in manually? Explain with an example Observing that operations, which are operated on front-end is effected on back-end or not. The approach is as follows: While adding a record thru' front-end check back-end that addition of record is effected or not. So same fordelete, update,...... Ex:Enter employee record in database thru' front-end and check if the record is added or notto the back-end(manually).

Part – 2

1. What is the difference between Functional Requirement and Non-Functional

Requirement?

The Functional Requirement specifies how the system or application SHOULD DO where inNon Functional Requirement it specifies how the system or application SHOULD BE.

Some functional Requirements are

Authentication

Business rules



Historical Data

Legal and Regulatory Requirements

External Interfaces

Some Non-Functional Requirements are

Performance Reliability

Security Recovery

Data Integrity

Usability

2. How Severity and Priority are related to each other?

Severity- tells the seriousness/depth of the bug where as Priority- tells which bug should rectify first.

Severity- Application point of view

Priority- User point of view

3. Explain the different types of Severity?

1. User Interface Defect-Low

2. Boundary Related Defects-Medium

3. Error Handling Defects-Medium

4. Calculation Defects-High

5. Interpreting Data Defects-High

6. Hardware Failures& Problems-High

7. Compatibility and Intersystem defects-High

8. Control Flow defects-High

9.

Load conditions (Memory leakages under load testing)-High

4. What is the difference between Priority and Severity?

The terms Priority and Severity are used in Bug Tracking to share the importance of a bugamong the team and to fix it.Severity: Is found in the Application point of view

Priority- Is found in the User point of viewSeverity- (tells the seriousness/depth of the bug)

1. The Severity status is used to explain how badly the deviation is affecting the build.

2. The severity type is defined by the tester based on the written test cases and

functionality.

Example

If an application or a web page crashes when a remote link is clicked, in this case clickingthe remote link by an user is rare but the impact of application crashing is severe, so theseverity is high and priority is low.



PRIORITY- (tells which bug should rectify first)

1. The Priority status is set by the tester to the developer mentioning the time frame tofix a defect. If High priority is mentioned then the developer has to fix it at theearliest.

2. The priority status is set based on the customer requirements.

Example

If the company name is misspelled in the home page of a website, then the priority is highand the severity is low to fix it.

Severity: Describes the bug in terms of functionality.Priority: Describes the bug in terms of customer.

Few examples:

High Severity and Low Priority -> Application doesn't allow customer expected

configuration.High Severity and High Priority -> Application doesn't allow multiple user's.Low Severity and High Priority -> No error message to prevent wrong operation.Low Severity and low Priority -> Error message is having complex meaning.

Or

Few examples:

High Severity -Low priority

Supposing, you try the wildest or the weirdest of operations in a software (say, to be

released the next day) which a normal user would not do and supposing this renders a run -time error in the application,the severity would be high. The priority would be low as theoperations or the steps which rendered this error by most chances will not be done by auser.

Low Severity -High priority

An example would be- you find a spelling mistake in the name of the website which you aretesting.Say, the name is supposed to be Google and its spelled there as 'Gaogle'. Though, itdoesn't affect the basic functionality of the software, it needs to be corrected before therelease. Hence, the priority is high.

High severity- High Priority

A bug which is a show stopper. i.e., a bug due to which we are unable to proceed ourtesting.An example would be a run time error during the normal operation of thesoftware,which would cause the application to quit abruptly.

Low severity - low priority



Cosmetic bugs

What is Defect Severity?

A defect is a product anomaly or flaw, which is variance from desired product specification.The classification of defect based on its impact on operation of product is called Defect

Severity.

5. What is Bucket Testing?

Bucket testing (also known as A/B Testing) is mostly used to study the impact of variousproduct designs in website metrics, two simultaneous versions were run in a single or set ofweb pages to measure the difference in click rates, interface and traffic.

6. What is Entry and Exit Criteria in Software Testing?

Entry Criteria is the process that must be present when a system begins, like,

SRS (Software Requirement Specification) FRS (Functional Requirement Specification)

Usecase

Test Case

Test plan

Exit Criteria ensures whether testing is completed and the application is ready for release,like,

Test Summary Report Metrics

Defect Analysis report

7. What is Concurrency Testing?

Concurrency Testing (also commonly known as Multi User Testing) is used to know theeffects of accessing the Application, Code Module or Database by different users at thesame time.It helps in identifying and measuring the problems in Response time, levels oflocking and deadlocking in the application.

Example

Load runner is widely used for this type of testing, Vugen (Virtual User Generator) is used toadd the number of concurrent users and how the users need to be added like Gradual Rampup or Spike Stepped.

8. Explain Statement coverage/Code coverage/Line Coverage?

Statement Coverage or Code Coverage or Line Coverage is a metric used in White BoxTesting where we can identify the statements executed and where the code is not executedcause of blockage. In this process each and every line of the code needs to be checked andexecuted.

Some advantages of Statement Coverage / Code Coverage / Line Coverage are



It verifies what the written code is expected to do and not to do. It measures the quality of code written. It checks the flow of different paths in the program also ensure whether those paths

are tested or not.

To Calculate Statement Coverage,

Statement Coverage = Statements Tested / Total No. of Statements.

9. Explain Branch Coverage/Decision Coverage?

Branch Coverage or Decision Coverage metric is used to check the volume of testing done inall components. This process is used to ensure whether all the code is executed by verifyingevery branch or decision outcome (if and while statements) by executing atleast one time,so that no branches lead to the failure of the application.

To Calculate Branch Coverage,

Branch Coverage = Tested Decision Outcomes / Total Decision Outcomes.

10. What is the difference between High level and Low Level test case?

High level Test cases are those which cover major functionality in the application (i.e.retrieve, update display, cancel (functionality related test cases), database test cases).Low level test cases are those related to User Interface (UI) in the application.

11. Explain Localization testing with example?

Localization is the process of changing or modifying an application to a particular cultureor locale. This includes change in user interface, graphical designs or even the initialsettings according to their culture and requirements.

In terms of Localization Testing it verifies how correctly the application is changed ormodified into that target culture and language.

In case of translation required of the application on that local language, testing should bedone on each field to check the correct translation. Other formats like date conversion,hardware and software usage like operating system should also be considered in localizationtesting.

Examples for Localization Testing are

In Islamic Banking all the transactions and product features are based on Shariah Law,

some important points to be noted in Islamic Banking are

1. In Islamic Banking, the bank shares the profit and loss with the customer. 2. In Islamic Banking, the bank cannot charge interest on the customer; instead they

charge a nominal fee which is termed as "Profit 3. In Islamic Banking, the bank will not deal or invest in business like Gambling,

Alcohol, Pork, etc.



In this case, we need to test whether these Islamic banking conditions were modified andapplied in the application or product.

In Islamic Lending, they follow both the Gregorian calendar and Hijiri Calendar forcalculating the loan repayment schedule. The Hijiri Calendar is commonly called as Islamic

Calendar followed in all the Muslim countries according to the lunar cycle. The HijiriCalendar has 12 months and 354 days which is 11 days shorter than Gregorian calendar. Inthis case, we need to test the repayment schedule by comparing both the Gregoriancalendar and Hijiri Calendar.

12. Explain Risk Analysis in Software Testing?

In Software Testing, Risk Analysis is the process of identifying risks in applications andprioritizing them to test.

In Software testing some unavoidable risk might takes place like

Change in requirements or Incomplete requirements

Time allocation for testing. Developers delaying to deliver the build for testing. Urgency from client for delivery. Defect Leakage due to application size or complexity.

To overcome these risks, the following activities can be done

Conducting Risk Assessment review meeting with the development team. Profile for Risk coverage is created by mentioning the importance of each area. Using maximum resources to work on High Risk areas like allocating more testers for

High risk areas and minimum resources for Medium and Low risk areas. Creation of

Risk assessment database for future maintenance and management review.

13. What is the difference between Two Tier Architecture and Three TierArchitecture?

In Two Tier Architecture or Client/Server Architecture two layers like Client andServer is involved. The Client sends request to Server and the Server responds to therequest by fetching the data from it. The problem with the Two Tier Architecture is theserver cannot respond to multiple requests at the same time which causes data integrityissues.The Client/Server Testing involves testing the Two Tier Architecture of user interface in thefront end and database as backend with dependencies on Client, Hardware and Servers.

In Three Tier Architecture or Multi Tier Architecture three layers like Client, Serverand Database are involved. In this the Client sends a request to Server, where the Serversends the request to Database for data, based on that request the Database sends back thedata to Server and from Server the data is forwarded to Client.

The Web Application Testing involves testing the Three Tier Architecture including the Userinterface, Functionality, Performance, Compatibility, Security and Database testing.



14. What is the difference between Static testing and dynamic testing?

Static Testing (done in Verification stage)

Static Testing is a White Box testing technique where the developers verify or test theircode with the help of checklist to find errors in it, this type of testing is done without

running the actually developed application or program. Code Reviews, Inspections,Walkthroughs are mostly done in this stage of testing.

Dynamic Testing (done in Validation stage)

Dynamic Testing is done by executing the actual application with valid inputs to check theexpected output. Examples of Dynamic Testing methodologies are Unit Testing, IntegrationTesting, System Testing and Acceptance Testing.

Some differences between Static Testing and Dynamic Testing are,

Static Testing is more cost effective than Dynamic Testing because Static Testing is

done in the initial stage. In terms of Statement Coverage, the Static Testing covers more areas than Dynamic

Testing in shorter time. Static Testing is done before the code deployment where the Dynamic Testing is

done after the code deployment.

Static Testing is done in the Verification stage where the Dynamic Testing is done inthe Validation stage.

15. Explain Use case diagram. What are the attributes of use cases?

Use Case Diagrams is an overview graphical representation of the functionality in a system.It is used in the analysis phase of a project to specify the system to be developed.In Use Case Diagrams the whole system is defined as ACTORS, USE CASES andASSOCIATIONS, the ACTORS are the external part of the system like users, computersoftware & hardware, USECASES is the behavior or functionality of the system when theseACTORS perform an action, the ASSOCIATIONS are the line drawn to show the connectionbetween ACTORS and USECASES. One ACTOR can link too many USECASES and oneUSECASE can link too many ACTORS.

16. What is Web Application testing? Explain the different phases in WebApplication testing?

Web Application testing is done on a website to check its load, performance, Security,Functionality, Interface, compatibility and other usability related issues. In Web applicationtesting, three phases of testing is done, they are,

Web Tier Testing

In Web tier testing, the browser compatibility of the application will be tested for IE, FireFox and other web browsers.

Middle Tier Testing



In Middle tier testing, the functionality and security issues were tested.

Database Tier Testing

In Database tier testing, the database integrity and the contents of the database weretested and verified.

17. Explain Unit testing, Interface Testing and Integration testing. Also explain thetypes of integration testing in brief?

Unit testing

Unit Testing is done to check whether the individual modules of the source code are workingproperly. i.e. testing each and every unit of the application separately by the developer indeveloper's environment.

Interface Testing

Interface Testing is done to check whether the individual modules are communicatingproperly one among other as per the specifications.Interface testing is mostly used in testing the user interface of GUI application.

Integration testing

Integration Testing is done to check the connectivity by combining all the individual modulestogether and test the functionality.

The types of Integration Testing are

1. Big Bang Integration Testing

In Big Bang Integration Testing, the individual modules are not integrated until all themodules are ready. Then they will run to check whether it is performing well.

In this type of testing, some disadvantages might occur like,

Defects can be found at the later stage.It would be difficult to find out whether the defectarouse in Interface or in module.

2. Top Down Integration Testing

In Top Down Integration Testing, the high level modules are integrated and tested first. i.eTesting from main module to sub module. In this type of testing, Stubs are used astemporary module if a module is not ready for integration testing.

3. Bottom Up Integration Testing

In Bottom Up Integration Testing, the low level modules are integrated and tested first i.eTesting from sub module to main module. Same like Stubs, here drivers are used as atemporary module for integration testing.



18. Explain Alpha, Beta, Gamma Testing?

Alpha Testing:

Alpha Testing is mostly like performing usability testing which is done by the in-housedevelopers who developed the software or testers. Sometimes this Alpha Testing is done bythe client or an outsider with the presence of developer and tester. The version release afteralpha testing is called Alpha Release.

Beta Testing:

Beta Testing is done by limited number of end users before delivery, the change requestwould be fixed if the user gives feedback or reports defect. The version release after betatesting is called beta Release.

Gamma Testing:

Gamma Testing is done when the software is ready for release with specified requirements,this testing is done directly by skipping all the in-house testing activities.

19. Explain the methods and techniques used for Security Testing?

Security testing can be performed in many ways like,

1. Black Box Testing

2. White Box Testing

3. Database Testing

1. Black Box Testing

a. Session Hijacking

Session Hijacking commonly called as "IP Spoofing" where a user session will be attackedon a protected network.

b. Session Prediction

Session prediction is a method of obtaining data or a session ID of an authorized user andgets access to the application. In a web application the session ID can be retrieved fromcookies or URL.The session prediction happening can be predicted when a website is not respondingnormally or stops responding for an unknown reason.

c. Email Spoofing

Email Spoofing is duplicating the email header ("From" address) to look like originated fromactual source and if the email is replied it will land in the spammers inbox. By inserting



commands in the header the message information can be altered. It is possible to send aspoofed email with information you didn't write.

d. Content Spoofing

Content spoofing is a technique to develop a fake website and make the user believe that

the information and website is genuine. When the user enters his Credit Card Number,Password, SSN and other important details the hacker can get the data and use if for fraudpurposes.

e. Phishing

Phishing is similar to Email Spoofing where the hacker sends a genuine look like mailattempting to get the personal and financial information of the user. The emails will appearto have come from well known websites.

f. Password Cracking

Password Cracking is used to identify an unknown password or to identify a forgottenpassword

Password cracking can be done through two ways,

1. Brute Force â€“ The hacker tries with a combination of characters within a lengthand tries until it is getting accepted.

2. Password Dictionary â€“ The hacker uses the Password dictionary where it isavailable on various topics.

2. White Box level

a. Malicious Code Injection

SQL Injection is most popular in Code Injection Attack, the hacker attach the malicious codeinto the good code by inserting the field in the application. The motive behind the injectionis to steal the secured information which was intended to be used by a set of users.

Apart from SQL Injection, the other types of malicious code injection are XPath Injection,LDAP Injection, and Command Execution Injection. Similar to SQL Injection the XPathInjection deals with XML document.

b. Penetration Testing:

Penetration Testing is used to check the security of a computer or a network. The testprocess explores all the security aspects of the system and tries to penetrate the system.

c. Input validation:

Input validation is used to defend the applications from hackers. If the input is not validatedmostly in web applications it could lead to system crashes, database manipulation andcorruption.



d. Variable Manipulation

Variable manipulation is used as a method for specifying or editing the variables in aprogram. It is mostly used to alter the data sent to web server.

3. Database Level

a. SQL Injection

SQL Injection is used to hack the websites by changing the backend SQL statements, usingthis technique the hacker can steal the data from database and also delete and modify it.

20. Explain IEEE 829 standards and other Software Testing standards?

An IEEE 829 standard is used for Software Test Documentation, where it specifies format forthe set of documents to be used in the different stages software testing. The documentsare,

Test Plan- Test Plan is a planning document which has information about the scope,resources, duration, test coverage and other details.Test Design- Test Design document has information of test pass criteria with testconditions and expected results.Test Case- Test case document has information about the test data to be used.Test Procedure- Test Procedure has information about the test steps to be followed andhow to execute it.Test Log- Test log has details about the run test cases, test plans & fail status, order, andthe resource information who tested it.Test Incident Report- Test Incident Report has information about the failed testcomparing the actual result with expected result.Test Summary Report- Test Summary Report has information about the testing done andquality of the software, it also analyses whether the software has met the requirementsgiven by customer.

The other standards related to software testing are,

IEEE 1008 is for Unit TestingIEEE 1012 is for Software verification and validationIEEE 1028 is for Software InspectionsIEEE 1061 is for Software metrics and methodologyIEEE 1233 is for guiding the SRS developmentIEEE 12207 is for SLC process

21. What is Test Harness?

Test Harness is configuring a set of tools and test data to test an application in variousconditions, which involves monitoring the output with expected output for correctness.

The benefits of Test Harness are,

Productivity increase due to process automation.



Quality in the application.

22. What is the difference between bug log and defect tracking?

Bug Log: Bug Log document showing the number of defect such as open, closed, reopen or

deferred of a particular module

Defect Tracking- The process of tracking a defect such as symptom, whether reproducible /not, priority, severity and status.

23. What are Integration Testing and Regression Testing?

Integration Testing:

Combining the modules together & construct software architecture. To test the communication & data flow

White & Black box testing techniques are used

It is done by developer & tester

Regression Testing

It is re-execution of our testing after the bug is fixed to ensure that the build is freefrom bugs.

Done after bug is fixed

It is done by Tester

24. Explain Peer Review in Software Testing?

It is an alternative form of Testing, where some colleagues were invited to examine yourwork products for defects and improvement opportunities.Some Peer review approaches are,

Inspection

It is a more systematic and rigorous type of peer review. Inspections are more effective atfinding defects than are informal reviews.Ex: In Motorola's Iridium project nearly 80% of the defects were detected throughinspections where only 60% of the defects were detected through formal reviews.

Team Reviews: It is a planned and structured approach but less formal and less rigorouscomparing to Inspections.Walkthrough: It is an informal review because the work product's author describes it tosome colleagues and asks for suggestions. Walkthroughs are informal because they typicallydo not follow a defined procedure, do not specify exit criteria, require no managementreporting, and generate no metrics.

Or

A 'walkthrough' is an informal meeting for evaluation or informational purposes. Little orno preparation is usually required.Pair Programming: In Pair Programming, two developers work together on the same



program at a single workstation and continuously reviewing their work.

Peer Desk check

In Peer Desk check only one person besides the author examines the work product. It is aninformal review, where the reviewer can use defect checklists and some analysis methods to

increase the effectiveness.Passaround: It is a multiple, concurrent peer desk check where several people are invitedto provide comments on the product.

25. Explain Compatibility testing with an example?

Compatibility testing is to evaluate the application compatibility with the computingenvironment like Operating System, Database, Browser compatibility, backwardscompatibility, computing capacity of the Hardware Platform and compatibility of thePeripherals.

Example

If Compatibility testing is done on a Game application, before installing a game on acomputer, its compatibility is checked with the computer specification that whether it iscompatible with the computer having that much of specification or not.

26. What is Traceability Matrix?

Traceability Matrix is a document used for tracking the requirement, Test cases and thedefect. This document is prepared to make the clients satisfy that the coverage done iscomplete as end to end, this document consists of Requirement/Base line doc Ref No., Testcase/Condition, Defects / Bug id. Using this document the person can track the Requirementbased on the Defect id.

27. Explain Boundary value testing and Equivalence testing with some examples?

Boundary value testing is a technique to find whether the application is accepting theexpected range of values and rejecting the values which falls out of range.

Exmple

A user ID text box has to accept alphabet characters ( a-z ) with length of 4 to 10characters.BVA is done like this, max value: 10 pass; max-1: 9 pass;max+1=11 fail ;min=4 pass;min+1=5 pass;min-1=3 fail;Like wise we check the corner values and come out with a conclusion whether the

application is accepting correct range of values.

Equivalence testing is normally used to check the type of the object.

Example

A user ID text box has to accept alphabet characters (a - z) with length of 4 to 10characters.In +ve condition we have test the object by giving alphabets. i.e. a-z char only, after that



we need to check whether the object accepts the value, it will pass.In -ve condition we have to test by giving other than alphabets (a-z) i.e. A-Z, 0-9, blanketc, it will fail.

28. What is Security testing?

Security testing is the process that determines that confidential data stays confidentialOrTesting how well the system protects against unauthorized internal or external access,willful damage, etc?This process involves functional testing, penetration testing and verification.

29. What is Installation testing?

Installation testing is done to verify whether the hardware and software are installed andconfigured properly. This will ensure that all the system components were used during thetesting process. This Installation testing will look out the testing for a high volume data,error messages as well as security testing.

30. What is AUT?

AUT is nothing but "Application Under Test". After the designing and coding phase inSoftware development life cycle, the application comes for testing then at that time theapplication is stated as Application Under Test.

31. What is Defect Leakage?

Defect leakage occurs at the Customer or the End user side after the application delivery.After the release of the application to the client, if the end user gets any type of defects byusing that application then it is called as Defect leakage. This Defect Leakage is also calledas Bug Leakage.

32. What are the contents in an effective Bug report?

1. Project 2. Subject 3. Description

4. Summary

5. Detected By (Name of the Tester)

6. Assigned To (Name of the Developer who is supposed to the Bug)

7. Test Lead (Name)

8. Detected in Version

9. Closed in Version

10. Date Detected

11.

Expected Date of Closure

12. Actual Date of Closure

13. Priority (Medium, Low, High, Urgent)

14. Severity (Ranges from 1 to 5)

15. Status

16. Bug ID

17. Attachment 18. Test Case Failed (Test case that is failed for the Bug)



33. What is Error guessing and Error seeding?

Error Guessing is a test case design technique where the tester has to guess what faultsmight occur and to design the tests to represent them.Error Seeding is the process of adding known faults intentionally in a program for thereason of monitoring the rate of detection & removal and also to estimate the number of

faults remaining in the program.

34. What is Ad-hoc testing?

Ad hoc testing is concern with the Application Testing without following any rules or testcases.For Ad hoc testing one should have strong knowledge about the Application.

35. What are the basic solutions for the software development problems?

1. Basic requirements- A clear, detailed, complete, achievable, testable requirementhas to be developed. Use some prototypes to help pin down requirements. In nimble

environments, continuous and close coordination with customers/end-users isneeded. 2. Schedules should be realistic- enough time to plan, design, test, bug fix, re-test,

change, and document in the given schedule. Adequate

3. testing- testing should be started early, it should be re-tested after the bug fixed orchanged, enough time should be spend for testing and bug-fixing.

4. Proper study on initial requirements- be ready to look after more changes afterthe development has begun and be ready to explain the changes done to others.Work closely with the customers and end-users to manage expectations. This avoidsexcessive changes in the later stages.

5. Communication- conduct frequent inspections and walkthroughs in appropriatetime period; ensure that the information and the documentation is available on up-to-date if possible electronic. More emphasize on promoting teamwork and

cooperation inside the team; use prototypes and proper communication with theend-users to clarify their doubts and expectations.

36. What are the common problems in the software development process?

Inadequate requirements from the Client: if the requirements given by the client is notclear, unfinished and not testable, then problems may come.Unrealistic schedules: Sometimes too much of work is being given to the developer and askhim to complete in a Short duration, then the problems are unavoidable.Insufficient testing: The problems can arise when the developed software is not testedproperly.Given another work under the existing process: request from the higher management to

work on another project or task will bring some problems when the project is being testedas a team.Miscommunication: in some cases, the developer was not informed about the Clientsrequirement and expectations, so there can be deviations.

37. What is the difference between Software Testing and Quality Assurance (QA)?

Software Testing involves operation of a system or application under controlled conditionsand evaluating the result. It is oriented to 'detection'.



Quality Assurance (QA) involves the entire software development PROCESS- monitoring andimproving the process, making sure that any agreed-upon standards and procedures arefollowed, and ensuring that problems are found and dealt with. It is oriented to 'prevention'.

38. How to Test the water bottle?

Note: Before going to generate some test idea on how to test a water bottle, I would like toask few questions like:

1. Is it a bottle made up off glass, plastic, rubber, some metal, some kind of disposablematerials or any thing else?

2. Is it meant only to hot water or we can use it with other fluids like tea, coffee, softdrinks, hot chocolate, soups, wine, cooking oil, vinegar, gasoline, acids, molten lava(!) etc.?

3. Who is going to use this bottle? A school going kid, a housewife, some beveragemanufacturing company, an office-goer, a sports man, a mob protesting in a rally(going to use as missiles), an Eskimo living in an igloo or an astronaut in a spaceship?

These kinds of questions may allow a tester to know a product (that he is going to test) in abetter way. In our case, I am assuming that the water bottle is in form of a pet bottle andactually made up off either plastic or glass (there are 2 versions of the product) and isintended to be used mainly with water. About the targeted user, even the manufacturingcompany is not sure about them! (Sounds familiar! When a software company develops aproduct without clear idea about the users who are going to use the software!)

Test Ideas

1. Check the dimension of the bottle. See if it actually looks like a water bottle or acylinder, a bowl, a cup, a flower vase, a pen stand or a dustbin! [Build Verification

Testing!] 2. See if the cap fits well with the bottle.[Installability Testing!]

3. Test if the mouth of the bottle is not too small to pour water. [Usability Testing!]

4. Fill the bottle with water and keep it on a smooth dry surface. See if it leaks.[Usability Testing!]

5. Fill the bottle with water, seal it with the cap and see if water leaks when the bottleis tilted, inverted, squeezed (in case of plastic made bottle)! [Usability Testing!]

6. Take water in the bottle and keep it in the refrigerator for cooling. See whathappens. [Usability Testing!]

7. Keep a water-filled bottle in the refrigerator for a very long time (say a week). Seewhat happens to the water and/or bottle. [Stress Testing!]

8. Keep a water-filled bottle under freezing condition. See if the bottle expands (if

plastic made) or breaks (if glass made). [Stress Testing!] 9. Try to heat (boil!) water by keeping the bottle in a microwave oven! [Stress Testing!] 10. Pour some hot (boiling!) water into the bottle and see the effect. [Stress Testing!]

11. Keep a dry bottle for a very long time. See what happens. See if any physical orchemical deformation occurs to the bottle.

12. Test the water after keeping it in the bottle and see if there is any chemical change.See if it is safe to be consumed as drinking water.

13. Keep water in the bottle for sometime. And see if the smell of water changes.



14. Try using the bottle with different types of water (like hard and soft water).[Compatibility Testing!]

15. Try to drink water directly from the bottle and see if it is comfortable to use. Orwater gets spilled while doing so. [Usability Testing!]

16. Test if the bottle is ergonomically designed and if it is comfortable to hold. Also see ifthe center of gravityof the bottle stays low (both when empty and when filled with

water) and it does not topple down easily. 17. Drop the bottle from a reasonable height (may be height of a dining table) and see if

it breaks (both with plastic and glass model). If it is a glass bottle then in most casesit may break. See if it breaks into tiny little pieces (which are often difficult to clean)or breaks into nice large pieces (which could be cleaned without much difficulty).[Stress Testing!] [Usability Testing!]

18. Test the above test idea with empty bottles and bottles filled with water. [StressTesting!]

19. Test if the bottle is made up of material, which is recyclable. In case of plastic madebottle test if it is easily crushable.

20. Test if the bottle can also be used to hold other common household things likehoney, fruit juice, fuel, paint, turpentine, liquid wax etc. [Capability Testing!]

39. What is Portlet Testing ?

Following are the features that should be concentrated while testing a portlet

i. Test alignment/size display with multiple style sheets and portal configurations. When youconfigure a portlet object in the portal, you must choose from the following alignments:

a. Narrow portlets are displayed in a narrow side column on the portal page. Narrowportlets must fit in a column that is fewer than 255 pixels wide.b. Wide portlets are displayed in the middle or widest side column on the portal page. Wideportlets fit in a column fewer than 500 pixels wide.

ii. Test all links and buttons within the portlet display. (if there are errors, check that allforms and functions are uniquely named, and that the preference and gateway settings areconfigured correctly in the portlet web service editor.)

iii. Test setting and changing preferences. (if there are errors, check that the preferencesare uniquely named and that the preference and gateway settings are configured correctlyin the portlet web service editor.)

iv. Test communication with the backend application. Confirm that actions executed throughthe portlet are completed correctly. (if there are errors, check the gateway configuration inthe portlet web service editor.)

v. Test localized portlets in all supported languages. (if there are errors, make sure that the

language files are installed correctly and are accessible to the portlet.)

vi. If the portlet displays secure information or uses a password, use a tunnel tool toconfirm that any secure information is not sent or stored in clear text.

Vii. If backwards compatibility is supported, test portlets in multiple versions of the portal.

40. What is Equivalence Partitioning?



Concepts: Equivalence partitioning is a method for deriving test cases. In this method,classes of input conditions called equivalence classes areidentified such that each member of the class causes the same kind ofprocessing and output to occur. In this method, the tester identifies various equivalenceclasses for partitioning. A class is a set of input conditions that are is likely to be handledthe same way by the system. If the system were to handle one case in the class

erroneously, it would handle all cases erroneously.

41. Why Learn Equivalence Partitioning?

Equivalence partitioning drastically cuts down the number of test cases required to test asystem reasonably. It is an attempt to get a good 'hit rate', to find the most errors with thesmallest number of test cases.

DESIGNING TEST CASES USING EQUIVALENCE PARTITIONING

To use equivalence partitioning, you will need to perform two steps.

1. Identify the equivalence classes

2.

Design test cases

STEP 1:

IDENTIFY EQUIVALENCE CLASSES Take each input condition described in the specificationand derive at least two equivalence classes for it. One class represents the set of caseswhich satisfy the condition (the valid class) and one represents cases which do not (theinvalid class) Following are some general guidelines for identifying equivalence classes: a) Ifthe requirements state that a numeric value is input to the system and must be within arange of values, identify one valid class inputs which are within the valid range and twoinvalid equivalence classes inputs which are too low and inputs which are too high. Forexample, if an item in inventory can have a quantity of - 9999 to + 9999, identify the

following classes:

1. One valid class: (QTY is greater than or equal to -9999 and is less than or equal to9999). This is written as (- 9999 < = QTY < = 9999)

2. The invalid class (QTY is less than -9999), also written as (QTY < -9999)3. The invalid class (QTY is greater than 9999) , also written as (QTY >9999) b) If the

requirements state that the number of items input by the system at some point mustlie within a certain range, specify one valid class where the number of inputs iswithin the valid range, one invalid class where there are too few inputs and oneinvalid class where there are, too many inputs.

42. What are two types of Metrics?

1. Process metrics: Primary metrics are also called as Process metrics. This is themetric the Six Sigma practitioners care about and can influence. Primary metrics arealmost the direct output characteristic of a process. It is a measure of a process andnot a measure of a high-level business objective. Primary Process metrics are usuallyProcess Defects, Process cycle time and Process consumption.

2. Product metrics: Product metrics quantitatively characterize some aspect of thestructure of a software product, such as a requirements specification, a design, orsource code.



43. What is the Outcome of Testing?

A stable application, performing its task as expected.

44. Why do you go for White box testing, when Black box testing is available?

A benchmark that certifies Commercial (Business) aspects and also functional (technical)aspects is objectives of black box testing. Here loops, structures, arrays, conditions, files,etc are very micro level but they arc Basement for any application, So White box takesthese things in Macro level and test these things

45. What is Baseline document, Can you say any two?

A baseline document, which starts the understanding of the application before the tester,starts actual testing. Functional Specification and Business Requirement Document

46. Tell names of some testing type which you learnt or experienced?

Any 5 or 6 types which are related to companies profile is good to say in the interview,

1. Ad - Hoc testing2. Cookie Testing

3. CET (Customer Experience Test)

4. Depth Test 5. Event-Driven6. Performance Testing7. Recovery testing8. Sanity Test9. Security Testing10. Smoke testing11. Web Testing

47. What exactly is Heuristic checklist approach for unit testing?

It is method of achieving the most appropriate solution of several found by alternativemethods is selected at successive stages testing. The checklist Prepared to Proceed is calledHeuristic checklist

48. What is a Data Guideline?

Data Guidelines are used to specify the data required to populate the test bed and preparetest scripts. It includes all data parameters that are required to test the conditions derivedfrom the requirement / specification The Document, which supports in preparing test dataare called Data guidelines

49. Why do you go for Test Bed?

When Test Condition is executed its result should be compared to Test result (expectedresult), as Test data is needed for this here comes the role of test Bed where Test data ismade ready.

50. Why do we prepare test condition, test cases, test script (Before StartingTesting)?



These are test design document which are used to execute the actual testing Without whichexecution of testing is impossible, finally this execution is going to find the bugs to be fixedso we have prepare this documents.

51. Is it not waste of time in preparing the test condition, test case & Test Script?

No document prepared in any process is waste of rime, That too test design documentswhich plays vital role in test execution can never be said waste of time as without whichproper testing cannot be done.

52. How do you go about testing of Web Application?

To approach a web application testing, the first attack on the application should be on itsperformance behavior as that is very important for a web application and then transfer ofdata between web server and .front end server, security server and back end server.

53. What kind of Document you need for going for a Functional testing?

Functional specification is the ultimate document, which expresses all the functionalities ofthe application and other documents like user manual and BRS are also need for functionaltesting. Gap analysis document will add value to understand expected and existing system.

54. Can the System testing be done at any stage?

No, .The system as a whole can be tested only if all modules arc integrated and all moduleswork correctly System testing should be done before UAT (User Acceptance testing) andBefore Unit Testing.

55. What is Mutation testing & when can it be done?

Mutation testing is a powerful fault-based testing technique for unit level testing. Since it isa fault-based testing technique, it is aimed at testing and uncovering some specific kinds offaults, namely simple syntactic changes to a program. Mutation testing is based on twoassumptions: the competent programmer hypothesis and the coupling effect. Thecompetent programmer hypothesis assumes that competent programmers turn to writenearly "correct" programs. The coupling effect stated that a set of test data that canuncover all simple faults in a program is also capable of detecting more complex faults.Mutation testing injects faults into code to determine optimal test inputs.

56. Why it is impossible to test a program completely?

With any software other than the smallest and simplest program, there are too manyinputs, too many outputs, and too many path combinations to fully test. Also, software

specifications can be subjective and be interpreted in different ways.

57. How will you review the test case and how many types are there?

There are 2 types of review:

Informal Review: technical lead reviewing.Peer Review: by a peer at the same organization (walkthrough? technical - inspection).



OrReviews:

1. Management Review

2. Technical Review

3. Code Review

4.

Formal Review (Inspections and Audits) 5. Informal Review (Peer Review and Code Review)

and coming to walk through....

objectives of Reviews:

1. To find defects in requirements. 2. To find defects in Design. 3. To identify deviations in any process and also provide valued suggestions to improve

the process.

58. What do you mean by Pilot Testing?

Pilot testing involves having a group of end users try the system prior to its fulldeployment in order to give feedback on IIS 5.0 features and functions.OrPilot Testing is a Testing Activity which resembles the Production Environment.

It is Done Exactly between UAT and Production Drop. Few Users who simulate the Production environment to continue the Business

Activity with the System. They Will Check the Major Functionality of the System before going into production.

This is basically done to avoid the high-level Disasters.

Priority of the Pilot Testing Is High and Issues Raised in Pilot Testing has to be FixedAs Soon As Possible.

59. What is SRS and BRS in manual testing?

BRS is Business Requirement Specification which means the client who want to make theapplication gives the specification to software development organization and then theorganization convert it to SRS (Software requirement Specification) as per the need of thesoftware.

60. What is Smoke Test and Sanity Testing? When will use the Above Tests?

Smoke Testing: It is done to make sure if the build we got is testable or not, i.e to check

for the testability of the build also called as "day 0" check. Done at the 'build level'Sanity Testing: It is done during the release phase to check for the main functionalitieswithout going deeper. Sometimes also called as subset of regression testing. When norigorous regression testing is done to the build, sanity does that part by checking majorfunctionalities. Done at the 'release level'

61. What is debugging?

Debugging is finding and removing "bugs" which cause the program to respond in a way



that is not intended.

62. What is determination?

Determination has different meanings in different situations. Determination means a strongintention or a fixed intention to achieve a specific purpose. Determination, as a core value,

means to have strong will power in order to achieve a task in life. Determination means astrong sense of self-devotion and self-commitment in order to achieve or perform a giventask. The people who are determined to achieve various objectives in life are known tosucceed highly in various walks of life.

Another way, it could also mean calculating, ascertaining or even realizing a specificamount, limit, character, etc. It also refers to a certain result of such ascertaining or evendefining a certain concept.

It can also mean to reach at a particular decision and firmly achieve its purpose.

63. What is exact difference between Debugging & Testing?

Testing is nothing but finding an error/problem and its done by testers where as debuggingis nothing but finding the root cause for the error/problem and that is taken care bydevelopers.OrDebugging- is removing the bug and is done by developer.

Testing - is identifying the bug and is done by tester.

64. What is fish model can you explain?

Fish model explains the mapping between different stages of development and testing.

Phase 1

Information gathering takes place and here the BRS document is prepared.

Phase 2

Analysis takes place

During this phase, development people prepare SRS document which is a combination offunctional requirement specification and system requirement specification. During thisphase, testing people are going for reviews.

Phase-3

Design phase

Here HLD and LLD high level design document and low level design documents are preparedby development team. Here, the testing people are going for prototype reviews.

Phase-4



coding phase

White box testers start coding and white box testing is being conducted by testing team.

Phase-5

testing phase

White box testing takes place by the black box test engineers.

Phase-6

release and maintenance.

65. What is Conformance Testing?

The process of testing that an implementation conforms to the specification on which it isbased. Usually applied to testing conformance to a formal standard.

66. What is Context Driven Testing?

The context-driven school of software testing is flavor of Agile Testing that advocatescontinuous and creative evaluation of testing opportunities in light of the potentialinformation revealed and the value of that information to the organization right now.

67. What is End-to-End testing?

Similar to system testing, the 'macro' end of the test scale involves testing of a completeapplication environment in a situation that mimics real-world use, such as interacting with adatabase, using network communications, or interacting with other hardware, applications,or systems if appropriate.

68. When the testing should be ended?

Testing is a never ending process, because of some factors testing May terminates.The factors may be most of the tests are executed, project deadline, test budget depletion,bug rate falls down below the criteria.

69. What is Parallel/Audit Testing?

Testing where the user reconciles the output of the new system to the output of the currentsystem to verify the new system performs the operations correctly.

70. What are the roles of glass-box and black-box testing tools?

Black-box testing

It is not based on knowledge of internal design or code. Tests are based on requirementsand functionality. Black box testing is used to find the errors in the following.

1. Interface errors

2. Performance errors



3. Initialization errors

4. Incorrect or missing functionality

5. Errors while accessing external database

Glass-box testing

It is based on internal design of an application code. Tests are based on path coverage,branch coverage, and statement coverage. It is also known as White Box testing.

1. White box test cases can check for;

2. All independent paths with in a module are executed atleast once

3. Execute all loops

4. Exercises all logical decisions

5. Exercise internal data structure to ensure their validity

71. What is your experience with change control? Our development team has only10 members. Do you think managing change is such a big deal for us?

Whenever the modifications happening to the actual project all the correspondingdocuments are adapted on the information. So as to keep the documents always in syncwith the product at any point of time

72. What is GAP ANALYSIS?

The gap analysis can be done by traceability matrix that means tracking down eachindividual requirement in SRS to various work products.

73. How do you know when your code has met specifications?

With the help of traceability matrix. All the requirements are tracked to the test cases.When all the test cases are executed and passed is an indication that the code has met therequirements.

74. At what stage of the life cycle does testing begin in your opinion?

Testing is a continuous process and it starts as and when the requirement for the project /product begins to be framed.Requirements phase: testing is done to check whether the project/product details arereflecting clients ideas or giving an idea of complete project from the clients perspective (ashe wished to be) or not.

75. What are the properties of a good requirement?

Requirement specifications are important and one of the most reliable methods of insuringproblems in a complex software project. Requirements are the details describing anapplication's externally perceived functionality and properties. Requirements should beclear, complete, reasonably detailed, cohesive, attainable and testable.

76. How do you scope, organize, and execute a test project?

The Scope can be defined from the BRS, SRS, FRS or from functional points. It may beanything that is provided by the client. And regarding organizing we need to analyze the



functionality to be covered and who will testing the modules and pros and cons of theapplication. Identify the number if test cases, resource allocation, what are the risks that weneed mitigate all these come into picture.Once this is done it is very easy to execute based on the plan what we have chalked out.

77. How would you ensure 100% coverage of testing?

We can not perform 100% testing on any application. but the criteria to ensure testcompletion on a project are:

1. All the test cases are executed with the certain percentage of pass.2. Bug falls below a certain level3. Test budget depleted4. Dead lines reached (project or test)

5. When all the functionalities are covered in a test cases6. All critical & high bugs must have a status of CLOSED

78. Do you go about testing a web application?

Ideally to test a web application, the components and functionality on both the client andserver side should be tested. But it is practically impossible

The best approach to examine the project's requirements, set priorities based on riskanalysis, and then determine where to focus testing efforts within budget and scheduleconstraints.To test a web application we need to perform testing for both GUI and client-serverarchitecture.

Based on many factors like project requirements, risk analysis, budget and schedule, wecan determine that what kind of testing will be appropriate for your project. We can performunit n integration testing, functionality testing, GUI testing, usability testing, compatibility

testing, security testing, performance testing, recovery testing and regression testing.

79. What are your strengths?

I'm well motivated, well-organized, good team player, dedicative to work and I've got astrong desire to succeed, and I'm always ready and willing to learn new information andskills.

80. When should you begin testing?

For any Project, testing activity will be there from starting onwards, After the Requirementsgathering, Design Document (High and Low) will be prepared, that will be tested, whetherthey are confirming to requirements or not, Design then Coding- White box will be done,after the Build or System is ready, Integration followed by functional testing will be done,Till the product or Project was stable. After the product or project is stable, then testing willbe stopped.

81. When should you begin test planning?

Test planning is done by test lead. As a test lead test planning begins when TRM is finalizedby project manager and handover to the test lead. Here test lead have some responsibilitiesthose are,



1. Testing team formation2. identifying tactical risks3. preparing test plan4. Reviews on test plans

82. Would you like to work in a team or alone, why?

I would like to work in a team. Because the process of software developmentis like a relay race where many runners have to contribute in their respective laps. It isimportant because the complexity of work and degree of efforts required is beyond level ofan individual.

83. When should testing Start in a project? Why?

Testing in a continuous activity carried out at every stage of the project. You first testeverything that you get from the client. As tester (technical tester), my work will start assoon as the project starts.

84. Have you ever created a test plan?

This is just a sample answer - "I have never created any test plan. I developed andexecuted testcase. But I was involved/ participated actively with my Team Leader whilecreating Test Plans."

85. Define quality for me as you understand it

It is software that is reasonably bug-free and delivered on time and within the budget,meets the requirements and expectations and is maintainable.

86. What is the role of QA in a development project?

Quality AssuranceGroup assures the Quality it must monitor the whole development process. they are mostconcentration on prevention of bugs.

It must set standards, introduce review procedures, and educate people into better ways todesign and develop products.

87. How involved where you with your Team Lead in writing the Test Plan?

As per my knowledge Test Member are always out of scope while preparing the Test Plan,Test Plan is a higher level document for Testing Team. Test Plan includes Purpose, scope,Customer/Client scope, schedule, Hardware, Deliverables and Test Cases etc. Test planderived from PMP (Project Management Plan). Team member scope is just go through TESTPLAN then they come to know what all are their responsibilities, Deliverable of modules.

Test Plan is just for input documents for every testing Team as well as Test Lead.

88. What processes/methodologies are you familiar with?

Methodology



1. Spiral methodology

2. Waterfall methodology. these two are old methods.

3. Rational unified processing. this is from I B M and

4. Rapid application development. this is from Microsoft office.

89. What is globalization testing?

The goal of globalization testing is to detect potential problems in application design thatcould inhibit globalization. It makes sure that the code can handle all international supportwithout breaking functionality that would cause either data loss or display problems.

90. What is base lining?

Base lining: Process by which the quality and cost effectiveness of a service is assessed,usually in advance of a change to the service. Base lining usually includes comparison of theservice before and after the Change or analysis of trend information. The termBenchmarking is normally used if the comparison is made against other enterprises.

For example:

If the company has different projects. For each project there will be separate test plans.This test plans should be accepted by peers in the organization after modifications. Thatmodified test plans are the baseline for the testers to use in different projects. Any furthermodifications are done in the test plan. Present modified becomes the baseline. Becausethis test plan becomes the basis for running the testing project.

91. Define each of the following and explain how each relates to the other: Unit,System and Integration testing.

Unit testing

it is a testing on each unit (program)

System testin

This is a bottleneck stage of our project. This testing done after integration of all modules tocheck whether our build meets all the requirements of customer or not. Unit and integrationtesting is a white box testing which can be done by programmers. System testing is a blackbox testing which can be done by people who do not know programming. The hierarchy ofthis testing is unit testing integration testing system testing

Integration testing: integration of some units called modules. the test on these modulesis called integration testing (module testing).

92. Who should you hire in a testing group and why?

Testing is an interesting part of software cycle. and it is responsible for providing an qualityproduct to a customer. It involves finding bugs which is more difficult and challenging. Iwanna be part of testing group because of this.

93. What do you think the role of test-group manager should be? Relative tosenior management? Relative to other technical groups in the company? Relative



to your staff?

ROLES OF test-group manager INCLUDE

Defect find and close rates by week, normalized against level of effort (are wefinding defects, and can developers keep up with the number found and the ones

necessary to fix?) Number of tests planned, run, passed by week (do we know what we have to test,

and are we able to do so?) Defects found per activity vs. total defects found (which activities find the most

defects?) Schedule estimates vs. actual (will we make the dates, and how well do we

estimate?) People on the project, planned vs. actual by week or month (do we have the people

we need when we need them?) Major and minor requirements changes (do we know what we have to do, and does it

change?)

94. What criteria do you use when determining when to automate a test or leave itmanual?

The Time and Budget both are the key factors in determining whether the test goes onManual or it can be automated. Apart from that the automation is required for areas such asFunctional, Regression, Load and User Interface for accurate results.

95. How do you analyze your test results? What metrics do you try to provide?

Test results are analyzed to identify the major causes of defect and which is the phase thathas introduced most of the defects. This can be achieved through cause/effect analysis orPareto analysis. Analysis of test results can provide several test matrics. Where matrices aremeasure to quantify s/w, s/w development resources and s/w development process. Few

matrices which we can provide are:

Defect density: total no of defects reported during testing/size of project

Test effectiveness'/(t+uat)where t: total no of defect recorded during testing

and UAT: total no of defect recorded during use acceptance testing

Defect removal efficiency(DRE): (total no of defect removed / total no of defectinjected)*100

96. How do you perform regression testing?

Regression Testing is carried out both manually and automation. The automatic tools aremainly used for the Regression Testing as this is mainly focused repeatedly testing thesame application for the changes the application gone through for the new functionality,after fixing the previous bugs, any new changes in the design etc. The regression testinginvolves executing the test cases, which we ran for finding the defects. Whenever anychange takes place in the Application we should make sure, the previous functionality is stillavailable without any break. For this reason one should do the regression testing on theapplication by running/executing the previously written test cases.



97. Describe to me when you would consider employing a failure mode and effectanalysis

FMEA (Failure Mode and Effects Analysis) is a proactive tool, technique and quality methodthat enables the identification and prevention of process or product errors before they

occur. Failure modes and effects analysis (FMEA) is a disciplined approach used to identifypossible failures of a product or service and then determine the frequency and impact of thefailure.

98. What is UML and how to use it for testing?

The Unified Modeling Language is a third-generation method for specifying, visualizing, anddocumenting the artifacts of an object-oriented system under development From the inside,the Unified Modeling Language consists of three things:

1. A formal metamodel2. A graphical notation3. A set of idioms of usage

99. What you will do during the first day of job?

In my present company HR introduced me to my colleagues. and i known the followingthings.

1. What is the organization structure?2. What is the current project developing, on what domain etc.,3. I will know to whom i have to report and what r my other responsibilities.

100. What is IEEE? Why is it important?

Organization of engineers Scientists and students involved in electrical, electronics, andrelated fields. It is important because it functions as a publishing house and standards-making body.

101. Define Verification and Validation. Explain the differences between the two.

Verification - Evaluation done at the end of a phase to determine that requirements areestablished during the previous phase have been met. Generally Verification refers to theoverall s/w evaluation activity, including reviewing, inspecting, checking and auditing.

Validation: - The process of evaluating s/w at the end of the development process toensure compliance with requirements. Validation typically involves actual testing and takes

place after verification is complete.

Or

Verification: Whether we are building the product right?

Validation: Whether we are building the right product/System?

102. Describe a past experience with implementing a test harness in the



development Of software

Harness: an arrangement of straps for attaching a horse to a cart.Test Harness: This class of tool supports the processing of tests by working it almostpainless to

1.

Install a candidate program in a test environment2. Feed it input data3. Simulate by stubs the behavior of subsidiary modules.

103. What criteria do you use when determining when to automate a test or leaveit manual?

The Time and Budget both are the key factors in determining whether the test goes onManual or it can be automated. Apart from that the automation is required for areas such asFunctional, Regression, Load and User Interface for accurate results.

104. What would you like to do five years from now?

I would like to be in a managerial role, ideally working closely with external clients. I haveworked in client-facing roles for more than two years and I enjoy the challenge of keepingthe customer satisfied. I think it's something I'm good at. I would also like to take onadditional responsibility within this area, and possibly other areas such as Finally, I'd like tobe on the right career path towards eventually becoming a Senior Manager within thecompany. I'm very aware that these are ambitious goals, however I feel through hard workand dedication they are quite attainable.

105. Define each of the following and explain how each relates to the other: Unit,System, and Integration testing

Unit system comes first. Performed by a developer.

Integration testing comes next. Performed by a tester System testing comes last-Performed by a tester.

106. What is IEEE? Why is it important?

"Institute of Electrical & Electronic Engineers" Organization of engineers, scientists andstudents involved in electrical, electronics, and related fields. It also functions as apublishing house and standards-making body.

107. What is the role of QA in a company that produces software?

The role of the QA in the company is to produce a quality software and to ensure that it

meets all the requirements of its customers before delivering the product.

108. How would you build a test team?

Building a test team needs a number of factors to judge. Firstly, you have to consider thecomplexity of the application or project that is going to be tested. Next testing, time allottedlevels of testing to be performed. With all these parameters in mind you need to decide theskills and experience level of your testers and how many testers.



109. In an application currently in production, one module of code is beingmodified. Is it necessary to retest the whole application or is it enough to justtest functionality associated with that module?

It depends on the functionality related with that module. We need to check whether thatmodule is inter-related with other modules. If it is related with other modules, we need to

test related modules too. Otherwise, if it is an independent module, no need to test othermodules.

110. What are ISO standards? Why are they important?

ISO 9000 specifies requirements for a Quality Management System overseeing theproduction of a product or service. It is not a standard for ensuring a product or service is ofquality; rather, it attests to the process of production, and how it will be managed andreviewed.

For ex a few:

ISO 9000:2000Quality management systems. Fundamentals and vocabulary

ISO 9000-1:1994Quality management and quality assurance standards. Guidelines for selection and use

ISO 9000-2:1997Quality management and quality assurance standards. Generic guidelines for the applicationof ISO 9001, ISO 9002 and ISO 9003

ISO 9000-3:1997Quality management and quality assurance standards. Guidelines for the application of ISO9001:1994 to the development, supply, installation and maintenance of computer software

ISO 9001:1994Quality systems. Model for quality assurance in design, development, production,installation and servicing

ISO 9001:2000

Quality management systems. Requirements

111. What is the Waterfall Development Method and do you agree with all thesteps?

Waterfall approach is a traditional approach to the s/w development. This will work out of itproject is a small one (Not complex).Real time projects need spiral methodology as SDLC.Some product based development can follow Waterfall, if it is not complex. Production costis less if we follow waterfall method.

112. What is migration testing?



Changing of an application or changing of their versions and conducting testing is migrationtesting. Testing of programs or procedures used to convert data from existing systems foruse in replacement systems.

113. What is terminology? Why testing Necessary fundamental test processpsychology of testing Testing Terminologies

Error: a human action that produces an incorrect result.

Fault: a manifestation of an error in software.

Failure: a deviation of the software from its expected delivery or service.

Reliability: the probability that the software will not cause the failure of the system for aspecified time under specified conditions.

Why Testing is Necessary

Testing is necessary because software is likely to have faults in it and it is better (cheaper,quicker and more expedient) to find and remove these faults before it is put into liveoperation. Failures that occur during live operation are much more expensive to deal withthan failures than occur during testing prior to the release of the software. Of course otherconsequences of a system failing during live operation include the possibility of the softwaresupplier being sued by the customers!

Testing is also necessary so we can learn about the reliability of the software (that is, howlikely it is to fail within a specified time under specified conditions).

114. What is UAT testing? When it is to be done?

UAT stands for 'User acceptance Testing' This testing is carried out with the user perspective

and it is usually done before a releaseUAT stands for User Acceptance Testing. It is done by the end users along with testers tovalidate the functionality of the application. It is also called as Pre-Production testing.

115. How to find that tools work well with your existing system?

I think we need to do a market research on various tools depending on the type ofapplication we are testing. Say we are testing an application made in VB with an OracleDatabase, and then Win runner is going to give good results. But in some cases it may not,say your application uses a lots of 3rd party Grids and modules which have been integratedinto the application. So it depends on the type of application u r testing.

Also we need to know what sort of testing will be performed. If u need to test theperformance, u cannot use a record and playback tool, u need a performance testing toolsuch as Load runner.

116. What is the difference between a test strategy and a test plan?

TEST PLAN: IT IS PLAN FOR TESTING.IT DEFINES SCOPE, APPROACH, ANDENVIRONEMENT.



TEST STRATEGY: A TEST STRATEGY IS NOT A DOCUMENT.IT IS A FRAMEWORK FORMAKING DECISIONS ABOUT VALUE.

117. What is Scenarios in term of testing?

Scenario means development. We define scenario by the following definition: Set of test

cases that ensure the business process flows are tested from end to end. It may beindependent tests or a series of tests that follow each other, each dependant on the outputof the previous one. The term test scenario and test case are often used synonymously.

118. Explain the differences between White-box, Gray-box, and Black-box testing?

Black box testing Tests are based on requirements and functionality. Not based on anyknowledge of internal design or code.

White box testing Tests are based on coverage of code statements, branches, paths,conditions. Based on knowledge of the internal logic of an application's code.

Gray Box Testing A Combination of Black and White Box testing methodologies, testing apiece of software against its specification but using some knowledge of its internal workings.

119. What is structural and behavioral Testing?

Structural Testing

It is basically the testing of code which is called white box testing.

Behavioral Testing

It is also called functional testing where the functionality of software is being tested. This

kind of testing is called black box testing.

Structural Testing

It's a White Box Testing Technique. Since the testing is based on the internal structure ofthe program/code & hence it is called as Structural Testing.

Behavioral Testing:

It's a Black Box Testing Technique. Since the testing is based on the externalbehavior/functionality of the system /application & hence it is called as Behavioral Testing.

120. How does unit testing play a role in the development / Software lifecycle?

We can catch simple bugs like GUI, small functional Bugs during unit testing. This reducestesting time. Overall this saves project time. If developer doesn't catch this type of bugs,this will come to integration testing part and if it catches by a tester, this need to gothrough a Bug life cycle and consumes a lot of time.



121. What made you pick testing over another career?

Testing is one aspect which is very important in the Software Development Life Cycle(SDLC). I like to be part of the team which is responsible for the quality of the applicationbeing delivered. Also, QA has broad opportunities and large scope for learning varioustechnologies. And of course it has lot more opportunities than the Development.

Sample Test Case:

Test

Case

ID

Test Case

Description

Input

Data

Expected

Result

Actual

Result Pass/Fail

Remarks

Sample Bug Case:

S. no Links BugID

DescriptionInitial BugStatus

RetestingBug Status

Conf Bug Status

Part – 3

Manual Testing Terminology

1. Differentiate between QA and QC? QA:

It is process oriented. It envolve in entire process of software developement. 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? Testcase is set of input values, execution preconditions,expected results and executionpostconditions, developed for a particular objective or test conditons, such as to exercise a paticularprogram 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 likeintroduction,objectives,test stratergy,scope,test items,program modules userprocedures,features to be tested features not to tested approach,pass or fail criteria,testingprocess,test deliverables,testing,tasks,responsibilities,resources,schedu le,environmental requirements,risks & contingencies,change management procedures,planapprovals,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 theapplication and sends the marshal id to the tester.The tester is the one who gives all the input/outputand checks whether he is getting reqd output or not.A developer is the one who works on insideinterfacing 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 smoketest.smoke test is the first test which is done by the testing team.this is according to the testingteam.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.Projectmanagers 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 functionalcomponent of the application...i.e.minimize button,transfer button,links etc.i.e we check what is eachcomponent doing in that application... regression testing is the testing the behaviour of the application of the unchanged areas when there isa change in the build.i.e we chk whether the changed requirement has altered the behaviour of theunchanged areas.the impacted area may be the whole of the application orsome part of the application...

9. 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.forexample, when you are testing a bank application ,in account balence it shows the100$as the available balence.but in database it shows the 120$. main thing is "integration done bythe developers and integration testing done by the testers"

10. Do u know abt configuration management tool,what is the purpose of maintaining all thedocuments 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 forex).Then you send it for Peer Review .They will provide some comments and that document will besaved 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 butthey won't be complete. In general we look at 1. Data Correctness (Defaults)2. Data Storage/Retreival3. Database Connectivity (across multiple platforms) 4. Database Indexing5. Data Integrity 6. Data Security

12. Suppose if you press a link in yahooshopping site in leads to some other companywebsite?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 thelink 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?

13. What are the contents of FRS?

F → Function BehavioursR → 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.

14. 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"

15. 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 orrelease. 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 basicrequirement.

Eg., The code is to generate some values with some vaild input conditions. The priority will beassigned so based on the following conditions: a> It is not accepting any valueb> 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 displayedcorrectly but after saving changes it gave some address value from thestack 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 corectly,it would give a negative impact.egICICC is spelled as a tittle for the project of the concern ICICI.then it is a high severity,low prioritydefect.

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

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(withoutbrowser) is an example for client -server.(The companyfirewalls for the server are not open to outside world. Outside people cannot access theapplication.)So there will be limited number of people using that application. Testing an application in internet(using browser) is called webtesting. The application which isaccessable 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 bedone 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.

20. Explain your web application archtechture?web application is tested in 3 phases 1. web tier testing --> browser compatibility2. middle tier testing --> functionality, security 3. data base tier testing --> database integrity, contents

21. Suppose the product/appication has to deliver to client at 5.00PM,At that time you or yourteam member caught a high severity defect at 3PM.(Remember defect is high severity)Butthe 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 ispreyority 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 tofind workarounds for the defect and mention these issues in the release notes as known issues orknown limitations or known bugs. Here the workaround means remeady process to be followed toovercome the defect effect. 3.Normally this known issues or known limitations(defects) will be fixed in next version or next releaseof 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 everwe are dipositing/withdrawing money it is not showing any conformation message but actually at theback 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 butas end user is not getting any conformation message so he/she will beconfuse 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 developer4)->if accepted moves to step5 else sends the bug to tester gain 5)fixed by developer -> 6)regression testing-> 7)no problem inbuilt and signoff8)->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 sheetMention : The Feture that been effected. mention : Test Case ID (Which fail you can even mention any other which aredependency on this bug) Mention : Actual Behavior Mention : Expected Behavior as mentioned in Test Case or EFS or EBS or SRSdocument 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 testcaseyou found some defect for which testcase is not prepared,thwn how you can report thebug?

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

26. 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 webapplication are 3 trier & client based are 2 trier.In web based changes are made at one place & it isrefelected on other layers also whereas client based separate changes need be installed on clientmachine also.

27. 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 resourcesin 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 testcases can you write per a day, an average figure? Complex test cases 4-7 per day Medium test cases 10-15 per dayNormal test cases 20-30 per day

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

30. 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 areenough.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 apllication will be tested with entire new set of data. DataDriven Testing(DDT)-It is a Automated testing process inwhich application is tested with multipletest data.DDT is very easy procedure than retesting because the tester should sit and need to givedifferent new inputsmanually from front end and it is very tedious and boringprodedure.

32. What is regression testing?After the Bug fixed ,testing the application whether the fixed bug is affecting remaining functionality ofthe application or not.Majorly in regression testing Bug fixed module and it'sconnected modules are checked for thier integrity after bug fixation.

33. How do u test web application?

Web application testing

Should 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 asportability) 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

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 bemanipulated. In this case the old test cases will be updated or completely re writtenaccording to new features of the application where bug fixed area.Here possible areas are old testcases will be executed as usual or some new testcases will be added to existing testcases or some testcases may be deleted.

35. What are 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 clientside. 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 webor client server application cleint side scripting is good because it won't send the unwanted input's to server for validation.fromfrontend 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 compromisingwith 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 report3.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 asdevelopper 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 abovemethod.

37. If u are only person in the office and client asked u for some changes and u didn,t get whatthe client asked for what will u do?

One thing here is very important. Nobody will ask test engineer to change software that isnot your duty, even if it is related to testing and anybody is not there try to listen carefully if you arenot 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,Equaltobuttons.The testcases should be focussed only on add-functionality but mot GUI.What arethose 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 buttonforequalto u should press 'equalto' labled button 0+1=here + and = positions will not varyso firstnumber position can be varied from 0 to 9 i.e from permutation and combinations u can fill that spacein 10 waysin the same waysecond number position can be varied from 0 to 9 i.e from permutationand 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 arange 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 areenough to test the calculator functionality.

40. 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 acceptonly Strings.By providing only String as input data to the textbox & to check whether its workingproperly or not means it is Positive Testing.If giving the input other than String means it is negativeTesting..

41. How will you prepare Test plan. What are the techniques involved in preparing the Testplan.

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 areresolved. Project milestones: dead lines

42. 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 application6.closed/reopened: if it is ok tester gives closed stauselse he reopens and sends back to developer.

43. Expalin about metrics Management?



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

44. 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 stablein the latest and the previous versions

45. How do you review testcase?? Type of Review ?Types of reviewing test cases depends upon company standards,viz , peer review,team leadreview,roject manager review. Some times client may also review the test cases reg what is approachfollowing for project.

46. 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 Documentthere will be URL path of the website link from from that we will receivethe build In case of web server projects, you will be provided with an URL or a 92.168.***.*** (Webaddress) 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.

47. 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, analysethe results report the bugs. invovled in regression testing, performance of systemtesting system intergration testing At last preparation of Test summary Report

48. Contents of test report ?

There are two documents,which should be prepared at particular phase. 1.Test Results document.

2.Test Report document. Test Results doc will be prepared at the phase of each type of Testing like FULL FUNCTIONAL TESTPASS, REGRESSION TEST PASS,SANITY TEST PASS etc. Test case execution against the application.Once you prepared this doc, we will send the doc to our TL and PM. By seeing the Test Results doc ,TLwill come to know the coverage part of the test case.Here Iam 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,% oftestcases failed)

Coming to Test report,generally we will prepare Test report ,once we rolled out the product to ourclient.This document will be prepared by TL and delivered to the client.Mainly,this document describesthe 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 andwe will summerize the all the activities,which have taken place in through out the project.Here I amgiving your the contents covered in the Test Report. 1.Test Environment(Should be covered the OS,Application or webservers,Mahchinenames,Database,etc...) 2.Test Methods(Types of Tests,we have done in the project like Functional Testing,PlatformTesting,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.

49. Write high level test cases ? Write all the test cases under high level TC ,which can be covered the main functionalities like

Creation ,edition, deletion, etc....as per prescribed in the screen. Write all the test cases under lowlevel TC, which can be covered the screen, like input fields are displayed as per the requirements,buttons are enabled or disabled, and test case for low priority functionalities. Example a screen contains two edit boxes login and password and a pust buttons OK and Reset andcheck box for the label "Remember my password" .Now let us write high level TCand 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 test cases under HIGH LEVEL and LOW LEVEL.

50. What is test scenario ? Test scenario will be framed on basis of the requirement, which need to be checked. For that, we willframe set of test cases ,in other terms, we can say all the conditions, which can be determined thetesting coverage against business requirement. Please see the below example,which is exactlymatched to my explanation. As we know all most all the application are having login screen, which contains login name andpassword. 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........................................

51. What is build duration ? It is a time gap between old version build and new version build in new version build some new extrafeatures are added

52. What is test deliverables ?

Test deliverables are nothing but documents preparing after testing like test plan document test casetemplate bug report template Test deliverables will be delivered to the client not only for thecompleted activities ,but also for the activites, which we are implementing for the betterproductivity.(As per the company's standards).Here I am giving you some of the Test deliverables inmy 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 Schedule 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.

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

just audians.

54. 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 arealways 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

55. 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 particularmodule which implements the requiremnts) will also change. Hence the test plan would also need tobe updated. This is because "REsource Allocation" is one section in the testplan. 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

56. Explain VSS ? Virtual Sourse Safe... After complition of all phages From development side developer store the code in development folderof VSS. Testing team copy code from that folder to testing folder, after completing above phases fromtesting, testers put the build in base line folder. It is version control Tool Mainly useful to developer, to storing code and maintains version Copying a code from VSS Bydevoloper is called CHECK-IN Upload the code in to VSS is called CHECK-OUT.



57. 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 thefunctionality. Priority means: is how soon it should get fixed i.e importance of the bug in terms of customer

58. 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 modulesare used. So stubs are small dummy modules that test the core module.

Driver testing: In bottom up approach, small modules are developed. To test them a dummy core module calleddriver is developed.

59. What is a "Good Tester"?

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

Part – 4

What is the need for test planning

a. to utilize a balance of testing techniques

b. to

understand

testing

process

c. to collect metrics

d. to perform ad hoc testing.

Which of the following is NOT a part of Test plan document?

a. assumptions

b. communication

approach

c. risk analysis

d. status report

Which part of Test plan will define “what will and will not be covered in the test”?



a. test scope

b. test objective

c. both a & b

d. none

of

the

above

Test objective is simply a testing

a. direction

b. vision

c. mission

d. goal

Which out of the below is NOT a concern for testers to complete a test plan ?

a. not enough training

b. lack of test tools

c. enough time for testing

d. rapid

change

The effort taken to create a test plan should be

a. half of the total test effort

b. one‐third of the total test efforts

c. two times of the total test effort

d. one

‐fifth

of

the

total

test

effort

What do you mean by “Having to say NO”

a. No, the problem is not with testers



b. No, the software is not ready for production

c. Both a & b

d. none of the above

Tools like change Man, Clear case are used as

a. functional automation tools

b. performance testing tools

c. configuration management tools

d. none of the above.

Which is not the Phase of SDLC?

a. Initiation Phase

b. Definition Phase

c. Planning Phase

d. Programming and Training Phase

Comparison of the expected benefit versus the cost of the solution is done in which phase of SDLC

a) Definition Phase

b) Design Phase

c) Initiation Phase

d) Implementation Phase

Who is policy/oversight participant in SDLC?

a. Project Manager

b. Contracting Officer

c. Information Technology Manger

d. Information Resources Management official



Who reviews proposed procurement for sufficiency in the acquisition and installation of the Off ‐the‐

Self Software?

a. Sponsor / User

b. Project Manager

c. IT Manger

d. All of the Above

“V” testing process is

a. System development process and system test process begins

b. Testing starts after coding is done

c. Do procedures are followed by Check procedures

d. Testing starts after the prototype is done

Validation is

a.

Execute

test

b. Review code

c. Desk check

d.

Audit

Which is not in sequence in 11 Step Software Testing process

a. Assess development plan and status

b. Develop the test plan

c. Test software design

d. Test software

requirement

Structural testing is

a. Requirements are properly satisfied by the application



b. Uncover errors during “Coding” of the program

c. Functions works properly

d. To test how the business requirements are implemented.

Functional testing is

a. Path testing

b. Technology has been used properly

c. Uncover errors that occurs in implementing requirements.

d. Uncover errors in program unit.

Structural testing is NOT

a. Installation testing

b. Stress testing

c. Recovery testing

d. Compliance testing

Stress testing transaction can be obtained from

a. Test data generators

b. Test transactions created by the test group

c. Transactions previously processed in the production environment

d. All of the above.

Who will assess vulnerability in the system

a. Internal Control Officer

b. System Security Officer



c. QA Engineer

d. Test Manager

What is

the

structure

testing

process

a. Parallel

b. Regression

c. Stress

d. Intersystem

Acceptance requirements

that

a system

should

meet

is

a. Usability

b. Understandability

c. Functionality

d. Enhancements

Testing techniques

that

can

be

used

in

acceptance

testing

are

a. Structural

b. Functional

c. Usability

d. A and B

e. B and C

For final software acceptance testing, the system should include

a. Delivered software

b. All user documents



c. Final version of other software deliverables

d. All of the above

Acceptance testing

means

a. Testing performed on a single stand – alone module or unit of code

b. Testing after changes have been made to ensure that no unwanted changes were introduced

c. Testing to ensure that the system meets the needs of the organization and end user.

d. Users test the application in the developers environment

Acceptance tests

are

normally

conducted

by

the

a. Developer

b. End users

c. Test team

d. Systems engineers

Which is

not

test

result

data

a. Test factors

b. Interface objective

c. Platform

d. Test estimation

What type

of

test

that

will

be

conducted

during

the

execution

of

tests,

which

will

be

based

on

software requirements. What category of status data I am looking?

a. Test Result

b. Test Transaction

c. Defects



d. Efficiency

Summary (project)status report provides

a. General

view

of

a project

b. General view of all the projects

c. Detailed view of all the projects

d. Detailed information about a project

Project status report provides

a. General

view

of

a project

b. General view of all the projects

c. Detailed view of all the projects

d. Detailed information about a project

What is not the primary data given by the tester in test execution

a. Total

number

of

tests

b. Number of test cases written for change request

c. Number of test executed to date

d. Number of tests executed successfully to date

Do the current project results meet the performance requirements? Which section of Project Status

Report I should look for

a. Vital Project Information

b. General Project Information

c. Project Activities Information

d. Essential Elements Information



Which is a section of Summary status report

a. Vital project information

b. Essential

elements

information

c. Project activities information

d. Time Line information

Test Result data is

a. Test Transactions

b. Test

events

c. Business Objectives

d. Reviews

What type of efficiency can be evaluated during testing?

a. Software system

b. Testing

c. Development

d. A and C

e. A and B

What is the purpose of code coverage tools?

a. They are used to show the extent to which the logic in the program was executed during testing.

b. They

are

used

as

an

alternative

to

testing

c. They are used to compile the program

Four examples of test specific metrics.



a. Testing Effort variation, Defect Density, Testing Efficiency, Requirements tested.

b. Inspection, review efficiency, Testing Effort variation, Defect Density

c. Test scalability, Defect deviation, Testing Efficiency, Schedule variation

Give one

commonly

recognized

size

measurement

tool.

a. Effort analysis

b. LCO Analysis

c. LOC Analysis

d. Code Analysis

Give three components included in a system test report.

a.

Description

of

Testing;

resource

requirement;

and

Recommendation

b. Testing requirements; defects; and usability

c. Description of test results and findings (defects); Summary (environment and references); and

Recommendation

Non Statistical tools are used in the

a. Work Practice process

b.

Benchmarking

process

c. Both A and B

d. None of the above

Quality Function deployment (QFD) is a

a. Statistical tool

b. Non statistical tool

c. Development tool

d. None of the above

The Sequence of the four Phases involved in Bench marking process is

a. Action, Planning, Integration, Analysis



b. Planning, Analysis, Integration, Action

c. Analysis, Planning, Integration, Action

d. Analysis, Action, Planning, Integration

Defect Density is calculated by

a. Total no. of Defects/ Effort

b. Valid Defects/ Total no. of Defect

c. Invalid Defects/ Valid Defects

d. Valid Defects/ Effort

Effort Variation is calculated by

a. (Planned – Actual)/ Actual

b. (Actual – Planned) / Actual

c. (Actual – Planned) / Planned

d. (Planned – Actual)/ Planned

Percentage Rework is calculated by

a. (Review effort + rework effort)/ Actual Effort expended

b. (Review effort ‐ rework effort)/ Actual Effort expended

c. Rework Effort / Planned Effort

d. Rework Effort / Actual Effort expended

A quantitative measurement used to determine the test completion is

a. Defect measurement

b. Requirements coverage



c. Statistical Analysis

The

categories

of

Error

Oriented

Techniques

are

a) Statistical assessment and Error‐based testing

b) Error‐based testing and Fault based testing.

c) Fault based testing and Statistical assessment

d) Statistical assessment, Error‐based testing and Fault based testing.

The

following

factors

should

be

considered

for

the

Test

Tool

selection

1. Test Phase

2. Test Objective

3. Test Technique

4. Test Deliverable

Equivalence

partitioning

consists

of

various

activities:

a). Ensure that test cases test each input and output equivalence class at least once

b). Identify all inputs and all outputs

c). Identify equivalence classes for each input

d). All of the above

It’s

an

unfair

test

to

perform

stress

testing

at

the

same

time

you

perform

load

testing

a) True

b) False

Verification activities during design stages are



a) Reviewing and Inspecting

b) Inspecting and Testing

c) Reviewing and Testing

d) Reviewing, Inspecting

and

Testing.

Testing, which is carried out using no recognized test case design

a) Failure Testing

b) Adhoc Testing

c) Exhaustive Testing

d) Empty test

case

Testing

A test case design technique for a component in which test cases are designed to execute statements

is called as ?

a) State transition Testing

b) Static Testing

c) Transition testing

d) Statement testing

part – 5

Application developed should fit user’s business process. The components of fit are

a. Data

b. People

c. Structure

d. All of the above

Which is not the responsibility of customer/ user of the software

a. Plan how and by whom each acceptance activity will be performed b. Prepare the acceptance plan

c. Prepare resource plan d. Plan resources for providing information on which to base acceptance decisions



In preparation for developing the acceptance criteria, the user should

a. Know the defects in the application b. Acquire the basic knowledge of the application for which the system is intended

c. Understand the risks and benefits of the development methodology that is to be used in

correcting the software system

d. Know new enhancement and basic understanding of how the application is implemented inusers organization

QC isa) Phase building activity

b) Intermediate activity

c) End of Phase activity d) Design activity

The ______________ is an application of process management and quality improvement

concepts to software development and maintenance.

a.

Malcolm Baldridge b. ISO 9000

c. SEI/CMM

d. QS14000

Which is a true prevention mechanism

a. verifying that the executable contains a defect b. detecting that the executable contains a defect c. Validating that the specified requirements are right, complete, achievable,

reasonable, testable d. Verifying that the specified requirements are right, complete, achievable,

reasonable, testable

Objective of review meeting is

a. to identify problems with design b. to solve the problems with design c. both a and b d. none of the above.

What are the Performance Testing Concepts ?

Load Testing Tools

a. reduces the time spent by the testers b. reduces the resources spent (hardware) c. mostly used in web testing



d. all of the above

Identify which one is a load condition

a. Lost messages b. Task starts before its prerequisites are met. c.

Lost or out of sync messages d. Early end of string

State which of the one is false a. In performance testing, usage of tool is a mustb. In database testing, database knowledge is a must. c. In Functional Testing, knowledge of business logic is a must d. none of the above.

Load testing emphasizes on performance under load while stress testing emphasizes on

a. Breaking load

b. Performance under stressc. Performance under load

d. There is no such difference, both are same

Which of the following is not a form of performance testing? a. Spike testing b. Volume testing

c. Transaction testing d. Endurance testing

Which of the following is not a client side statistics in load testing

a. Hits per second b. Throughput

c. Cache hit ratio d. Transaction per second

Feasibility study is more important before load testing

a. Web Applications b. Client-server applications

c. Mainframe applications

d. Citrix applications

Basic Automation Concept :

Tools usage

a. very helpful in regression testing b. saves time c. helpful in simulating Users d. all of the above.



The following five tasks are needed to develop, use and maintain Test scripts.

1) Unit scripting 2) Pseudoconcurrency scripting

3) Integration scripting

4) Regression Scripting

5) Stress/Performance Scripting.

What is the scenario in which automation testing can be done:

1) Application is stable 2) Usability testing is to be done

3) The project is short term

4) Long term project having numerous releases

What is the common limitation of automated testing?

a. They are not useful for performance testing

b.

They cannot be used for requirement validationc. It is very difficult for automated scripts to verify a wide range of application

responses.

d. They are not useful when requirements are changing frequently

The extent of automation for a given project is generally guided by

e. Scope for automation f. Tool support

g. Business Functionality

h. Vendor’s skills

What are the main attributes of test automation

1. Time saving

2. Correctness 3. Less Manpower

4. More reliable

Some of the common problems of test automation are

i. Changing requirements j. Lack of time

k. Both a and b

l.

None of the above



Part – 6

Software Testing Interview Questions

Software Testing Basics

In which Software Life cycle phase does testing occur?

Can you explain PDCA cycle and where does testing fit?

What is the difference between white box, black box and gray box testing?

Define Defect?

What is the difference between Defect and Failure?

What are the broader categories of defects?

What is the difference between Verification and Validation?

How does testing affect risk?

Does Increase in testing always mean good to the project?

As a manager what process did you adopt to define testing policy? Should testing be only after build and execution?

Are number of defects more in design phase or coding phase?

What kind of inputs do we need from the end user to start proper testing?

What is the difference between Latent and Masked Defect?

A defect which could have been removed during initial stage is removed in laterstage how does it affect cost?

In testing can you explain the concept of work bench?

What's the difference between Alpha and Beta testing?

Can you explain the concept of defect cascading?

Can you explain how one defect leads to other defects?

Can you explain what is Usability testing?

What are the different strategies of rollout to the end users?

Can you explain requirement traceability and its importance?

What is the difference between Pilot and Beta testing?

How will you do a risk analysis during software testing?

How do you conclude which section is most risky in your application?

What does entry and exit criteria mean in a project?

On what basis is the Acceptance plan prepared?

What's the relation between environment reality and test phases?

What are different types of verifications?

What's the difference between Inspections and Walkthroughs? Can you explain regression testing and confirmation testing?

What do you mean by coverage and what are the different types of coveragetechniques?

How does fundamentally a coverage tool work?

What is configuration management?

Can you explain the concept of baseline in software development?



What are the different test plan documents in project?

How do test documents in a project span across software development life cycle?

Can you explain inventories?

How do you do Analysis and design for testing projects?

Can you explain calibration?

Which test cases are first written white boxes or black box? Can you explain Co-habiting software?

What different impact rating's you have used in your project?

Can you explain what a test log is?

Explain SDLC (Software development Life Cycle) in detail?

Can you explain waterfall model?

Can you explain big-bang waterfall model?

Can you explain phased waterfall model?

Explain Iterative model, Incremental model, Spiral model, Evolutionary model

and V-Model?

Explain Unit testing, Integration tests, System testing and Acceptance testing? What's the difference between system and acceptance testing?

Which is the best model?

What group of teams can do software testing?

Testing techniques

Can you explain boundary value analysis?

What is BV in software testing?

Can you explain Equivalence partitioning?

Can you explain how state transition diagram can be helpful during testing?

Can you explain random testing?

Can you explain monkey testing?

What is negative and positive testing?

Can you explain exploratory testing?

What exactly are semi-random test cases?

Can you explain the concept of orthogonal array?

Can you explain pair-wise defect fundamental?

Can you explain the concept of decision tables?

How did you define severity ratings in your project?

Software process

What is a Software process?

What are the different cost element involved in implementing process in an

organization?

What is a model?

What is maturity level?



Can you explain the concept of process area in CMMI?

Can you explain the concept of tailoring?

CMMI

What is CMMI and what's the advantage of implementing CMMI in anorganization?

What's the difference between implementation and Institutionalization?

What are different models in CMMI?

Can you explain staged and continuous models in CMMI?

Can you explain the different maturity levels in staged representation?

Can you explain capability levels in continuous representation?

Which model should we use and under what scenarios?

How many process areas are present in CMMI and in what classification do theyfall in?

What the difference between every level in CMMI? What different sources are needed to verify authenticity for CMMI

implementation?

Can you explain SCAMPI process?

How is appraisal done in CMMI?

Which appraisal method class is the best?

Can you explain the importance of PII in SCAMPI?

Can you explain implementation of CMMI in one of the Key process areas?

Explanation of all process areas with goals and practices?

Can you explain the process areas?

Six Sigma

What is six sigma?

Can you explain the different methodology for execution and design process inSIX sigma?

What does executive leaders, champions, Master Black belt, green belts and black belts mean?

What are the different kinds of variations used in six sigma?

Can you explain the concept of standard deviation?

Can you explain the concept of fish bone/ Ishikawa diagram?

Can you explain QFD? Can you explain FMEA?

Can you explain X bar charts?

Can you explain Flow charting and brain storming?

Metrics



What is meant by measure and metrics?

Can you explain Number of defects measure?

Can you explain number of production defects measure?

Can you explain defect seeding?

Can you explain DRE?

Can you explain Unit and system test DRE? How do you measure test effectiveness?

Can you explain Defect age and Defect spoilage?

Automated Testing

What are good candidate for automation in testing?

Does automation replace manual testing?

Which automation tool have you worked and can you explain them in brief?

Can you explain how does load testing conceptually work for websites?

Can you explain how did you perform load testing using tool? What does load test summary report contain?

Can you explain the concept of data-driven testing?

Can you explain table-driven testing?

How can you perform data-driven testing using Automated QA?

Testing Estimation

What are the different ways of doing black box testing?

Can you explain TPA analysis?

Can you explain in brief Function points?

Can you explain the concept Application boundary?

Can you explain the concept of elementary process?

Can you explain the concept of static and dynamic elementary process?

Can you explain concept of FTR, ILF, EIF, EI, EO, EQ and GSC?

How can you estimate number of acceptance test cases in a project?

Can you explain on what basis does TPA actually work?

How did you do estimation for black box testing?

How did you estimate white box testing?

Is there a way to estimate acceptance test cases in a system?