MANUAL TESTING QUESTIONS & ANSWERS

1. What is meant by Priority an se!erity" Severity: 1. This is assigned by the Test Engineer 2. This is to say how badly the deviation that is occurring is affecting the other modules of the build or release. Priority: 1. This is assigned by the Developer. 2. This is to say how soon the bug as to be fi ed in the main code! so that it pass the basic re"uirement. Egg. The code is to generate some values with some valid input conditions. The priority will be assigned so based on the following conditions: a# $t is not accepting any value b# $t is accepting value but output is in non%defined format &say 'nicode (haracters). * good e ample $ used some 'nicode characters to generate a left defined arrow! it displayed correctly but after saving changes it gave some address value from the Stac+ of this server. ,or more information mail me $ will let you +now. #. Gi!e me some e$am%&e 'or hi(h se!erity an &o) %riority e'e*t" $f suppose the title of the particular concern is not spelled correctly! it would give a negative impacted $($(( is spelled as a title for the pro-ect of the concern $($($. Then it is a high severity! low priority defect. +. What is basis 'or test *ase re!ie)" The main basis for the test case review is 1. Testing techni"ues oriented review 2. .e"uirements oriented review /. Defects oriented review. ,. What are the *ontents o' SRS o*-ments" Software re"uirements specifications and ,unctional re"uirements specifications. .. What is i''eren*e bet)een the Web a%%&i*ation testin( an /&ient Ser!er testin(" Testing the application in intranet &without browser) is an e ample for client %server. &The company firewalls for the server are not open to outside world. 0utside people cannot access the application.)So there will be limited number of people using that application. Testing an application in internet &using browser) is called web testing. The application which is accessible by numerous numbers around the world &1orld

1ide 1eb.) So testing web application! apart from the above said two testing there are many other testing to be done depending on the type of web application we are testing. $f it is a secured application &li+e ban+ing site% we go for security testing etc.) $f it is an e%commerce testing application we go for 'sability etc2 Testing. 0. E$%&ain yo-r )eb a%%&i*ation ar*hite*t-re" 1eb application is tested in / phases 1. 1eb tier testing 3# browser compatibility 2. 4iddle tier testing 3# functionality! security /. Data base tier testing 3# database integrity! contents 1.s-%%ose the %ro -*t2a%%&i*ation has to e&i!er to *&ient at ..33PM4At that time yo- or yo-r team member *a-(ht a hi(h se!erity e'e*t at +PM. 5Remember e'e*t is hi(h se!erity67-t the *&ient is *annot )ait 'or &on( time. 8o- sho-& e&i!er the %ro -*t at ..33Pm e$a*t&y. Then )hat is the %ro*e -re yo- 'o&&o)" The bug is high severity only so we send the application to the client and find out the severity is priority or not. $f its priority then we as+ him to wait. 5ere we found defects6bugs in the last minute of the delivery or release date Then we have two options 1. E plain the situation to client and as+ some more time to fi the bug. 2. $f the client is not ready to give some time then analy7e the impact of defect6bug and try to find wor+arounds for the defect and mention these issues in the release notes as +nown issues or +nown limitations or +nown bugs. 5ere the wor+around means remedy process to be followed to overcome the defect effect. /. 8ormally this +nown issues or +nown limitations &defects) will be fi ed in ne t version or ne t release of the software 9. Gi!e me e$am%&es 'or hi(h %riority an &o) se!erity e'e*ts" Suppose in one ban+ing application there is one module *T4 ,acility. $n that *T4 facility when ever we are depositing6withdrawing money it is not showing any conformation message but actually at the bac+ end it is happening properly with out any mista+e means only missing 0f message. $n this case as it is happening properly so there is nothing wrong with the application but as end user is not getting any conformation message so he6she will be (onfuse for this. So we can consider this issue as 5$95 Priority but :01 Severity defects2 :. E$%&ain abo-t 7-( &i'e *y*&e" 1) Tester%# 2) 0pen defect%# /) Send to developer

;) %#if accepted moves to step< else sends the bug to tester gain <) ,i ed by developer %# =) .egression testing%# >) 8o problem inbuilt and sign off %#if problem in built reopen the issue send to step/ 13. ;o) *an yo- re%ort the e'e*t -sin( e$*e& sheet" To report the defect using e cel sheet 4ention: The ,uture that been effected. 4ention: Test (ase $D &1hich fail you can even mention any other which are dependency on this bug) 4ention : *ctual ?ehavior 4ention : E pected ?ehavior as mentioned in Test (ase or E,S or E?S or S.S document with section 4ention : @our Test Setup used during Testing 4ention : Steps to .e%Produce the bug 4ention : *dditional $nfo 4ention : *ttach a Screen Shot if it is a 9'$ bug 4ention : 1hich other features it is bloc+ing because of this bug that you are unable to E ecute the test cases. 4ention: 5ow much time you too+ to e ecute that test case or follow that specific T( 1hich leaded to bugA 11.I' yo- ha!e e$e*-te 133 test *ases 4e!ery test *ase %asse b-t a%art 'rom these test *ase yo- 'o-n some e'e*t 'or )hi*h test *ase is not %re%are 4th)n ho) yo- *an re%ort the b-(" 1hile reporting this bug into bug trac+ing tool you will generate the test case mean put the steps to reproduce the bug. 1#. What is the i''eren*e bet)een )eb base a%%&i*ation an *&ient ser!er a%%&i*ation" The basic difference between web based application B client server application is that the web application are / tier B client based are 2 trier.$n web based changes are made at one place B it is reflected on other layers also whereas client based separate changes need be installed on client machine also. 1+. What is test %&an" An *an yo- te&& the test %&an *ontents" Test plan is a high level document which e plains the test strategy! time lines and available resources in detail. Typically a test plan contains: %0b-ective %Test strategy %.esources %Entry criteria %E it criteria

