1. I-soft What should be done after writing test case?? -----------------------------------------------------------------------2.Covansys Testing 1. What is bidirectional traceability ??? and how it is implemented * When requirements can be traced by code and code can be traced by requirement * Done throughout the development process * To ensure that all the requirements are implemented in the system Agreed but the definition of Bi-directional Traceability is that both vertical and Horizontal traceability is maintained. Horizontal Traceability is the traceability of requirements across all the development phases Req-> Design->Module Spec>Unit Testing-> Module testing->Integration testing-> Systems testing Vertical traceability is the traceability of the requirements across modules or other requirements in the product. This may not apply to all project / products because this requirements was an outcome of having large projects such as the ones executed by NASA and US Military. ----------------------------------------------------------------------2. What is Automation Test frame work ? A Test Automation Framework is a set of assumptions, concepts and tools that provide support for automated software testing. The main advantage of such a framework is the low cost for maintenance. If there is change to any test case then only the test case file needs to be updated and the Driver Script and Startup script will remain the same. There's no need to update the scripts in case of changes to the application. Different Frame works Modularity-driven testing Data-driven testing Keyword-driven testing Model-based testing Hybrid testing -----------------------------------------------------------------------3. Define the components present in test strategy It is a company level document developed bye quality assurance manager or quality analyst category people. It defines testing approach to reach the standards. During

test strategy document preparation QA people concentrate on below factors: 1. scope and Objective 2. Budget control 3. Testing approach 4. Test deliverables 5. roles and responsibilities 6. communication and status reporting 7. automation tools (if needed) 8. testing measurements 9. risks and litigations 10. change configuration management 11. training plan ----------------------------------------------------------------------4. Define the components present in test plan Test Plan: Test plan is a document that describes the objectives,scope,approach,and focus of a s/w testing effort. ---------------------------------------------------------------------5. Define database testing ? Database Testing: Database Testing basically include in the following areas 1.Data Validity Testing. 2.Data Integrity Testing. 3.Performance Related Testing 4.Testing of Procedure,Triggers and Functions Severity: Severity actually bug impacted on functionality of an application. Priority: Priority means how it soon will be fixed example for low severity and high priority: In an application instead of 'Accenture' Axenture will be there this is a functional side bug. there is spelling mistake will be there, functionally it is a come under low severity and customer side it is come under high priority ----------------------------------------------------------------------6. What is the difference between QA and QC . Quality Control = Processes used to test the Project Functionality Quality Assurance = Measures the quality of QC processes used to create a Quality Project. -----------------------------------------------------------------------7. What is the difference between V&V 8. What are different types of test case that u have written in your project.. 9. Have u written Test plan ?.

SQL 1. What is joins and define all the joins 2. What is Foreign key ? 3. Write an SQL query if u want to select the data from one block which intern reflects in another block ? Unix 1. Which command is used to run an interface? 2. How will you see the hidden file ? Ls -a 3. What is the command used to set the date and timing's 4. Some basic commands like copy, move,delete ? rm, 5. Which command used to the go back to the home directory . 6. Which command used to view the the current directory PWD. 3. Virtusa Testing 1. Tell me about Yourself? 2. Testing process followed in your company -----------------------------------------------------------------------3. Testing Methodology We begin the testing process by developing a comprehensive plan to test the general functionality and special features on a variety of platform combinations. Strict quality control procedures are used. The process verifies that the application meets the requirements specified in the system requirements document and is bug free. At the end of each testing day, the team prepares a summary of completed and failed tests. Our programmers address any identified issues, and the application is resubmitted to the testing team until every item is resolved. All changes and retesting are tracked through spreadsheets available to both the testing and programming teams. Applications are not allowed to launch until all identified problems are fixed. A report is prepared at the end of testing to show exactly what was tested and to list the final outcomes. Our software testing methodology is applied in four distinct phases: unit testing, system testing, integration testing, and acceptance testing -----------------------------------------------------------------------4. Where u maintains the Repositories? Test repository is the database for the test cases where we keep the previously run test cases. Its also called test suite. Need for maintaining is the reviewability, future

