Why you chose Testing as a career? in my view testing is a challenge. Because as a tester u have to find defects in an application.

it proves ur efficiency. Because as tester well get more knowledge on the application i.e. the complete end to end flow and functionality of the project. and thinking and writing scenarios to break the functionality of the application is more interesting. I have chosen Testing cause I am a 'Good analyzer'; I have chosen testing as a carrier bcoz it is most responsible job for releasing the product. I chose testing as a career because the Tester is the person who finally decides the quality of the product. A lot depends on the tester while delivering the project to the customer. Questions: 1. what is the difference between sevierty and priority Severity means how server is the functionality affected by the bug (or mismatch). Priority
means how quickly the bug should be fixed.

Severity: is how bad this bug impact on the system. Priority: Is how important this bug is. Severity: This is assigned by the tester. Severity of a defect is set based on the issue's seriousness. it can be stated as mentioned. Show stopper: 4 Major defect: 3 Minor defect: 2 Cosmetic: 1 Setting values for these four categories can be again defined by the organization based on their views. Showstopper: this have a higher severity as u cannot proceed further testing with the application testing. Major: If there are any main defect based on the functionality. Minor: If there is any error in the functionality of one object under one functionality Cosmetic: any error based on the look and feel of the system or improper location of the object (something based on the design of the web page) Priority: this will be set by the team lead or the project lead. based on the severity and the time constraint that the module has the priority will be set 2. After receiving the build. How will you start the testing? First we will do smoke testing on application build, if build is stable then i will proceed to system testing phase Whenever we receiving the application build (.exe) from the developers first we will perform sanity testing. Here testing team verifies whether the app. build is stable or not. After completion of sanity testing then we will go for system testing. 3. What is Test Harness, explain in Detail? 1. In software testing, a test harness or automated test framework is a collection of software and test data configured to test a program unit by running it under varying conditions and monitoring its behavior and outputs. It has two main parts: the Test execution engine and the Test script repository. Test harnesses allow for the automation of tests. They can call functions with supplied parameters and print out and compare the results to the desired value. The test harness is a hook to the developed code, which can be tested using an automation framework.

 A test harness should allow specific tests to run (this helps in optimizing), orchestrate a runtime environment, and provide a capability to analyze results. The typical objectives of a test harness are to: i. Automate the testing process. ii. Execute test suites of test cases. iii. Generate associated test reports 2. In software testing, a test harness is a collection of software tools and test data configured to test a program unit by running it under varying conditions and monitor its behavior and outputs. 4. What is difference between localization testing and internationalization testing? Explain with an example? Internationalization, or localization, testing involves verifying that formats and structures that vary by locale are followed. We can test for any localization inconsistencies. We will follow the standards and formats defined by the client, which often conform to a widely recognized regional standard such as metric vs. standard, date formats, number grouping/decimal formats, and time zone/format differences. The goal of internationalization testing is to confirm that the locale-specific formats and standards are followed. Localization Testing Localization translates the product UI and occasionally changes some initial settings to make it suitable for another region. Localization testing checks the quality of a product's localization for a particular target culture/locale. This test is based on the results of globalization testing, which verifies the functional support for that particular culture/locale. Localization testing can be executed only on the localized version of a product. Localizability testing does not test for localization quality. The test effort during localization testing focuses on: Areas affected by localization, such as UI and content Culture/locale-specific, language-specific, and region-specific areas In addition, localization testing should include: Basic functionality tests Setup and upgrade tests run in the localized environment Plan application and hardware compatibility tests according to the product's target region Internationalization is the process of designing and coding a product so it can perform properly when it is modified for use in different languages and locales. Localization (also known as L10N) refers to the process, on a properly internationalized base product, of translating messages and documentation as well as modifying other locale specific files. Assuming that there is not a separate base product for the locale, the localized files are installed at their proper location in the base product. This product is then released as a localized version of the product. Localizing a properly internationalized product in most cases should require no changes to the source code.