%'se cases6Test cases %Tas+s %,eatures to be tested and not tested %.is+s6*ssumptions. 1,. ;o) many test *ases *an yo- )rite %er a ay4 an a!era(e 'i(-re" (omple test cases ;%> per day 4edium test cases 1C%1< per day 8ormal test cases 2C%/C per day 1.. Who )i&& %re%are <RS 5'-n*tiona& re=-irement o*-ments6" What is the im%ortant o' <RS" The ?usiness *nalyst will pre pare the ,.S. ?ased on this we are going to prepare test cases. $t contains 1. 0ver view of the pro-ect 2. Page elements of the *pplication &,iled 8ames) /. Prototype of the of the application ;. ?usiness rules and Error States <. Data ,low diagrams =. 'se cases contains *ctor and *ctions and System .esponses 10. ;o) yo- *an e*i e the n-mber o' test *ases is eno-(h 'or testin( the (i!en mo -&e" The developed test cases are covered all the functionality of the application we can say test cases are enough. $f u +nows the functionality covered or not u can use .T4. 11. What is the i''eren*e bet)een Retestin( an >ata >ri!en Testin(" .etesting: it is manual process in which application will be tested with entire new set of data. Data Driven Testing&DDT)%$t is a *utomated testing process in which application is tested with multiple test dated is very easy procedure than retesting because the tester should sit and need to give different new inputs manually from front end and it is very tedious and boring Procedure. 19. What is re(ression testin(" *fter the ?ug fi ed! testing the application whether the fi ed bug is affecting remaining functionality of the application or not. 4a-orly in regression testing ?ug fi ed module and itDs (onnected modules are chec+ed for their integrity after bug fi ation.

1:. ;o) oes - test )eb a%%&i*ation" 1eb application testing 1eb application should have the following features li+e 1. *ttractive 'ser $nterface &logos! fonts! alignment) 2. 5igh 'sability options /. Security features &if it has login feature) ;. Database &bac+ end). <. Performance &appearing speed of the application on client system) =. *ble to wor+ on different ?rowsers &?rowser compatibility)! 0.S compatibility &technically called as portability) >. ?ro+en lin+ testing222etc so we need to follow out the following test strategy. 1. ,unctionality Testing 2. Performance Testing &:oad! volume! Stress! Scalability) /. 'sability Testing ;. 'ser $nterface Testing &colors! fonts! alignments2) <. Security Testing =. ?rowser compatibility Testing &different versions and different browser) >. ?ro+en lin+ and 8avigation Testing E. Database &bac+ end) Testing &data integrity) F. Portability testing &4ulti 0.s Support)2.etc #3. ;o) oes - %er'orm re(ression testin(4 means )hat test *ases - se&e*t 'or re(ression" .egression testing will be conducted after any bug fi ed or any functionality changed. During defect fi ing procedure some part of coding may be changed or functionality may be manipulated. $n this case the old test cases will be updated or completely re written *ccording to new features of the application where bug fi ed area. 5ere possible areas are old test cases will be e ecuted as usual or some new test cases will be added to e isting test cases or some test cases may be deleted. #1. What r the *&ient si e s*ri%tin( &an(-a(es an ser!er si e s*ri%tin( &an(-a(es" (lient side scripting languages are Gavascript! HbScript! P5P2etc Server side Scripting languages are Perl! GSP! *SP! P5P.etc (lient side scripting languages are useful to validate the inputs or user actions from user side or client side. Server side Scripting languages are to validate the inputs at server side. These scripting languages provide security for the application. *nd also provides

dynamic nature to web or client server application (lient side scripting is good because it wonDt send the unwanted inputDs to server for validation. ,rom front%end it self it validated the user inputs and restricts the user activities and guides him ##. I' a !ery &o) e'e*t 5-ser inter'a*e6 is ete*te by - an the e!e&o%er not *om%romisin( )ith that e'e*t4)hat )i&& - o" 'ser interface defect is a high visibility defect and easy to reproduce. ,ollow the below procedure 1. .eproduce the defect 2. (apture the defect screen shots /. Document the proper inputs that you are used to get the defect in the defect report /. Send the defect report with screen shots! i6ps and procedure for defect reproduction. ?efore going to this you must chec+ your computer hard ware configuration that is same as developer system configuration. *nd also chec+ the system graphic drivers are properly $nstalled or not. $f the problem in graphic drivers the 'ser interfaces error will come. So first chec+ your side if it is correct from your side then reports the defect by following the above method. #+.i' - r on&y %erson in the o''i*e an *&ient as?e - 'or some *han(es an - i n@t (et )hat the *&ient as?e 'or )hat )i&& - o" 0ne thing here is very important. 8obody will as+ test engineer to change software that is not your duty! even if it is related to testing and anybody is not there try to listen care fully if you are not understand as+ him again and inform to the corresponding people immediately. 5ere the client need speedy service! we &our company) should not get any blame from customer side. #,. ;o) to (et to% t)o sa&aries 'rom em%&oyee tab&es" Select I from E4P e where 2#J &select count &I) from E4P e where sal#e.sal) order by desc sal. #.. ;o) many TestA/ases *an be )ritten 'or the *a&*-&ator ha!in( 3A: b-ttons4 A 4 E=-a&to b-ttons" The test *ases sho-& be 'o*-se on&y on a A'-n*tiona&ity b-t mot GUI.What is those testA*ases" Test%(ases for the calculator so here we have 12 buttons totali7e C!1!2!/!;!<!=!>!E!F!*DD!E"ualto %12 buttons here u can press at least ; buttons at a time minimum for e ample CK1J for 7ero u should press L7eroD labeled button for plus u should press LKD labeled button for one u should press LoneD labeled button for e"ual to u should press Le"ual toD labeled button CK1Jhere K and J positions will not vary so first number position

can be varied from C to F i.e. from permutation and combinations u can fill that space in 1C ways in the same way second number position can be varied from C to F i.e. from permutation and combinations u can fill that space in 1C ways Total number of possibilities are J1CM1CJ1CC This is e haustive testing methodology and this is not possible in all cases. $n mathematics we have one policy that the function satisfies the starting and ending values of a range then it can satisfy for entire range of values from starting to ending. then we chec+ the starting conditions i.e. one test case for LCKCJD &e pected values you +now thatDs LC) then another test case for LFKFJD&e pected values you +now thatDs L1E) only two test cases are enough to test the calculator functionality. #0. What is %ositi!e an ne(ati!e testin(.E$%&ain )ith e$am%&e" Positive Testing % testing the system by giving the valid data. 8egative Testing % testing the system by giving the $nvalid data. ,or E am application contains a te tbo and as per the userDs .e"uirements the te tbo should accept only Strings. ?y providing only String as input data to the te tbo B to chec+ whether its wor+ing properly or not means it is Positive Testing. $f giving the input other than String means it is negative Testing. #1. ;o) )i&& yo- %re%are Test %&an. What are the te*hni=-es in!o&!e in %re%arin( the Test %&an" Test plan means planning for the release. This includes Pro-ect bac+ground Test 0b-ectives: ?rief overview and description of the document Test Scope: setting the boundaries ,eatures being tested &,unctionalities) 5ardware re"uirements Software re"uirements Entrance (riteria &1hen to start testing): Test environment established! ?uilder received from developer! Test case prepared and reviewed. E it criteria &when to stop testing): *ll bug status cycle are closed! all functionalities are tested! and all high and medium bugs are resolved. Pro-ect milestones: dead lines #9. What is the >e'e*t Li'e /y*&e" Defect life cycle is also called as bug life cycle. $t has =stages namely 1. 8ew: found new bug 2. *ssigned: bud assigned to developer /. 0pen: developer is fi ing the bug ;. ,i ed: developer has fi ed the bug <. .etest: tester retests the application =. closed6reopened: if it is o+ tester gives closed statuselse he reopens and sends bac+ to developer.

