Anda di halaman 1dari 4

Question 1: Difference between Smoke and Sanity testing? http://www.guru99.com/smoke-sanity-testing.

html Answer 1 : Testing done with an intent to check the ma or operational features of the build so as to !erify that the features are working properly or not is been reffered as "Smoke testing# . $or e%ample: - Ser!er &unching' Dri!er launching . (hereas the purpose to stable the system by checking the deeper details and the rele!ant interaction among the modules is been reffered as "Sanity testing# Question 2: Difference between Sanity and )egression Testing? Answer 2 : The purpose of stability of the system by checking the deeper details and the rele!ant interaction among the modules is been reffered as "Sanity testing# whereas testing done with an intent to check the application under test when there is a change in the software or in the en!ironment of the application under test*+,T- so as to !erify wheather a new bug might ha!e not been introduce with an e%isting system will be reffered as ")egression testing# Question 3: Difference between Smoke and )egression Testing? Answer 3 : Testing done with an intent to check the ma or operational features of the build so as to !erify that the features are working properly or not is been reffered as "Smoke testing# . $or e%ample: - Ser!er &unching' Dri!er launching. (hereas testing done with an intent to check the application under test when there is a change in the software or in the en!ironment of the application under test*+,T- so as to !erify wheather a new bug might ha!e not been introduce with an e%isting system will be reffered as ")egression testing#. Question 4:Difference between )egression and )e-testing? Answer 4 : Testing done with an intent to check the application under test when there is a change in the software or in the en!ironment of the application under test*+,T- so as to !erify wheather a new bug might ha!e not been introduce with an e%isting system will be reffered as ")egression testing#. )e-e%ecuting the same set up test data on the application under test*+,T- so as to !erify the bug has been fi%ed or not is been reffered as )e-testing. Question 5: Difference between .ompatibilty and )e-testing? Answer 5 : Testing done with an intent to check the software re/uirement with +,T to !erify the optimi0e compatibility of the system is been reffered as ".ompatibility Testing#. )e-e%ecuting the same set up test data on the application under test*+,T- so as to !erify the bug has been fi%ed or not is been reffered as )e-testing.

Question 6: Difference between ,serbility and ,ser-interface testing? Answer 6 : Testing done with an intent to check the ease of use of the application under test*+,T- so as to identify how easy is to learn' obser!e' and understand that application by !erifying the non functional re/uirements. The purpose of this testing is to ensure the user friendliness of the +,T. (hereas testing done with an intent to check the design specification of the +pplication under Test*+,T- on the basis of S)S and 1)D is been reffered as ,ser-interface testing. The purpose of this testing is to ensure look in for application. Question 7: (hat are the ad!antages and disad!antages of (hite-1o% testing? Answer 7 : +d!antages : $orces test de!eloper to reason carefully about implementation +ppro%imates the partitioning done by e%ecution e/ui!alence )e!eals errors in 2hidden2 code: 1eneficent side-effects 3ptimi0ations *e.g. chartable that changes reps when si0e 4 566+s the knowledge of internal coding structure is prere/uisite' it becomes !ery easy to find out which type of input/data can help in testing the application effecti!ely. The other ad!antage of white bo% testing is that it helps in optimi0ing the code. 7t helps in remo!ing the e%tra lines of code' which can bring in hidden defects.

Disad!antages : 8%pensi!e 9iss cases omitted in the code +s knowledge of code and internal structure is a prere/uisite' a skilled tester is needed to carry out this type of testing' which increases the cost. +nd it is nearly impossible to look into e!ery bit of code to find out hidden errors' which may create problems' resulting in failure of the application. :ot looking at the code in a runtime en!ironment. That;s important for a number of reasons. 8%ploitation of !ulnerability is dependent upon all aspects of the platform being targeted and source code is ust of those components. The underlying operating system' the backend database being used' third party security tools' dependent libraries' etc. must all be taken into account when determining e%ploitability. + source code re!iew is not able to take these factors into account.

<ery few white-bo% tests can be done without modifying the program' changing !alues to force different e%ecution paths' or to generate a full range of inputs to test a particular function.

Question 8: (hat are the ad!antages and disad!antages of 1lack-1o% testing? Answer 8 : +d!antages : 1lack bo% tests are reproducible. The en!ironment the program is running is also tested. The in!ested effort can be used multiple times. Tester needs no knowledge of implementation' including specific programming languages Tests are done from a user;s point of !iew (ill help to e%pose any ambiguities or inconsistencies in the specifications 8fficient when used on &arger systems +s the tester and de!eloper are independent of each other' test is balanced and unpre udiced Tester can be non-technical. There is no need of ha!ing detailed functional knowledge of system to the tester. Tests will be done from an end user;s point of !iew. 1ecause end user should accept the system. *This is reason' sometimes this testing techni/ue is also called as +cceptance testingTesting helps to identify the !agueness and contradiction in functional specifications. Test cases can be designed as soon as the functional specifications are complete

Disad!antages: The results are often o!erestimated. :ot all properties of a software product can be tested The reason for a failure is not found. 3nly a small number of possible inputs can actually be tested' to test e!ery possible input stream would take nearly fore!er (ithout clear and concise specifications' test cases are hard to design There may be unnecessary repetition of test inputs if the tester is not informed of test cases the programmer has already tried 9ay lea!e many program paths untested .annot be directed toward specific segments of code which may be !ery comple% *and therefore more error prone-

Test cases are tough and challenging to design' without ha!ing clear functional specifications 7t is difficult to identify tricky inputs' if the test cases are not de!eloped based on specifications. 7t is difficult to identify all possible inputs in limited testing time. So writing test cases is slow and difficult .hances of ha!ing unidentified paths during this testing .hances of ha!ing repetition of tests that are already done by programmer.