5. What is meant by deferred status? The bug, changed to deferred state means the bug is expected to be fixed in next releases. The reasons for changing the bug to this state have many factors. Some of them are priority of the bug may be low, lack of time for the release or the bug may not have major effect on the software. Postponing the resolution of the bug due lack of time, lack of knowledge is called differed (In other terms putting the issue to on hold status) 6. what is fpa ? fpa means function point analysis or feature point analysis and is a technique to Estimate the size of project in terms of lines of code FPA "Function point analysis" is used to measure the size of functionality of an information system The FPA technique involves viewing the functionality of software from the users perspective and then estimating the size based on the required functionality. 7. What is the Difference between Stub Testing and Driver Testing? Test driver is a s/w component or module used to test the sub module in the absence of main module. Test stub is a dummy module to receive calls from main module. It is used to test the main module in the absence of sub module Test Driver - A program or test tool used to execute software against a test case suite. Stubs - A skeletal or special-purpose implementation of a software module, used to develop or test a component that calls or is otherwise dependent on it. After [IEEE].

8. What is the entry criteria and exit criteria for system testing? Entry Criteria: The conditions that must exist before a unit of project work can commence. Exit Criteria: The conditions that must exist before a unit of project work can be deemed complete. Entry Criteria for Unit testing phase are: The following documents have been completed reviewed and approved: 1. Business Requirement Document complete 2. Program Required Documents complete 3. Preliminary Software Development Project Plan 4. Phase 1 Planning 5. Functional Specification 6. High-Level Design Specifications 7. Software Development Project Plan approved 8. Software Verification Plan approved 9. Software Configuration Management Plan 10. Quality Assurance Plan approved.

Exit criteria for the Unit testing phase are: 1. Unit test has been passed 2. The module resides in a baseline directory 3. The project is code-complete. There are no missing features or media elements 4. All priority a bug have been fixed and closed 5. Internal documentation has been updated to reflect the current state of the product. Note: Unit testing will be performed mostly by the Developer. Entry Criteria for Integration testing phase are: 1. The project is code-complete. There are no missing features or media elements 2. The product satisfies the performance and memory requirements specified by the Functional Spec. 3. Software/Curriculum have run and passed a Sanity Test that has been provided by the QA group. 4. All priority a bug have been fixed and closed 5. Internal documentation has been updated to reflect the current state of the product. 6. Curriculum has done a content review of the lessons. Exit Criteria for Integration phase are: 1. The Integration engineer has tested for install ability. 2. All priority a bug have been fixed and closed. 3. Internal documentation has been updated to reflect the current state of the product. 4. The Technical Lead has submitted all files for integration accompanied by Release Notes. Entry Criteria for System testing phase are: 1. QA has spot tested content features and functionality of the product and verified that it is feature-complete. 2. The user interface and the feature set are frozen. 3. The final CD-ROM layout has been determined. 4. The Technical Lead has submitted all files for integration accompanied by Release Notes. 5. The Integration engineer has tested for install ability. 6. All priority a bug have been fixed and closed. 7. Internal documentation has been updated to reflect the current state of the product. Exit Criteria for System testing The Exit Criteria for the System testing phase are: 1. Final Publications Draft of product publications including the Quick Start Guide has been reviewed tested in QA and approved by the Core Team. 2. All priority a bug have been fixed and closed. 3. The software runs on all the product s supported hardware and software configurations. 4. The product is compatible with third-party products as specified in the Functional Spec. Final Entry Criteria The Entry Criteria for the Final phase are 1. Quality Assurance Plan approved. 2. The work has been approved and signed off by Product Marketing 3. Final Publications Draft of product publications including the Quick Start Guide has been reviewed tested in QA and approved by the Core Team. 4. All priority a bug have been fixed and closed. 5. The software runs on all the product s supported hardware and software configurations. 6. The product is compatible with third-party products as specified in the Functional Spec.

9. What do u do if a bug logged by u is not reproducible in developers environment (developers environment is same as urs) 10. what responsibility of system administrator? 11. what are the Levels of testing? Unit Testing Integration Testing System Testing Acceptance Testing Regression Testing There are 4 levels of testing Level 0: Sanity Testing test whether build is testable Or not Level 1: Unit testing, Integration Testing, System Testing Level 2: Regression Testing Level 3: Final Regression testing or Postmortem Testing Or 4. User Acceptance Testing 12. Who can perform the unit testing? 13. explain v model in detail(pls explain with real tme company process)? 14. in configuration tool as a tester which documents u r going to add?? 15. 1. Unit testing ->integration testing->system testing->UAT in this where do u do the functional testing & regression testing? if these two done in each phase why should not mentioned in that ? 16. what is difference between build and version 17. What was early release of Quality centre called? 18. What is the traceability matrix template? Darw the all fields? 19. what is the diff between BVA & ECP and also advantages about these techniques..& i want some proper examples... 20. how does a client /server environment affects testing? 21. How much interaction with users should testers have, and why? 22. The program prints data on the screen instead of the printer. Referring to the fault above, which load condition errors has occurred? 23. What are initial conditions?