reference, Time saving example if a person working on a test case has left the company who will know that which test case was run for a particular scenario if it comes again in any other project. 5. What is CVS? CVS is version control system. It is used to handle the different versions being released for your product. 6. Bug Tool used? -----------------------------------------------------------------------7. How will you prepare traceability matrix if there is no Business Doc and Functional Doc? Actually traceability matrix was created for keeping track of Functional Requirement against each Business Requirement. each business requirement will have multiple functional requirement mentioning the features, process, outcome and so on. This is part of RUP standard. Traceability matrix is tracing your requirements to your test cases or any other documents. 8. How will you validate the functionality of the Test cases, if there is no business requirement document or user requirement document as such 9. Testing process followed in your company? ----------------------------------------------------------------------10. Tell me about CMM LEVEL -4 what are steps that to be followed to achieve the CMM-IV standards? CMM LEVEL 1: the company would not have any specific plan or procedure to carry out the project they will follow their own procedures CMM LEVEL2:the company would formulate some procedures to carry out a project but that also not well managed CMM LEVEL3: the company would go proper life cycle and they organize it from the start of the project till the completion CMM4: the company should have proper regulatory committee called quality assurance department to take care of the process life cycle to enhance the quality of the process CMM5: the company have proper life cycle ,QA team and there will be periodic suggestions and analysis will happen in order to keep the quality high -----------------------------------------------------------------------11. What is Back End testing? Back end Testing means database Testing.

Normally a software product/application uses GUI front end for easy user interaction. The Data entered in the front end will be stored in the back end database. The data base may be oracle,MSSQL Server,MY SQL,DB2...etc The data will be organized in the tables as record. Major aim of using database is to support the content of the page. so it is critical and very important to check back end or database. Back end Testing means ensuring that, If you enter data in the front end ,the data should be stored properly in the back end. If you call that stored record frown front end it should display properly. I think you have cleared with this .. ----------------------------------------------------------------------12. What is Unit Testing? 13. How will u write test cases for an given scenarioi.e. main page, login screen, transaction, Report Verification? Test Scenario Re Test Cases Or Test Scripts,and the Sequence In which they are To Be executed. 14. How will u write traceability matrix? 15. What is CVS and why it is used? 16. What will be specified in the Defect Report? ----------------------------------------------------------------------17. What is Test summary Report? it is the product outcome of the testing endeavor, this report should summarize all of the testing that was performed during testing phase. This is not the sole property of testing department. This report can be produced once test plan is completed, the tests like unit test, integration test, system test, security test and user acceptance test completed, and all associated test reports available -------------------------------------------------------------------18. What is Test Closure report? i think the test closure document is nothing but the test summary report which we give after the whole testing is finished....it gives panoramic view of total test result it contains 1.Total number of test cases

2.Total number of bugs found 3.Number of bugs resolved(fixed) 4.Number of Bugs rejected 5.Total number of bugs differed......tec ----------------------------------------------------------------------19. Explain Defect life cycle 20. What will be specified in the Test Case 21. What are the Testing methodologies that u have followed in your project ? 22. What kind of testing that u have been involved in and explain about it. 23. What is UAT Testing? 24. What is joins and what are the different types of joins in SQL and explain the same? 25. What is Foreign Key in SQL? KLA Tencor 1. Bug life cycle? 2. Explain about the Project. And draw the architecture of your project? 3. What are the different types of severity? 4. Defect tracking tools used? 5. what are the responsibilities of an tester? 6. Give some example how will you write the test cases if an scenario involves Login screen. Aztec ----------------------------------------------------------------------1. What are the different types of testing followed .. unit testing,smoke,sanity,integration,w.b.t,B.B.t,Functional testing ,retesting,compatabilty,acceptance,Stress,load, -----------------------------------------------------------------------2. What are the different levels of testing used during testing the application? ----------------------------------------------------------------------4. What type of testing will be done in Installation testing or system testing? System testing will be done by Blackbox testers Blackbox testing will be done. testing will done in 3 types 1.Big ban approach 2.Top down approach 3.Bottom up approach the type of testing done in installation testing is static testing.i.e.we will just verify the documents and check whether we are able to install the product according to the guide lines given.so here we will be doing only verification.