#:. E$%a&in abo-t metri*s Mana(ement" 4etrics: is nothing but a measurement analysis.4easurment analysis and $mprovement is one of the process area in (44 $ :2. +3. What is %er'orman*e Testin( an Re(ression Testin(" Performance Testing:%testing the present wor+ing condition of the product .egression Testing:%.egression Testing is chec+ing for the newly added functionality causing any errors interims of functionality and the common functionality should be stable $n the latest and the previous versions +1.;o) o yo- re!ie) test *ase" Ty%e o' Re!ie)B Types of reviewing test cases depend upon company standards! vi7..! Peer review! team lead review! pro-ect manager review. Some times client may also review the test cases reg what is approach following for pro-ect +#. In )hi*h )ay tester (et 7-i& A4 7-i& 74 7-i& C o' an a%%&i*ation4 D-st e$%&ains the %ro*ess" *fter preparation of test cases pro-ect manager will release software release note in that Document there will be '.: path of the website lin+ from that we will receive The build $n case of web server pro-ects! you will be provided with an '.: or a F2.1=E. III. III &1eb address) which will help you access the pro-ect using a browser from your system. $n case of (lient server! the build is placed in the HSS &(onfiguration tool) which will help you get the .e e downloaded to your computer. ++. A%art 'rom b-( re%ortin( )hat is yo-r in!o&!ement in %roDe*t &i'e *y*&e" *s a Test engineer we design test cases! prepare test cases E ecute Test cases! trac+ the bugs! analy7e the results report the bugs. $nvolved in regression testing! performance of system Testing system integration testing at last preparation of Test summary .eport +,.What are the *ontents o' test re%ort" There are two documents! which should be prepared at particular phase. 1. Test .esults document. 2. Test .eport document. Test .esults doc will be prepared at the phase of each type of Testing li+e ,':: ,'8(T$08*: TEST P*SS!.E9.ESS$08 TEST P*SS!S*8$T@ TEST P*SS etc2Test case e ecution against The application. 0nce you prepared this doc! we will send the doc to our T: and P4.?y seeing the Test .esults doc! T: will come to +now the coverage part of the testcase.5ere $ am giving you the contents used in the Test .esults docA

1. ?uild 8o 2. Hersion 8ame /. (lient 0S ;. ,eature set <. 4ain ,eature =. Defined Test cases on each feature. >. N* engineer 8ame E. Test e%cases e ecuted. &$ncludes pass and fail) F. Testcases on 50:D &$ncludes bloc+ing test cases and deferred Test cases) 1C. (overeage .eport &1hich includes the coverage ratings in O! li+e O of test cases covered! O of test cases failed) (oming to Test report! generally we will prepare Test report! once we rolled out the product to our client. This document will be prepared by T: and delivered to the client.4ainly! this document describes the what we have done in the pro-ect! chievements we have reached! our :earningDs in throughout the pro-ect etc2The other name for Test report is Pro-ect (losure .eport and we will summari7e the all the activities! which have ta+en place in through out the pro-ect. 5ere $ am giving your the contents covered in the Test .eport. 1. Test Environment &Should be covered the 0S! *pplication or webservers! 4ahchine names! Database! etc2) 2.Test 4ethods&Types of Tests! we have done in the pro-ect li+e ,unctional Testing! Platform Testing! regression Testing!etc.. /. 4a-or areas (overed. ;. ?ug Trac+ing Details. &$ncludes inflow and outflow of the bus in our delivered pro-ect) <. 1or+ schedule &1hen we start the testing and we finished) =. Defect *nalysis =.1 Defects logged in different types of tests li+e ,unctional Test! regressiion Test as per area wised. =.2 State of the Defects at end of the Test cycle. =./ .oot cause analysis for the bugs mar+ed as 80T * ?'9. >. N* observations or learningDs thought the life cycle. +.. Write hi(h &e!e& test *ases" 1rite all the test cases under high level T(! which can be covered the main functionalities li+e (reation! edition! deletion! etc2.as per prescribed in the screen. 1rite all the test cases under low level T(!which can be covered the screen! li+e input fields are displayed as per the re"uirements! buttons are enabled or disabled! and test case for low priority functionalities. E ample a screen contains two edit bo es login and password and a put buttons 0P and .eset and chec+ bo for the label Q.emember my passwordR. 8ow let us write high level T( *nd low level test cases.