24. is QUALITY CENTER & TEST DIRECTOR are same or different ? 25. write the test cases that you have scheduled an interview and you came for the same and you are about to take the interview. 26. As experienced what could be the interview questions based on project? 27. What is the Model/Process do u follow in your Organization for Testing? 28. At what stage unit testing has to be done? 29. What is "V-n-V" Model ? Why is it called as "V"& why not "U" ? Also tell at what Stage Testing should be best to stared? 30. You get the build directly from the developer or through tl, if so how? 31. As a tester what type of document req. on tester's bench to design the test cases and for execution. What will be the practical approach If we are using excel-sheet. through excel- sheet how tester communicate with developers about the test cases and result and what will be the cycle of testing between tester and developers. what type of MANGEMNT TOOL (like VSS) should be used (PLEASE IN DETAIL)by tester if he is working in small company. 32. Give an example of low severity and high priority bug? 33. Requirement is given : 1) The Login screen should require with 2 fields "Login" & "Password" 2) After successful login Success Message will display. 3) For Invalid login Error Message will display. 4) "Login" & "Password" both fields are case insensitive. 5) The Application should be Dialog application. What are the test cases for above requirements? 34. how can i derive the test case for requirement and use case ? 35. Nowadays Product based testing is done is almost all companies. What does a "Product" actually means. 36. at the time of testing web based applications and client server applications, what you observed as a tester? (i need not differences, but i need what you observed at the time of testing as a tester) 37. me what is the Buffer size of transmission buffer or rectiption buffer in TM,UM and AM of RLC. 38. What is the common in all s.o.p (standard operating procedure)? 39. Why use caffine for HPLC calibration ? 40. What is the difference between use case and test case? give example.

41. what is security testing? can u please set an example for it? 42. why Test plan is needed?? 43. Can anybody tell me by referring which document a tester writes test scenarios? And what is the need of test scenarios an how a tester determine the coverage of test scenario? 44. any one can explain error guessing..?it depends on validation or functional testing? give one example ..? 45. when 200 test cases are to be written in a single day, then what will you do? 46. Difference between regression and retesting? 47. Specify another matrix/table used for same functionality as of traceability matrix? 48. what is the entry and exit criteria for system testing in v model 49. From which phase will you start testing and How will you find out the left out things in testing? 50. what will you do in review meetings? 51. Could anyone let me how to write test cases in Manual Testing with the real time examples. 52. What is role of tester in spiral model? 53. Write max. no of test case's in following scenario Developer develops single page which consist of simple Text box and a Submit button. Developer has not written a single line of code for the button (i.e. no relation of Text box and Submit button). No validations are implemented on Test box as well as button. 54. what is white box testing and what is the techniques 55. How many types of applications are available for a Test engineer to test? In detail? PLZ. 56. what is the difference between reporting and testing? which one is good to choose as a carrer? 57. 1. can u explain about testing levels and its type with example? 2. First explain about both testing. then difference B/W sanity and smoke testing? 3. Explain about integration , functional , system testing? 4. what are methods use to writing test cases? 58. Can any body tell me in real time how cookies testing is done. And please tell me the steps.And for cookies testing test cases is needed. 59. As a Tester how we choose black or white box testing technique for a application?

60. Can any one explain about USE CASES? 61. what is the importance of SQL and SQL Server in Testing and also let me know the best institue for SQL and SQL SERVER for this 2 courses? Thanks in Advance. 62. what is the Quality and Value that you are going to add to your company 63. Wat is de difference btw inspection and walkthrough in static testing? 64. Is Validation Test & Negative Tests have same meaning???Are both same??? 65. What is the difference between Smoke testing & Sanity Testing? 66. When the Developer fixes and releases a defect.. then the tester tests it and fails the defect. Suppose the developer again fixes it and the tester again fails it and this process continues for the same defect for more times then what is that u do for getting the defect closed? 67. why do you go for white box testing when black box testing is available? 68. What is database testing? 69. What is CRD and SRD file 70. what is strategy? 71. what are reviews in sdlc? 72. How would you ensure 100% coverage of testing? 73. define the testing technique? 74. What is waterfall model? explain? what is v model? explain all phase? and the difference between two model? 75. Differentiate regular regression testing and final regression testing 76. what is the difference between branch coverage, decision coverage and condition coverage? 77. What is red box testing and yellow box testing?