the type of testing done in system testing is dynamic testing. here we will execute test cases. correct me if i am wrong. ----------------------------------------------------------------------5. What is meant by CMMI what are different types of CMM Level? CMM more about software development .CMMI Software development and System engineering. Means CMMI also suits the mfg industry also. 6. Explain about the components involved in CMM-4 level 7. Explain about Performance testing ? ---------------------------------------------------------------------8. What is Traceability matrix and how it is done ? Hi, If you want to prepate Traceability matrix for web testing, first you need to identify Quality factors(i.e.reliability, correctness,completeness,integrity etc..)that are Important for your web based application(Non availability of these Quality factors becomes Potential risk of your application) and also Prepare Test requirements( test cases)to cover required quality factors. Mapping of these test cases to Quality factors to ensure Test coverage is said to be Traceability matrix. -----------------------------------------------------------------9. How can you differentiate Severity and Priority based on technical and business point of view. 10. What is the difference between Test life cycle and defect life cycle ? 11. How will u ensure that you have covered all the functionality while writing test cases if there is no functional spec and there is no KT about the application? Kinds of Testing WHAT KINDS OF TESTING SHOULD BE CONSIDERED? 1. Black box testing: not based on any knowledge of internal design or code. Tests are based on requirements and functionality 2. White box testing: based on knowledge of the internal logic of an applications code. Tests are based on coverage of code statements, branches, paths, and conditions. 3. Unit testing: the most micro scale of testing; to test particular functions or code modules. Typically done by the programmer and not by testers, as it requires detailed knowledge of the internal program design and code. Not always easily done unless the application has a well-designed architecture with tight code; may require developing test driver modules or test harnesses. 4. Incremental integration testing: continuous testing of an application as new functionality is added; requires that various aspects of an applications functionality be independent enough to work separately before all parts of the program are completed, or

that test drivers be developed as needed; done by programmers or by testers. 6. Integration testing: testing of combined parts of an application to determine if they function together correctly the parts can be code modules, individual applications, client and server applications on a networked. This type of testing is especially relevant to client/server and distributed systems. 7. Functional testing: black-box type testing geared to functional requirements of an application; testers should do this type of testing. This does not mean that the programmers should not check their code works before releasing it(which of course applies to any stage of testing). 8. System testing: black box type testing that is based on overall requirements specifications; covers all combined parts of system. 9. End to end testing: similar to system testing; the macro end of the test scale; involves testing of a complete application environment in a situation that mimics real-world use, such as interacting with database, using network communications, or interacting with other hardware, applications, or systems if appropriate. 10. Sanity testing: typically an initial testing effort to determine if a new software version is performing well enough to accept it for a major testing effort. For example, if the new software is crashing systems every 5minutes warrant further testing in item current state. 11. Regression testing: re-testing after fixes or modifications of the software or its environment. It can be difficult to determine how much re-testing is needed, especially near the end of the development cycle. Automated testing tools can be especially useful for this type of testing. 12. Acceptance testing: final testing based on specifications of the end-user or customer, or based on use by end users/customers over some limited period of time. 13. Load testing: testing an application under heavy loads, such as testing of a web site under a range of loads to determine at what point the systems response time degrades or fails. 14. Stress testing: term often used interchangeably with load and performance testing. Also used to describe such tests as system functional testing while under unusually heavy loads, heavy repletion of certain actions or inputs input of large numerical values, large complex queries to a database system, etc. 15. Performance testing: term often used interchangeable with stress and load testing. Ideally performance testing (and another type of testing) is defined in requirements documentation or QA or test plans. 16. Usability testing: testing for user-friendlinesses. Clearly this is subjective,and will depend on the targeted end-user or customer. User interviews, surveys, video recording of user sessions, and other techniques can be used programmers and testers are usually not appropriate as usability testers. 17. Install/uninstall testing: testing of full, partial, or upgrade install/uninstall processes. 18. Recovery testing: testing how well a system recovers from crashes, hardware failures or other catastrophic problems. 19. Security testing: testing how well system protects against unauthorized internal or external access, damage, etc, any require sophisticated testing techniques. 20. Compatibility testing: testing how well software performs in a particular hardware/software/operating/system/network/etc environment. 21. Exploratory testing: often taken to mean a creative, informal software test that is not