5$95 :EHE: T( 1. Herify that 'ser is able to login with valid login and valid password. 2. Herify that 'ser is not able to login with invalid login and valid password. Etc2 .. /. Herify that .eset button clears the filled screen. ;. Herify that a pop up message is displayed for blan+ login. Etc2 Etc. :01 :EHE: T( 1. Herify that after launching the '.: of the application below fields are displays in the screen. 1. :ogin 8ame 2.Password./.0P ?'TT08 ;..ESET button etc. <. (hec+ bo ! provided for the label Qremember my pwdR is unchec+ed. 2. Herify that 0P button should be disabled before selecting login and password fields. /. Herify that 0P button should we enabled after selecting login and password. ;. Herify that 'ser is able to chec+ the chec+ bo ! providedfor the label Qremember my passwordR. Etc. $n this way! we can categories all the test cases under 5$95 :EHE: and :01 :EHE:. +0. What is test s*enario" Test scenario will be framed on basis of the re"uirement! which need to be chec+ed. ,or that! we will frame set of test cases! in other terms! we can say all the conditions! which can be determined the testing coverage against business re"uirement. Please see the below e ample! which is e actly matched to my e planation. *s we +now all most all the application are having login screen! which contains login name and password. 5ere is the test scenario for login screen. Scenario: 'SE.DS :09$8 (onditions to be chec+ed to test the above scenario: SSSSSSSSSSSSSSSSS% 1. Test login field and Password fields individually. 2. Try to login with valid login and valid password. /. Try to login with invalid login and valid password. Etc +1. What is b-i& -ration" it is a tine gap between old version build and new version build in new version build some new e tra features are added +9. What is test e&i!erab&es" Test deliverables are nothing but documents preparing after testing li+e test plan document test case template bug report template Test deliverables will be

delivered to the client not only for the completed activities! but also for the activites! which we are implementing for the better productivity. &*s per the companyDs standards).5ere $ am giving you some of the Test deliverables in my pro-ect. 1. N* Test Plan 2. Test case Docs /. N* Test plan! if we are using *utomation. ;. *utomation scripts <. N* (overage 4atri and defect matri . =. Traceability 4atri >. Test .esults doc E. N* Schedule doc &describes the deadlines) F. Test .eport or Pro-ect (losure .eport. &Prepared once we rolled out the pro-ect to client) 1C. 1ee+ly status report &sent by P4 to the client) 11. .elease 8otes. +:. What is yo-r in!o&!ement in test %&an" Test lead is involved in preparing test plan test engineers are no way related in preparing test plan role TE is test case design! and e ecution and bug trac+ing and reporting them 9enerally T: is involved in preparation of the TestPlan.?ut it is not mandatory only T: will ta+e main part in the preparation of the TP.Test engineer can suggest to T:! if he &or) she has good understanding on pro-ect and resources! if he or she has more e p with the pro-ect! if T: is wrongly given deadlines. $f your suggestions are valid! T: will incorporate all of them to the TestPlan.?ut in most of the companies Test engineers are -ust audience. ,3. Whi*h test *ases are not to be a-tomate " *ll the test cases which are related to a feature of the product! that +eeps on changing &there are always some or the other enhancements in it). ,re"uent enhancements may change the '$! add6remove few controls. 5ence such cases! if automated! would involve lot of a intendance ,1. I' a %roDe*t is &on( term %roDe*t4 re=-irements are a&so *han(es then test %&an )i&& *han(e or not" Why" @es. Definitely. $f re"uirement changes! the design documents! specifications &for that particular module which implements the re"uirements) will also change. 5ence the test plan would also need to be updated. This is because Q.esource *llocationR is one section in the test Plan. 1e would need to write new test cases! review! and e ecute it. 5ence resource allocation would have to be done accordingly. *s a result the Test plan would change ,#. E$%&ain ESS 5Eirt-a& So-r*e Sa'e6" *fter completion of all phages from development side developer store the code in development folder of HSS! Testing team copying code from that folder to

testing folder! after completing above phages from testing! testers put the build in base line folder. $t is version control Tool 4ainly useful to developer! to storing code and maintains version (opying a code from HSS ?y developer is called (5E(P%$8 'pload the code in to HSS is called (5E(P%0'T. ,+. Who )i&& assi(n se!erity & %riority" The tester6developer should give the priority based on severity of the bug Severity means: is the impact of the bug on the application .i.e seriousness of the bug interims of the functionality. Priority means: is how soon it should get fi ed i.e. importance of the bug interims of customer ,,. What is the >i''eren*e bet)een St-b Testin( an >ri!er Testin(" Stub testing: $n top down approach! a core module is developed. To test that core module! small dummy modules r used. So stubs r small dummy modules that test the core module. Driver testing: $n bottom up approach! small modules r developed. To test them a dummy core module called driver is developed. ,.. What is a FGoo TesterG" $s one who tries to brea+ the developers software and in a position to venture the bugs. So that at least ECO bugs free software can deliver. ,0. What is *oo?ie An Session testin(" * small te t file of information that certain 1eb sites attach to a userDs hard drive while the user is browsing the 1eb site. * (oo+ie can contain information such as user $D! user preferences! archive shopping cart information! etc. (oo+ies can contain Personally $dentifiable $nformation. Session is a connection between a server and client. ,1. ;o) )o-& yo- %er'orman*e testin( man-a&&y 'or )eb site" ?y noting the time to load page or perform any action with stop watch. $ +now it sounds funny but this is the way performance is tested manually. ,9. What is -se *ase" Te&& me the attrib-te o' -se *ase" Q'se (ase is description of functionality certain features of an application interims of *ctors! actions and responsibilities.R 'se (ase attributes are: 1. $nformation of Document! 2. Description! /. 0b-ective! ;. *ctors! <.Pre% conditions! =.Data%element descriptions! >.post conditions! E.primary flow! F. *lternative flow and ?usiness rules6interaction implementations and etc2.

,:. What is the i''eren*e bet)een stress4 !o&-me an &oa testin(" :oad Testing gradually increase the load and chec+ the performance of the application .v chec+ at what point or ma imum load application can sustain. Stress testing: $n this testing v chec+ the performance of application under e treme condign which rarely occurs li+e &1)4any concurrent user access the application for short time. &2) E tra ordinary long transaction. &/) Hery short transaction reputed "uic+ly. .3. When )i&& o the beta test" When )i&& o the a&%ha test" *lpha and ?eta tests comes under 'ser acceptance test. 1e will conduct these two systems being released. 1e are giving opportunity to customer to chec+ all punctualities covered or not. *lpha testing conducting for software application by real customer at development site. ?eta testing conducting for software product by model customer at customer site. .#. ;o) o yo- se&e*t test *ases 'or Re(ression Testin( 5The %oint is )hen there is *han(e *o e ho) o yo- *ome to ?no) )hi*h %art o' *o e or mo -&es it )i&& a''e*t6" (onsider an e ample of a form which has a user name! password and :ogin button. There is a code change and a new button Q.esetR is introduced. .egression testing &for that build) will include testing only the Q:oginR button and not the .eset button &testing .eset button will be a part of conation testing). 5ence the .egression tester need not worry about the change in code! functionality. ?ut he has to ma+e sure that the e isting functionality is wor+ing as desired. Testing of Q.esetR button will be included as a part of .egression! for the ne t build .+. /an yo- e$%&ain )ith e$am%&e o' hi(h se!iority an &o) %riority4 &o) se!iority an hi(h %riority4 hi(h se!iority an hi(h %riority4 &o) se!iority an &o) %riority" 1. 5igh severity and high priority % Database connectivity cannot be established by multiple users. 2. :ow severity and low priority % Small issues li+e! incorrect number of decimal digits in the output. /. :ow severity and high priority % $mages not updated. ;. 5igh severity and low priority % $n a module of say 2 interfaces! the lin+ between them is bro+en or is not functioning. &1)5igh priority B 5igh Severity: $f u clic+s on e plorer icon or any other icon then system crash. &2) :ow priority B low severity: $n login window! spell of o+ button is QPoR. &/):ow priority B high serverty: $n login window! there is a restriction login name should be E characters if user enter F or than F in that case system get crash.

&;)5igh priority B low severity: Suppose logo of any brand company is not proper in their product. So it affects their business. .,. What )i&& be the Test *ase 'or ATM Ma*hine & /o''ee Ma*hine" Test cases for *T4 4achine 1. Successful inspection of *T4 card 2. 'n successful operation due to insert card in wrong angle /. 'n successful operation due to invalid account e : other ban+ card or time e pired card ;. Successful entry of P$8 number <. 'n successful operation due to enter wrong P$8 number /times =. Successful selection of language >. Successful selection of account type E. 'n successful operation due to invalid account type 1C. Successful selection of withdraw operation 11. Successful selection of amount to be withdraw 12. Successful withdraw operation 1/. 'nsuccessful withdraw operation due to wrong denominations 1;. 'nsuccessful withdraw operation due to amount is greater than day limit 1<. 'nsuccessful withdraw operation due to lac+ of money in *T4 1=. 'nsuccessful withdraw operation due to amount is greater than possible balance 1>. 'nsuccessful withdraw operation due to transactions is greater than day limit 1E. 'nsuccessful withdraw operation due to clic+ cancel after insert card 1F. 'nsuccessful withdraw operation due to clic+ cancel after insert card B pin number 2C. 'nsuccessful withdraw operation due to clic+ cancel after insert card! pin number B language 21. 'nsuccessful withdraw operation due to clic+ cancel after insert card! pin number! language Baccount type 22. 'nsuccessful withdraw operation due to clic+ cancel after insert card ! pin number ! language !account type B withdraw operation 2/.unsuccessful withdraw operation due to clic+ cancel after insert card ! pin number ! language !account type !withdraw operation Bamount to be withdraw ... Te&& me abo-t yo-r ai&y a*ti!ities as a test en(ineer" .ole: 1. 'nderstanding the ?.S and 'se cases Document 2. 9iving system demo to P4! System analyst! designer! Dev lead. /. Preparing the Test *ctions in ls sheet. ;. 'pdating the Test *ctions based on review comments by System analyst6?usiness *nalyst. <. Preparing the Test cases and Datasets &System level and global level datasets) in word document =. 'pdating the Test (ases based on review comments by System analyst. >. $nstalling the application%Testing environment set up.

