Testing+common+interview+questions[2]

TESTING COMMON INTERVIEW QUESTIONS 1. what is contained in srs?,give a sample srs.what is cohesive testing and span control? 2. What is Difference Between QA plan and Test Plan? QA is more over prevention thing which works towards non occurance of error- were as tesplan come s in testin i.e in quality control which works towards how to identify defects/errors 3. what is the Test server 4. What are all the key factors to write system test plan? keyfactors 5. How to perform integration testing on a web application? What are the considerations? Detailed pls. 6. If you have an application, but you do not have any requiremnts available, then how would you perform With out a requirements documents how can u develop an application .if it is developed without any requirements then the application is made with assumptions .Then testing is done depending on the assumptions made through application.In this case, if you are going to work for s ome company, 7. How can you know if a test case is necessary? 8. What is peer review in practical terms? Test cases written by a QA engineer will be reviewed (for correctness) by fellow QA Engineer. 9. How do you know when you have enough test cases to adequately test a software system or module? 10. Who approved your test cases? It depends on the organization. QA Lead, if present, will approve the test cas es. Otherwise, Peer Reviews are a good way of evaluating the test cases. 11. What will you when you find a bug? 1)Ex ecute some more tests, to make clear what the bug EXCATLY is. Suppose, the test case failed when State=NY and Class=Business. Tester has to exceute some more tests to find out whether the problem is with Just 'NY' state or with just 'Busines s' class or with both of them together.2) Report the bug 12. What test plans have you written? Master Test plan is usually prepared by QA Lead. Testers write Test Cases, which in some organizations are called as Test Plans. 13. What is QA? What is Testing? Are they both same or different? Testing is s ubset of QA. Testing is just a phase that comes after coding. But QA is the one that should be incorporated into the entire Software Development Life Cycle. 14. How to write Negative Testcase?Give ex. Negative test cases are written bas ed on think ing abt AUT in a destructive manner in the sense,what happens if i test the application with irrelevant inputs . 15. In an application currently in production, one module of code is being modified. Is it necessary to re-test 1) Test the modified module2) Test all the other modules/areas of the application whic h will have direct/indirect interaction with the modified module. 16. What is included in test strategy?What is overall process of testing step by step and what are various Test strategy is creating a procedure of how to test the software and creating a strategy what all to be tested(screens,process ,modules,..)and time limts for testing process(automated or manual) .So everything has to be planned and implemented.Testing overall procedure isThe duties of software test 17. What is the most challenging situation you had during testing 18. what are you going to do if there is no Functional Spec or any documents related to the system and developer First of all, when a developer left then another one in or someone assigned to take care of the respons ibilities .Most of the functional testing needs more knowledge about the product then the code. Be familiarize with the code. Research similar product in the market. Inc rease communication with related 19. What is the major problem did you resolve during testing process 20. What are the types of functional testing? There are followingtypes of functional testing.1. Functionality testing.2. Input domain testing.3.Error handling testing.about 90% of the functional testing will be covered with teh completion of above three.4. Recovery testing.5.Compatibility testing6.Configuration testing7.Intersystems testing8.Installation

21. 1.how will u write integration test cases2.how will u track bugs from winrunner3.how u customise the A use case is a description of how end-users will use a software c ode. It describes a task or a series of tasks that users will ac complish using the software, and includes the responses of the software to user actions. Use cases may be included in the Software Requirements Document (SRD) as a way of 22. what is the difference between smoke testing and sanity testing smoke testing is conducted by development people according to the clients requirements.the first test conducted by testing people when build is rec eived is called sanity testing.in sanity testing testing people check the basic functionality i.e whether all buttons are working or not etc 23. What is Random Testing? Random data tests confort the application under test with input data generated at random.Typically,testers pay no attention to expect data types.They feed a random sequence of numbers,letters & characters into nummeric data field. 24. What is smoke testing? during this test test engineer reject build with reason, when that build is not working before testing process 25. What is stage containment in testing? 26. Security testing and Performance testing on Communication interface 27. what are the steps in volved in sanity testing? Sanity testing is same as smok e testing. It involves intial testing of the application or module just make sure wether it is stable enough to start testing. Mostly used as a bench mark to gather the readiness of the application for automated testing 28. How do we do calculation testing in banking ferm? 29. What is the Difference Between Rational Robot & WinRunner ? -> Winrunner is just a functional Tool where as Robot, we can use it for both functional (GUI) and performance(VU).-> WR has 4 check points where as Robot has 13 verification points. 30. What is the testing process? Verifying that an input data produce the expected output. 31. What is the difference between testing and quality assurance (QA)? This question is surprisingly popular. However, the answer is quite simple. The goals of both are different: The goal of testing is to find the errors . The goal of QA is to prevent the errors in the program. 32. Difference between QA and QC? simple definitions are: QA:assurance for process control.here we r going to follow certain quality standards and strive for process improvement.we r not going to deal with product.the intension is to follow good quality standards.if we follow these automatically we are going to produce better/best 33. what is the difference between retest and regression testing? hello friends regarding retesting and regression testing this is very important interview question which is asked for every one of us.so as far as my knowledge.retesting:if any modifications r done in the application then testing that particular unit is retesting.regression testing 34. What is the difference between bug priority & bug severity? HiPrority : Urgenc y Of the BugSeverity : Impact of the Bug 35. What kinds of testing do you know? What is it system testing? What is it integration testing? What is You theoretical background and home work may shine in this question. System testing is a testing of the entire system as a whole. This is what user see and feels about the product you provide. Integration testing is the testing of integration of different modules of the system. Usually, the integration 36. What is a bug? What types of bugs do you know? Bug is a error during execution of the program. There are two types of bugs: syntax and logical. 37. What is the difference between structural and functional testing? Structural is a "white box" testing and based on the algorithm or code. Functional testing is a "black box" (behavioral) testing where the tester verifies the func tional specific ation. 38. What is defect density? defect density = Total number of defects/LOCHere the Total number of defects include the defects from Review and from the customer also 39. How would you test a mug (chair/table/gas station etc.)? First of all you must demand requirements and functional specification and design document of the mug. There will find requirements like ability to hold hot water, waterproof, stability, break ability and so on. Then you should test the mug according to all documents.