based on formal test plans of test cases; testers may be learning the software as they test it. 22. Ad-hoc testing: similar to exploratory testing, but often taken to mean that the testers have significant understanding of the software testing it. 23. User acceptance testing: determining if software is satisfactory to an end-user or customer. 24. Comparison testing: comparing software weakness and strengths to competing products. 25. Alpha testing: testing of an application when development is nearing completion; minor design changes may still be made as a result of such testing. Typically done by end-users or others, not by programmers or testers. 26. Beta testing: testing when development and testing are essentially completed and final bugs and problems need to be found before final release. Typically done by endusers or others, not by programmers or testers. 27. Mutation testing: method for determining if a set of test data or test cases is useful, by deliberately introducing various code changes (bugs) and retesting with the original test data/cases to determine if the bugs are detected proper implementation requires large computational resources. Difference between client server testing and web server testing. Web systems are one type of client/server. The client is the browser, the server is whatever is on the back end (database, proxy, mirror, etc). This differs from so-called traditional client/server in a few ways but both systems are a type of client/server. There is a certain client that connects via some protocol with a server (or set of servers). Also understand that in a strict difference based on how the question is worded, testing a Web server specifically is simply testing the functionality and performance of the Web server itself. (For example, I might test if HTTP Keep-Alives are enabled and if that works. Or I might test if the logging feature is working. Or I might test certain filters, like ISAPI. Or I might test some general characteristics such as the load the server can take.) In the case of client server testing, as you have worded it, you might be doing the same general things to some other type of server, such as a database server. Also note that you can be testing the server directly, in some cases, and other times you can be testing it via the interaction of a client. You can also test connectivity in both. (Anytime you have a client and a server there has to be connectivity between them or the system would be less than useful so far as I can see.) In the Web you are looking at HTTP protocols and perhaps FTP depending upon your site and if your server is configured for FTP connections as well as general TCP/IP concerns. In a traditional client/server you may be looking at sockets, Telnet, NNTP, etc.

----------------------------------------------------------------------1. What is SQA Activities? a. Metric calculation b. Involved in Entire Software development process c. Monitoring and improving process d. Hence problems are found and dealt with it e. It's oriented to prevention 1.prepare an SQA plan for a project 2.participates in the developed of the project's software process description 3.Audit designated software work . 4.Ensure that deviation in software work 5.Records any non compliance and reports to senior management. ----------------------------------------------------------------------2. How can we perform testing without expected results? 3. Which of the following statements about regression testing are true? a. Regression Testing must consist of a fixed set of tests to create a baseline b. Regression Testing should be used to detect defects in new features c. Regression Testing can be run on every build d. Regression Testing should be targeted to areas of high risk and known code change e. Regression Testing, when automated, is highly effective in preventing defects ----------------------------------------------------------------------4. How do you conduct boundary analyst testing for okpushbutton 1. Proper URL of Window is opening or not 2. user interface testing Yeah you are correct there is no boundary value analysis for "OK" button. but we can do Error Guessing approach like 1. Clicking the OK button more than once...twice thrice ten times check what happens 2. Use Tab & set focus the Ok Button, (If you cant use tab, ask DEV to code it such a way that he can write set focus on form load some sort like that) & a. click Enter button. b. Use Space button. 3. Try using Alt+"O" ----------------------------------------------------------------------5. What is an exit and entry criteria in a Test Plan ? 6. To whom you send test deliverables? Client/customer

----------------------------------------------------------------------7. What is configuration Management? The traditional software configuration management (SCM) process is looked upon as the best solution to handling changes in software projects ----------------------------------------------------------------------8. Who writes the Business requirements? What you do when you have the BRD? 9. What we normally check for in the Database Testing? 10. What is walk through and inspection? 11. What are the key elements for creating test plan? 12. How do you ensure the quality of the product? 13. What is the job of Quality assurance engineer? Difference between the testing & Quality Assurance job. 14. Can any one send information regarding manual testing. I know just how to use winrunner load runner tool with sample flight reservation application. can any one send me the information how to test web logic and web sphere. 15. What are the demerits of winrunner? 16. How you used white box and block box technologies in your application? 17. What is the role of QA in a project development? ----------------------------------------------------------------------18. How can u test the white page ? You can check whether the dimensions of the paper and quality of the paper is from the requirements document ---------------------------------------------------------------------19. How do you scope, organize, and execute a test project? 20. What is the role of QA in a company that produces software? 21. Describe to me when you would consider employing a failure mode and defect analysis? 22. In general, how do you see automation fitting into the overall process of testing? 23. How do you decide when you have tested enough? 24. Describe to the basic elements you put in a defect report? ----------------------------------------------------------------------25. What is use case? What is the difference between test cases and use cases? Use cases are means of capturing functional specifications. Use case diagrams explains you how the business flow is. To be more specific it explains you the interaction between the actor and the system. 26. What is the importance of a requirements traceability in a product testing? 27. If the actual result doesnt match with expected result in this situation what should we do? 28. Explain about Metrics and types of metrics like schedule variance , effort variance? 29. What is the difference between functional testing & black box testing? 30. What is heuristic checklist used in Unit Testing? 31. What is the difference between System Testing,Integration Testing & System Integration Testing? 32. How to calculate the estimate for test case design and review?