E. Performing ,unctional! 9'$! System! (ompatibility testing &$f necessary)! .egression testing based on Test cases F. Preparing the defect report! ?ug trac+ing list and sending daily status report to P4! leads. .0. In S>L/ %ro*ess )hat is the ro&e o' PM4 TL4 >EEELOPER4 tester in ea*h an e!ery %hase" P&ease e$%&ain me in etai&" $n the SD:( we have these phases 1. $nitial phase 2. *nalysis phase /. Designing phase ;. (oding phase <. Testing =. Delivery and maintenance $n the initial phase pro-ect manager can prepare a document for the re"uirements! team leader will prepare a team which is having test engineers! developer will provided by the pro-ect manager! tested will prepare test cases for that particular pro-ect *nalysis phase all the members have a meeting to finali7e the technology to develop that pro-ect! the employee! time2 Designing phase the pro-ect manager li+e senior level management will give the directions and source code to the team members to develop the actual code that is guidelines will be given in this phase (oding phase developer will develop the actual code using the source code and they release the application to the tested Testing phase they deploy their test cases to that application and prepare a bug profile document if there is any defect6bug in that application and send it bac+ to developer! developer may rectify and releases than application as ne t build and if the bug not understand it will send to the pro-ect lead in the delivery phase the so test eng can deploy the application in the client environment 4aintenance phase if the client get any problem with the application it may solved by the pro-ect lead with help of testers and developers .1. ;o) o yo- Test A%%&i*ation )ith ha!in( any re=-irement an >o*-ment" $f it is an e isting system or if a build is available then we e plore the system while testing. This helps +nowing the functional use of the system! and its usability. ?y as+ing "uestions to end users and how they use it will be more beneficial. *lso! you may wor+ with ?* to +now more about the system. ?lac+ bo test is nothing but the same where you e plore the system without having any prior +nowledge to the system. .9. What is ba*? en testin( -sin( SQL" E ecuting SN: statements to chec+ if the data submitted by a 9'$ program is

updated in the database or notA E ecuting the statement the data base is connecting to that particular changes! updations or not it will test. ?ac+ end testing is the testing the integration between the application and the database. $t is chec+ing the changes made in the database are getting reflected in the application. E ample: * new column is added in the table. 5ere we test by giving values in the application and value has to be stored in the table. .:. What are the reasons )hy %arameteriHation is ne*essary )hen &oa testin( the Web ser!er an the atabase ser!er" 1hen you test your applications! you may want to chec+ how the application performs the same operations with multiple sets of data. ,or e ample! suppose you want to chec+ how @our 1eb site responds to ten separate sets of data. @ou could record ten separate tests! each with its own set of data. *lternatively! you can create Data Table parameters so that your test runs ten times! each time using a different set of data. 03. >i''eren*e bet)een strate(i* test %&an & test %&an" Strategic test is an organi7ational level term which is applied for all the pro-ects in the organi7ation with small customi7ations Test plan is pro-ect level term and which can be applied for that specific pro-ect only. Test plan is a strategic document which describes how to perform testing in an efficient effective and uptimes way. Nuality lead test lead can prepare this test plan Strategic test plan is an already or new test plan which can bow used in the future for another pro-ect also with some changes in the same organisation. 01. >ra) 7a*?s o' a-tomate testin(" D.*1 ?*(PS 0, *'T4*T$08 E pensive! lac+ of e pertisation! all the areas we can not automate 0#. When )i&& - ma?e -% ate an mo i'y the test obDe*t %ro%erties in the re%ository" 1hen ever the developer may change any one of the ob-ect properties definitely we have to change the same in the 0. ob-ect repository. $f new version net build released from the development department we the test engineers must to modify or update the same is compulsory! other wise than test will show the bug 0+. What is the o*-ment nee e to *reate a test *ase" ;o) - te&& it is test *ase" System re"uirements specification! 'se case document! Test Plan 0,. In *-stomer etai&s 'orm ha!in( 'ie& s &i?e *-stomer name4 *-stomer a ress. A'ter *om%&etion o' this mo -&e4 *&ient raise the *han(e as insert