40. What is considered a successful test? A test that disc overed more errors. The whole purpose of testing process is to discover as many bugs and errors as possible. Test that covers more functionality and discovers more errors in your software product, therefore c onsidered more successful. 41. What bug tracking system did you use? Again and again, it does not matter what bug tracking system did you use if you made your homework and invented the name of such or mentioned a standard one. You may say you've used proprietary bug tracking system (works especially well if you previous company was this way or another dealing with databases) 42. When does testing begin - requirements, plan, design, code / testing phase? Obviously Testing will begins in requirement phase. 43. Could you test a program 100%? 90%? Why? Definitely not! The major problem with testing that you cannot calculate how many error are in the code, functioning etc. There are many factors involved such as experience of programmer, complexity of the system etc. 44. What is the difference between testing and debugging? Big difference is that debugging is conducted by a programmer and the programmer fix the errors during debugging phase. Tester never fixes the errors, but rather find them and return to programmer. 45. How would you conduct your test? Each test is based on the technical requirements of the software product. 46. Have you used automatic testing tools. Which ones? If you never have seen automation tools before, do not try to fool around the interviewer. You produce a bad impression when "caught" on lying to the interviewer. However, if you ever used the automation tools, it would be a huge advantage for us to mention them even if those tools were proprietary automation 47. How would you build a test with WinRunner? Rational Visual Test? First of all, see the comments to the previous question. Then, all automation testing tools I ever heard of have a GUI recorder which allows you to record the basic user interactions with the software underneath. Then, you manually update your initial script to suit your needs. You must know scripting 48. What is considered a good test? Good test is a test covering most of the object's functionality. 49. How would you conduct a test: top-down or down-top? What is it? Which one is better? Down-Top: unit -> interface -> s ystem. Top-Down is a vice versa. You may use both, but downtop allows to discover malfunctioning at earlier phases of dev elopment and cheaper to fix than in the case of top-down. 50. How to develop a test plan ? How to develop a test case? Test plan consists of test cases. Test cases you develop according to requirement and design documents of the unit, system etc. You may be asked what would you do if you are not provided with requirements documents. Then, you start creating your test cases based on functionality of the system. You should 51. How do you see a QA role in the product development life cycle? QA should be involved in early stages of the development process in order to create an adequate test cases and better general understanding of the system. QA, however, must be separated from the development team to ensure that there is no influence of developers on QA engineers. As a last resort before 52. What is the size of your executable? 10MB. Who cares? You should demonstrate that you can't be caught with unexpected questions. This question is one of the dumbest, but you must react accordingly. Tell any reasonable number you want, but be careful not to exaggerate! 53. What version of Oracle database did you use? Homework. Tell any version number you want - not many interviewers know the difference at version level. However, do not tell any numbers if you never work ed with Oracle! 54. How would you execute a SQL query in Oracle 8? Again, if you ever worked with Oracle, this question should be trivial for you to answer (from command prompt, of course) If you never worked with Oracle, note politely that you did not touch an Orac le database on your career path. 55. What version of OS were you using? Tell whatever you want - you can't be caught here. Popular answers are Windows 95/98, Windows 2000 (make sure you know various flavors) and various Unix flavors (AIX, Solaris, SunOS, HPUX etc.) 56. Have you tested front-end of back-end? In other word you are asked if you tested GUI part of the application or server part of your application.

57. What was the most difficult problem you ever found while testing? This is homework. Think about one and give it as an example. 58. What were you responsible to test in your previous company? This is homework for you. Actually, this question is a test of the knowledge of your own resume. You must know your real or fake resume as a bible. Practice in front of mirror or ask you 59. Why do you like to test? You enjoy bug hunting process, feel great being between developers and customers, your background and experience are targeting the testing techniques enhancements and you feel proud of your contribution to the whole development process. 60. What role do you see yourself in 2-3 years from now? Would you want to become a developer? You should not concentrate the attention of the interviewer on your wish to become a developer. You are being hired for testing role and you should demonstrate reliability. Team lead of QA team is OK, but do not answer yes when asked if you are willing to become a developer.