33. What is Requirements Traceability ? What is the purpose of it ? Explain types of traceability matrices ? 34. What are the contents of Risk management Plan? Have you ever prepared a Risk Management Plan ? 35. What metrics used to measure the size of the software? ----------------------------------------------------------------------1. What is diff. between CMMI and CMM levels? A: - CMM: - this is applicable only for software industry. KPAs -18 CMMI: - This is applicable for software, out sourcing and all other industries. KPA - 25 ----------------------------------------------------------------------2. What is the scalability testing? 1. Scalability is nothing but how many users that the application should handle 2. Scalability is nothing but maximum no of users that the system can handle 3. Scalability testing is a subtype of performance test where performance requirements for response time, throughput, and/or utilization are tested as load on the SUT is increased over time. 4. As a part of scalability testing we test the expandability of the application. In scalability we test 1.Applicaation scalability, 2.Performance scalability Application scalability: to test the possibility of implementing new features in the system or updating the existing features of the system. With the help of design doc we do this testing Performance scalability: To test how the s/w perform when it is subjected to varying loads to measure and to evaluate the Performance behavior and the ability for the s/w to continue to function properly under different workloads. > To check the comfort level of an application in terms of user load. And user experience and system tolerance levels > The point within an application that when subjected to increasing workload begin to degrade in terms of end user experience and system tolerance > Response time Execution time System resource utilization Network delays ? stress testing ----------------------------------------------------------------------3. What is status of defect when you are performing regression testing? A:-Fixed Status ----------------------------------------------------------------------4. What is the first test in software testing process?

A) Monkey testing B) Unit Testing c) Static analysis d) None of the above A: - Unit testing is the first test in testing process, though it is done by developers after the completion of coding it is correct one. ----------------------------------------------------------------------4. When will the testing starts? a) Once the requirements are Complete b) In requirement phase? A: - Once the requirements are complete. This is Static testing. Here, u r supposed to read the documents (requirements) and it is quite a common issue in S/w industry that many requirements contradict with other requirements. These are also can be reported as bugs. However, they will be reviewed before reporting them as bugs (defects). ----------------------------------------------------------------------5. What is the part of QA and QC in refinement v model? A: V model is a kind of SDLC. QC (Quality Control) team tests the developed product for quality. It deals only with product, both in static and dynamic testing. QA (Quality Assurance) team works on the process and manages for better quality in the process. It deals with (reviews) everything right from collecting requirements to delivery. ----------------------------------------------------------------------6. What are the bugs we cannot find in black box? A: If there r any bugs in security settings of the pages or any other internal mistake made in coding cannot be found in black box testing. ----------------------------------------------------------------------7. What are Microsoft 6 rules? A: As far as my knowledge these rules are used at user Interface test. These are also called Microsoft windows standards. They are . GUI objects are aligned in windows All defined text is visible on a GUI object Labels on GUI objects are capitalized Each label includes an underlined letter (mnemonics) Each window includes an OK button, a Cancel button, and a System menu ----------------------------------------------------------------------8. What are the steps to test any software through automation tools? A: First, you need to segregate the test cases that can be automated. Then, prepare test data as per the requirements of those test cases. Write reusable functions which are used frequently in those test cases. Now, prepare the test scripts using those reusable functions and by applying loops and conditions where ever necessary. However, Automation framework that is followed in the organization

should strictly follow through out the process. ----------------------------------------------------------------------9. What is Defect removable efficiency? A: - The DRE is the percentage of defects that have been removed during an activity, computed with the equation below. The DRE can also be computed for each software development activity and plotted on a bar graph to show the relative defect removal efficiencies for each activity. Or, the DRE may be computed for a specific task or technique (e.g. design inspection, code walkthrough, unit test, 6 month operation, etc.) Number Defects Removed DRE = * 100 Number Defects at Start of Process DRE=A/A+B = 0.8 A = Testing Team (Defects by testing team) B = customer ( customer ) If dre