the t)o ra io b-ttons a'ter *-stomer a ress. ;o) yo- *an *he*? as a tester" 1. ,irst we need to verify whether the radio button is there are notA 2. (onform the radio buttons are present after the customer address or not. /. Herify the no of radio button. ;. Herify only one radio button should be chec+ed initially when we open the (ustomer details form &if it is mentioned in ,S) <. Herify the functionality of the radio buttons i.e. if we chec+ one ratio button! second radio button should be unchec+ed. =. Herify the spell chec+ of radio button label name. >. Herify the alignment of radio buttons in the form. 0.. At the time o' testin( )eb base a%%&i*ations an *&ient ser!er a%%&i*ations4 )hat yo- absorbe as a tester" 1e generally chec+ for the lin+s! data retrieving and posting. 1e perform load and stress testing especially for 1eb based and (lient%Server applications. 00. What are the o*-ments re=-ire to %re%are test %&an" $ntroduction! scope! test team and their responsibilities! test environment S61 B 561 re"uirements! test data preparation! levels of testing! seniority B priority! schedule! ris+! automation Plan! features to test! bug life cycle all these are documents of test plan. 01. What is testin( %o&i*y an testin( metho o&o(y" An )hat is the i''eren*e" Testing policy means all types of testing or testing techni"ues &i.e. functional testing! sanity testing etc).Testing methodology means white bo and blac+ bo testing. 09. What is *om%arison testin(" (omparison Testing means comparing your software with the better one or youDre (ompetitor. 1hile comparison Testing we basically compare the Performance of the software. ,or e $f you have to do (omparison Testing of PD, converter&Des+top ?ased *pplication) then you will compare your software with your (ompetitor on the basis of:% 1. Speed of (onversion PD, file into 1ord. 2. Nuality of converted file. 0:. What is the (enera& testin( %ro*ess" Testing Process: 1. Test re"uirements analysis 2. (reation of Test Strategy &1hich includes creation of Test (ases) /. (reation of Test Plans &1hich includes Test (ases and Test Procedures)

;. E ecution of test cases <. *naly7e the test results =. .eport the defects if any 13. What %arti*i%ation a man-a& tester *an o in o*-mentation" Are there any too&s a!ai&ab&e 'or on&y o*-mentation" @es! 4anual tester will do Sub Test plan documents! as of my +nowledge no tool is used to prepare documentation 11. What is the i''eren*e bet)een &o) an hi(h &e!e& test *ases" Gi!e E$am%&es" 5igh level Test cases are those which covers ma-or functionality in the application &i.e. retrieve! update display! cancel &functionality related test cases)! database test cases). :ow level test cases are those which are related to '$ related testcases. 1#. Is it man atory to -se USE/ASES or ire*t&y one *an )rite test *ases 'rom re=-irements" $tDs not mandatory to write 'se (ases! if the re"uirements are clear you can go ahead with Test (ases. 'se (ases are written to +now the business flow of the module6application. 1+. ;o) oes - e!e&o% test harness" Test Environment Test ?ed Test Environment S61 and 561 Test ?ed: Test Documents li+e Test Plan Document! Test (ase Document. Test Environment means T Test ?ed installation and configuration T 8etwor+ connectivityDs T *ll the Software6 tools $nstallation and configuration T (oordination with Hendors and others 1,. Gi!en re=-irement *o&&e*tion o*4 tester *an %re%are )hi*h test %&an" Test lead can prepare a test plan which performs testing on an application in an efficient effective and in an optimi7ed way. Test development will done by the testers using the test Plan in the test plan they prepare the test strategy 1.. Tester )ith e!e&o% meant ?no)&e (e )i&& be more e''e*ti!e .D-sti'y" $f tester has e perience in Development! it will be useful when testing for logical thin+ing where the error occurs! what is the causeA 5e can guess the functionality of componentA 5e can easily understand the application environmentA Those are plus points which people have Development e perience.

Precisely he can -ustify that either functionality is wrong or right and can analy7e the defects 10.As 'ar as the S>L/ is *on*erne &ast test *ase4)i&& it be )ritten 'or FMaintenan*e PhaseG" *s far as the SD:( is concerned last test case will be written for Q*cceptance TestingR 11. What is test s*enario an test *ase" P&ease e$%&ain in etai&" Test Scenario: Test scenario is li+e laying out plans for testing the product! environmental condition! number of team members re"uired! ma+ing test plans! ma+ing test cases and what all features are to be tested for the product. Test scenario is very much dependent on the product to be tested. Test scenario is made before the actual testing starts. Test (ase: Test case is a document which provides the steps to be e ecuted which has been planned earlier. $t also depends on the type of product to be tested. 8umber of test cases is 8ot fi ed for any product. 19. What is the i''eren*e bet)een ProDe*t 7ase Testin( an Pro -*t 7ase Testin(" Pro-ect based is nothing but client re"uirements. Product based is nothing but mar+et re"uirements. E .stiching shirt is a pro-ect based and ready made shirt is product based. 93. What is testin( %ro*ess in re&ate to A%%&i*ation testin( %ro*ess is the one )hi*h te&&s yo- ho) the a%%&i*ation sho-& be teste in or er to minimiHe the b-(s in the a%%&i*ation" 0ne main thing no application can be released as bug free application which is impossible. 91. What is the i''eren*e b2n Testin( Metho o&o(y an Testin( metho s" Testing 4ethodology define process! set of rules and principle which are follow by group concerned with testing the application. 5ere $ e plain > step testing methodology: 1. Test .e"uirement *nalysis 2. Test Plan /. Test Design ;. Test e ecute <. Defect trac+ =. Test *utomation >. Test 4aintain Testing methods or we can say that Testing Techni"ues: 1hite ?o Testing &'nit Testing! $ntegration Testing)

?lac+ ?o Testing &System Testing! ,unctional Testing! Performance Testing#:oad testing#stress testing#volume testing B Security Testing) '*T &done by user6client with actual6live data) 9#. What are startin( &in?s to test )hi&e )ebsite testin(" 1eb based systems are those using the internet! intranet and e tranets 1eb based testing only needs be done once for any applications using the web. 1eb based testing are as follows: 1. ,unctional correctness 2. $ntegration /. 'sability ;. Security <. Performance =. Herification of code 9+. ;o) GUI testin( )i&& be one in man-a& testin( 'or a )ebsite" ,or any testing there should be some set of standards to be followed. Particularly in 9'$ testing! loo+ and feel should be good. 1e should follow the re"uirements specification documents for 9'$ testing. There should be some screen shots &given by client) which we should follow as it is. *nd for button si7es! font! font si7e !colors used! placing of lin+s! ob-ects and the placing of the ob-ects in the page should be followed some standards. $f we ta+e a button in the page that should be some standard si7e. $f the si7e of that button is more or less the client feel bad about that. So we should have minimum common since while testing 9'$ testing. Some time there may be some mista+es in the screen shots provided by the client also! but that is our responsibility to raise those issues. 9,. What thin(s sho-& be teste in re(ression testin(" 1hile doing .egression Testing a tester must chec+ that any new updating or 4odification or (hange in ,unctionality of a Particular (omponent or 4odule does not create any disorder and any negative affects on the functionality of the *pplication 9.. What is the o*-ment re=-ire to %re%are -rin( testin(" 8ormally Test engineers are responsible for any release of a pro-ect. Even the release is for staging environment or change re"uest release or production release The minimum documents are 1. Test Plan 2. Test (ases /. Test (ase .eport ;. ?ug report. <. .elease notes &which contains +nown issues). =. $nstallation document.

90. What is Test ata" Where )e are -sin( this in testin( %ro*ess" What is the im%ortan*e o' this ata" To e ecute test cases we should have test data. This test data should be for positive and negative testings.for win runner we can get this test data from +eyboard! e cel sheets or from data base 91. What is the i''eren*e bet)een test *ase an test s*ri%t" Test case is a description what data to be tested and what data to be inserted what are the actions to be done to chec+ actual result against e pected result what are the actual inputs we will useA 1hat are the e pected resultsA $s called test script Test Script: $s a short program written in a programming language used to test part of the functionality of the software system. * written set of steps that should be performed manually (an also be called a test scriptU however this is more correctly called a test case. 9:. What is the i''eren*e bet)een b-(4 error an e'e*t" *t the time of coding mista+e error! when the mista+e noticed by the tester defect! tester sends this defect to development team if the developer agrees then it is bug :3. What is the i''eren*e bet)een =-a&ity ass-ran*e an system testin( e$%&ains in etai& )ith an e$am%&e" Nuality *ssurance: $t is nothing but building an ade"uate confidence in the customer that the developed software is acceding to re"uirements. Entire SD:( comes under N*. $t is process oriented. System Testing: $t is the process of e ecuting entire system i.e. chec+ing the s6w as well as parts of system. :1. ;o) o yo- e*i e )hen yo- ha!e Iteste eno-(h@" 1hen the FCO of re"uirements are covered! 4a imum defects are rectified e cept &some) low level defects are not covered! customer satisfy that pro-ect and time is less! then we are closing the testing. :#. What is the i''eren*e bet)een 7-i& Mana(ement an Re&ease Mana(ement" When )i&& *on -*t b-i& !eri'i*ation an en to en testin(" ?uild 4anagement is managing the issue fi ture tas+s in the builds whereas .elease management is managing the functionality to be incorporated in the .elease. ?uild Herification Test &?HT) is done when the build is first received by the testers. The basic functionality is chec+ed with valid data. This is done to chec+ whether the build is testable or not. This is done by testers. End to End testing is also called system testing. Done by senior test engineers or Test lead.

:+. What is bo-n ary !a&-e ana&ysis 57EA6" What is the -se o' it" ?oundary value analysis is a techni"ue for test data selection. Test engineer chooses the values that lie along the data e treams.$t includes ma ! minimum! -ust inside! -ust out side! typical values and error values. ?oundary Halue *nalysis is a techni"ue used for writing the test cases. ,or e ample: $f a particular field accepts the Halues from 1 to 1CCC! then we test that field by entering only 1! 1CCC! C! 1CC1! FFF! 2. $.e. we chec+ on the boundaries and then 4inimum%1! minimum K1 and ma imumK1! ma imum%1. :,. What is e=-i!a&en*e *&ass %artition5E/P6" What is the -se o' it" *"uaplane nothing but select the valid and valid classDs e ample as per client re"uirement the edit bo access only /%< capital alphabets then we divided in esp. li+e valid values only *%V invalid values are a%7 and special characters li+e W!EXO :.. I' there is no s-''i*ient time 'or testin( & - ha!e to *om%&ete the testin(4 then )hat )i&& - o" 1hen $ have less time to test the Product then $ will ta+e these following stepsS 1) Sanity or smo+e testing 2) 'sability Testing /) ,ormal ,unctionality and 9'$ Testing ;) 1al+ through with the Product :0. What is meanin( by %rototy%e in S>L/" This is a cyclic version of the linear model. $n this model! once the re"uirement analysis is done and the design for a prototype is made! the development process gets started. 0nce the prototype is created! it is given to the customer for evaluation. The customer tests the pac+age and gives his6her feed bac+ to the developer who refines the product according to the customerDs e act e pectation. *fter a finite number of iterations! the final software pac+age is 9iven to the customer. $n this methodology! the software is devolved as a result of periodic shuttling of information between the customer and developer. This is the most popular development model in the contemporary $T industry. 4ost of the successful software products have been developed using this model % as it is very difficult &even for a whi7 +idY) To comprehend all the re"uirements of a customer in one shot. There are many variations of this model s+ewed with respect to the pro-ect management styles of the companies. 8ew versions of a software product evolve as a result of prototyping. :1. What is i''eren*e bet)een es?to% an )eb a%%&i*ation" The biggest d6f b6w Des+top and web application is% Des+top *pp &D*) is the machine independent! hence every change has only reflects at the machine level. 1here as 1eb *pp &1*) is the $nternet dependent program! hence any

change in the program reflects at every where! where it becomes use. EZ22 Suppose there are < machines in D*! < times installed individually at every machine and if there is any change made in D* then at every machine change has to be made. $n 1* where the program or *pplication at the Server or at the one common machine! then if changes made at only central or server or common machine all the changes get reflected at Every client machine. :9. >i''eren*e bet)een a%%&i*ation testin( an %ro -*t testin(" Product testing means when any company does testing for their own &companyDs) product e 2 8orton *ntivirus is the SymantecDs productU if Symantec test the 8orton i.e. called *s the Product testing. 1here as if any company ta+e some pro-ects from some other (ompanies li+e *?( (ompany ta+es pro-ects from $?4 and test that pro-ect on some charges i.e. called as *pplication Testing. ::. What is a bro?en &in? in )eb testin( an ho) test it" 1hen we clic+ed on 5yper lin+ if it opens Page canDt be displayed then that 5yper lin+ is called as bro+en lin+.

133J What is /MM &e!e&" I nee the ans)er in etai&. The (apability 4aturity 4odel for Software describes the principles and practices underlying software process maturity and is intended to help software organi7ations improve the maturity of their software processes in terms of an evolutionary path from ad hoc chaotic processes to mature disciplined software processes. The (44 is organi7ed into five maturity levels