1. The top management was feeling that when there are any changes in the technology being used, development schedules etc, it was a waste of time to update the Test Plan. Instead, they were emphasizing that you should put your time into testing than working on the test plan. Your Project Manager asked for your opinion. You have argued that Test Plan is very important and you need to update your test plan from time to time. It’s not a waste of time and testing activities would be more effective when you have your plan clear. Use some metrics. How you would support your argument to have the test plan consistently updated all the time.
2. The QAI is starting a project to put the CSTE certification online. They will use an automated process for recording candidate information, scheduling candidates for exams, keeping track of results and sending out certificates. Write a brief test plan for this new project.
3. The project had a very high cost of testing. After going in detail, someone found out that the testers are spending their time on software that doesn’t have too many defects. How will you make sure that this is correct?
4. What are the disadvantages of overtesting?
5. What happens to the test plan if the application has a functionality not mentioned in the requirements?
6. You are given two scenarios to test. Scenario 1 has only one terminal for entry and processing whereas scenario 2 has several terminals where the data input can be made. Assuming that the processing work is the same, what would be the specific tests that you would perform in Scenario 2, which you would not carry on Scenario 1?
7. Your customer does not have experience in writing Acceptance Test Plan. How will you do that in coordination with customer? What will be the contents of Acceptance Test Plan?
8. How do you know when to stop testing?
9. What can you do if the requirements are changing continuously?
10. What is the need for Test Planning?
11. What are the various status reports you will generate to Developers and Senior Management?
12. Define and explain any three aspects of code review?
13. Why do you need test planning?
14. Explain 5 risks in an e-commerce project. Identify the personnel that must be involved in the risk analysis of a project and describe their duties. How will you prioritize the risks?
15. What are the various status reports that you need generate for Developers and Senior Management?
16. You have been asked to design a Defect Tracking system. Think about the fields you would specify in the defect tracking system?
17. Write a sample Test Policy?
18. Explain the various types of testing after arranging them in a chronological order?
19. Explain what test tools you will need for client-server testing and why?
20. Explain what test tools you will need for Web app testing and why?
21. Explain pros and cons of testing done development team and testing by an independent team?
22. Differentiate Validation and Verification?
23. Explain Stress, Load and Performance testing?
24. Describe automated capture/playback tools and list their benefits?
25. How can software QA processes be implemented without stifling productivity?
26. How is testing affected by object-oriented designs?
27. What is extreme programming and what does it have to do with testing?
28. Write a test transaction for a scenario where 6.2% of tax deduction for the first $62,000 of income has to be done?
29. What would be the Test Objective for Unit Testing? What are the quality measurements to assure that unit testing is complete?
30. Prepare a checklist for the developers on Unit Testing before the application comes to testing department.
31. Draw a pictorial diagram of a report you would create for developers to determine project status.
32. Draw a pictorial diagram of a report you would create for users and management to determine project status.
33. What 3 tools would you purchase for your company for use in testing? Justify the need?
34. Put the following concepts, put them in order, and provide a brief description of each:
* system testing
* acceptance testing
* unit testing
* integration testing
* benefits realization testing
35. What are two primary goals of testing?
36. If your company is going to conduct a review meeting, who should be on the review committe and why?
37. Write any three attributes which will impact the Testing Process?
38. What activity is done in Acceptance Testing, which is not done in System testing?
39. You are a tester for testing a large system. The system data model is very large with many attributes and there are a lot of inter-dependencies within the fields. What steps would you use to test the system and also what are the effects of the steps you have taken on the test plan?
40. Explain and provide examples for the following black box techniques?
* Boundary Value testing
* Equivalence testing
* Error Guessing
41. What are the product standards for?
* Test Plan
* Test Script and Test Report
42. You are the test manager starting on system testing. The development team says that due to a change in the requirements, they will be able to deliver the system for SQA 5 days past the deadline. You cannot change the resources (work hours, days, or test tools). What steps will you take to be able to finish the testing in time?
43. Your company is about to roll out an e-commerce application. It’s not possible to test the application on all types of browsers on all platforms and operating systems. What steps would you take in the testing environment to reduce the business risks and commercial risks?
44. In your organization, testers are delivering code for system testing without performing unit testing. Give an example of test policy:
* Policy statement
* Methodology
* Measurement
45. Testers in your organization are performing tests on the deliverables even after significant defects have been found. This has resulted in unnecessary testing of little value, because re-testing needs to be done after defects have been rectified. You are going to update the test plan with recommendations on when to halt testing. Wwhat recommendations are you going to make?
46. How do you measure:
* Test Effectiveness
* Test Efficiency
47. You found out the senior testers are making more mistakes then junior testers; you need to communicate this aspect to the senior tester. Also, you don’t want to lose this tester. How should one go about constructive criticism?
48. You are assigned to be the test lead for a new program that will automate take-offs and landings at an airport. How would you write a test strategy for this new program?
Showing posts with label Qa Testing Interview Questions. Show all posts
Showing posts with label Qa Testing Interview Questions. Show all posts
Sunday, April 5, 2009
Microsoft software development engineer in test (SDET) interview questions
1. How would you deal with changes being made a week or so before the ship date?
2. How would you deal with a bug that no one wants to fix? Both the SDE and his lead have said they won’t fix it.
3. Write a function that counts the number of primes in the range [1-N]. Write the test cases for this function.
4. Given a MAKEFILE (yeah a makefile), design the data structure that a parser would create and then write code that iterates over that data structure
executing commands if needed.
5. Write a function that inserts an integer into a linked list in ascending order. Write the test cases for this function.
6. Test the save dialog in Notepad. (This was the question I enjoyed the most).
7. Write the InStr function. Write the test cases for this function.
8. Write a function that will return the number of days in a month (not using System.DateTime).
9. You have 3 jars. Each jar has a label on it: white, black, or white&black. You have 3 sets of marbles: white, black, and
white&black. One set is stored in one jar. The labels on the jars are guaranteed to be incorrect (i.e. white will not contain white). Which jar would you choose from to give you the best chances of identifying the which set of marbles in is in which jar.
10. Why do you want to work for Microsoft?
11. Write the test cases for a vending machine. (Those were the questions I was asked. I had a lot of discussions about how to handle situations. Such as a tester is focused on one part of an SDK. During triage it was determined that that portion of the SDK was not on the critical path, and the tester was needed elsewhere. But the tester continued to test that portion because it is his baby. How would you get him to stop testing that portion and work on what needs to be worked on? Other situations came up like arranging tests into the different testing buckets (functional, stress, perf, etc.).)
2. How would you deal with a bug that no one wants to fix? Both the SDE and his lead have said they won’t fix it.
3. Write a function that counts the number of primes in the range [1-N]. Write the test cases for this function.
4. Given a MAKEFILE (yeah a makefile), design the data structure that a parser would create and then write code that iterates over that data structure
executing commands if needed.
5. Write a function that inserts an integer into a linked list in ascending order. Write the test cases for this function.
6. Test the save dialog in Notepad. (This was the question I enjoyed the most).
7. Write the InStr function. Write the test cases for this function.
8. Write a function that will return the number of days in a month (not using System.DateTime).
9. You have 3 jars. Each jar has a label on it: white, black, or white&black. You have 3 sets of marbles: white, black, and
white&black. One set is stored in one jar. The labels on the jars are guaranteed to be incorrect (i.e. white will not contain white). Which jar would you choose from to give you the best chances of identifying the which set of marbles in is in which jar.
10. Why do you want to work for Microsoft?
11. Write the test cases for a vending machine. (Those were the questions I was asked. I had a lot of discussions about how to handle situations. Such as a tester is focused on one part of an SDK. During triage it was determined that that portion of the SDK was not on the critical path, and the tester was needed elsewhere. But the tester continued to test that portion because it is his baby. How would you get him to stop testing that portion and work on what needs to be worked on? Other situations came up like arranging tests into the different testing buckets (functional, stress, perf, etc.).)
SQA and testing frequently asked definitions
Black box testing
not based on any knowledge of internal design or code. Tests are based on requirements and functionality.
White box testing
based on knowledge of the internal logic of an application’s code. Tests are based on coverage of code statements, branches, paths, conditions.
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.
Incremental integration testing
continuous testing of an application as new functionality is added; requires that various aspects of an application’s 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.
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 network, etc. This type of testing is especially relevant to client/server and distributed systems.
Functional testing
black-box type testing geared to functional requirements of an application; this type of testing should be done by testers. This doesn’t mean that the programmers shouldn’t check that their code works before releasing it (which of course applies to any stage of testing.)
System testing
black box type testing that is based on overall requirement specifications; covers all combined parts of a system.
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 a database, using network communications, or interacting with other hardware, applications, or systems if appropriate.
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 5 minutes, bogging down systems to a crawl, or destroying databases, the software may not be in a ’sane’ enough condition to warrant further testing in its current state.
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.
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.
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.
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 repetition of certain actions or inputs, input of large numerical values, large complex queries to a database system, etc.
Performance testing
term often used interchangeably with ’stress’ and ‘load’ testing. Ideally ‘performance’ testing (and any other ‘type’ of testing) is defined in requirements documentation or QA or Test Plans.
Usability testing
testing for ‘user-friendliness’. 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.
Install/uninstall testing
testing of full, partial, or upgrade install/uninstall processes.
Recovery testing
testing how well a system recovers from crashes, hardware failures, or other catastrophic problems.
Security testing
testing how well the system protects against unauthorized internal or external access, willful damage, etc; may require sophisticated testing techniques.
Compatibility testing
testing how well software performs in a particular hardware/software/operating system/network/etc. environment.
Exploratory testing
often taken to mean a creative, informal software test that is not based on formal test plans or test cases; testers may be learning the software as they test it.
Ad-hoc testing
similar to exploratory testing, but often taken to mean that the testers have significant understanding of the software before testing it.
User acceptance testing
determining if software is satisfactory to an end-user or customer.
Comparison testing
comparing software weaknesses and strengths to competing products.
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.
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 end-users or others, not by programmers or testers.
Mutation testing
a 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.
not based on any knowledge of internal design or code. Tests are based on requirements and functionality.
White box testing
based on knowledge of the internal logic of an application’s code. Tests are based on coverage of code statements, branches, paths, conditions.
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.
Incremental integration testing
continuous testing of an application as new functionality is added; requires that various aspects of an application’s 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.
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 network, etc. This type of testing is especially relevant to client/server and distributed systems.
Functional testing
black-box type testing geared to functional requirements of an application; this type of testing should be done by testers. This doesn’t mean that the programmers shouldn’t check that their code works before releasing it (which of course applies to any stage of testing.)
System testing
black box type testing that is based on overall requirement specifications; covers all combined parts of a system.
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 a database, using network communications, or interacting with other hardware, applications, or systems if appropriate.
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 5 minutes, bogging down systems to a crawl, or destroying databases, the software may not be in a ’sane’ enough condition to warrant further testing in its current state.
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.
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.
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.
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 repetition of certain actions or inputs, input of large numerical values, large complex queries to a database system, etc.
Performance testing
term often used interchangeably with ’stress’ and ‘load’ testing. Ideally ‘performance’ testing (and any other ‘type’ of testing) is defined in requirements documentation or QA or Test Plans.
Usability testing
testing for ‘user-friendliness’. 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.
Install/uninstall testing
testing of full, partial, or upgrade install/uninstall processes.
Recovery testing
testing how well a system recovers from crashes, hardware failures, or other catastrophic problems.
Security testing
testing how well the system protects against unauthorized internal or external access, willful damage, etc; may require sophisticated testing techniques.
Compatibility testing
testing how well software performs in a particular hardware/software/operating system/network/etc. environment.
Exploratory testing
often taken to mean a creative, informal software test that is not based on formal test plans or test cases; testers may be learning the software as they test it.
Ad-hoc testing
similar to exploratory testing, but often taken to mean that the testers have significant understanding of the software before testing it.
User acceptance testing
determining if software is satisfactory to an end-user or customer.
Comparison testing
comparing software weaknesses and strengths to competing products.
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.
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 end-users or others, not by programmers or testers.
Mutation testing
a 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.
Load testing interview questions
1. What criteria would you use to select Web transactions for load testing?
2. Why are virtual users created?
3. Why is it recommended to add verification checks to your all your scenarios?
4. What’s the scenario, where you would want to parameterize a text verification check?
5. Why do you need to parameterize fields in your virtual user script?
6. What are the cases why parameterization is necessary when load testing the Web server and the database server?
7. How can data caching have a negative effect on load testing results?
8. What is usually a good indicator that your virtual user script has dynamic data, which is dependent on the parameterized fields?
9. What are the benefits of creating multiple actions within any virtual user script?
10. What is a Load Test Results Summary Report?
2. Why are virtual users created?
3. Why is it recommended to add verification checks to your all your scenarios?
4. What’s the scenario, where you would want to parameterize a text verification check?
5. Why do you need to parameterize fields in your virtual user script?
6. What are the cases why parameterization is necessary when load testing the Web server and the database server?
7. How can data caching have a negative effect on load testing results?
8. What is usually a good indicator that your virtual user script has dynamic data, which is dependent on the parameterized fields?
9. What are the benefits of creating multiple actions within any virtual user script?
10. What is a Load Test Results Summary Report?
QTP interview questions and answers 1
1. • What does it mean when a check point is in red color? what do u do? - A red color indicates failure. Here we analyze the cause for failure whether it is a Script Issue or Environment Issue or a Application issue.
2. • What is Object Spy in QTP? - Using the Object Spy, you can view the properties of any object in an open application. You use the Object Spy pointer to point to an object. The Object Spy displays the selected object’s hierarchy tree and its properties and values in the Properties tab of the Object Spy dialog box.
3. • What is the file extension of the code file & object repository file in QTP? - Code file extension is.vbs and object repository is.tsr
4. • Explain the concept of object repository & how QTP recognizes objects? - Object Repository: displays a tree of all objects in the current component or in the current action or entire test (depending on the object repository mode you selected). We can view or modify the test object description of any test object in the repository or to add new objects to the repository. Quicktest learns the default property values and determines in which test object class it fits. If it is not enough it adds assistive properties, one by one to the description until it has compiled the unique description. If no assistive properties are available, then it adds a special Ordinal identifier such as objects location on the page or in the source code.
5. • What are the properties you would use for identifying a browser & page when using descriptive programming? - Name would be another property apart from title that we can use.
6. • Give me an example where you have used a COM interface in your QTP project? - com interface appears in the scenario of front end and back end. for eg:if you r using oracle as back end and front end as VB or any language then for better compatibility we will go for an interface. of which COM will be one among those interfaces. Create object creates handle to the instance of the specified object so that we program can use the methods on the specified object. It is used for implementing Automation(as defined by Microsoft).
7. • Explain in brief about the QTP Automation Object Model. - Essentially all configuration and run functionality provided via the Quick Test interface is in some way represented in the Quick Test automation object model via objects, methods, and properties. Although a one-on-one comparison cannot always be made, most dialog boxes in Quick Test have a corresponding automation object, most options in dialog boxes can be set and/or retrieved using the corresponding object property, and most menu commands and other operations have corresponding automation methods. You can use the objects, methods, and properties exposed by the Quick Test automation object model, along with standard programming elements such as loops and conditional statements to design your program.
2. • What is Object Spy in QTP? - Using the Object Spy, you can view the properties of any object in an open application. You use the Object Spy pointer to point to an object. The Object Spy displays the selected object’s hierarchy tree and its properties and values in the Properties tab of the Object Spy dialog box.
3. • What is the file extension of the code file & object repository file in QTP? - Code file extension is.vbs and object repository is.tsr
4. • Explain the concept of object repository & how QTP recognizes objects? - Object Repository: displays a tree of all objects in the current component or in the current action or entire test (depending on the object repository mode you selected). We can view or modify the test object description of any test object in the repository or to add new objects to the repository. Quicktest learns the default property values and determines in which test object class it fits. If it is not enough it adds assistive properties, one by one to the description until it has compiled the unique description. If no assistive properties are available, then it adds a special Ordinal identifier such as objects location on the page or in the source code.
5. • What are the properties you would use for identifying a browser & page when using descriptive programming? - Name would be another property apart from title that we can use.
6. • Give me an example where you have used a COM interface in your QTP project? - com interface appears in the scenario of front end and back end. for eg:if you r using oracle as back end and front end as VB or any language then for better compatibility we will go for an interface. of which COM will be one among those interfaces. Create object creates handle to the instance of the specified object so that we program can use the methods on the specified object. It is used for implementing Automation(as defined by Microsoft).
7. • Explain in brief about the QTP Automation Object Model. - Essentially all configuration and run functionality provided via the Quick Test interface is in some way represented in the Quick Test automation object model via objects, methods, and properties. Although a one-on-one comparison cannot always be made, most dialog boxes in Quick Test have a corresponding automation object, most options in dialog boxes can be set and/or retrieved using the corresponding object property, and most menu commands and other operations have corresponding automation methods. You can use the objects, methods, and properties exposed by the Quick Test automation object model, along with standard programming elements such as loops and conditional statements to design your program.
QTP interview questions and answers
1. What are the Features & Benefits of Quick Test Pro (QTP 8.0)? - Operates stand-alone, or integrated into Mercury Business Process Testing and Mercury Quality Center. Introduces next-generation zero-configuration Keyword Driven testing technology in Quick Test Professional 8.0 allowing for fast test creation, easier maintenance, and more powerful data-driving capability. Identifies objects with Unique Smart Object Recognition, even if they change from build to build, enabling reliable unattended script execution. Collapses test documentation and test creation to a single step with Auto-documentation technology. Enables thorough validation of applications through a full complement of checkpoints.
2. How to handle the exceptions using recovery scenario manager in QTP? - There are 4 trigger events during which a recovery scenario should be activated. A pop up window appears in an opened application during the test run: A property of an object changes its state or value, A step in the test does not run successfully, An open application fails during the test run, These triggers are considered as exceptions.You can instruct QTP to recover unexpected events or errors that occurred in your testing environment during test run. Recovery scenario manager provides a wizard that guides you through the defining recovery scenario. Recovery scenario has three steps: 1. Triggered Events 2. Recovery steps 3. Post Recovery Test-Run
3. What is the use of Text output value in QTP? - Output values enable to view the values that the application talks during run time. When parameterized, the values change for each iteration. Thus by creating output values, we can capture the values that the application takes for each run and output them to the data table.
4. How to use the Object spy in QTP 8.0 version? - There are two ways to Spy the objects in QTP: 1) Thru file toolbar, In the File Toolbar click on the last toolbar button (an icon showing a person with hat). 2) True Object repository Dialog, In Object repository dialog click on the button object spy. In the Object spy Dialog click on the button showing hand symbol. The pointer now changes in to a hand symbol and we have to point out the object to spy the state of the object if at all the object is not visible. or window is minimized then, hold the Ctrl button and activate the required window to and release the Ctrl button.
5. How Does Run time data (Parameterization) is handled in QTP? - You can then enter test data into the Data Table, an integrated spreadsheet with the full functionality of Excel, to manipulate data sets and create multiple test iterations, without programming, to expand test case coverage. Data can be typed in or imported from databases, spreadsheets, or text files.
6. What is keyword view and Expert view in QTP? - Quick Test’s Keyword Driven approach, test automation experts have full access to the underlying test and object properties, via an integrated scripting and debugging environment that is round-trip synchronized with the Keyword View. Advanced testers can view and edit their tests in the Expert View, which reveals the underlying industry-standard VBScript that Quick Test Professional automatically generates. Any changes made in the Expert View are automatically synchronized with the Keyword View.
7. Explain about the Test Fusion Report of QTP? - Once a tester has run a test, a Test Fusion report displays all aspects of the test run: a high-level results overview, an expandable Tree View of the test specifying exactly where application failures occurred, the test data used, application screen shots for every step that highlight any discrepancies, and detailed explanations of each checkpoint pass and failure. By combining Test Fusion reports with Quick Test Professional, you can share reports across an entire QA and development team.
8. Which environments does QTP support? - Quick Test Professional supports functional testing of all enterprise environments, including Windows, Web,..NET, Java/J2EE, SAP, Siebel, Oracle, PeopleSoft, Visual Basic, ActiveX, mainframe terminal emulators, and Web services.
9. What is QTP? - Quick Test is a graphical interface record-playback automation tool. It is able to work with any web, java or windows client application. Quick Test enables you to test standard web objects and ActiveX controls. In addition to these environments, Quick Test Professional also enables you to test Java applets and applications and multimedia objects on Applications as well as standard Windows applications, Visual Basic 6 applications and.NET framework applications
10. Explain QTP Testing process? - Quick Test testing process consists of 6 main phases:
11. Create your test plan - Prior to automating there should be a detailed description of the test including the exact steps to follow, data to be input, and all items to be verified by the test. The verification information should include both data validations and existence or state verifications of objects in the application.
12. Recording a session on your application - As you navigate through your application, Quick Test graphically displays each step you perform in the form of a collapsible icon-based test tree. A step is any user action that causes or makes a change in your site, such as clicking a link or image, or entering data in a form.
13. Enhancing your test - Inserting checkpoints into your test lets you search for a specific value of a page, object or text string, which helps you identify whether or not your application is functioning correctly. NOTE: Checkpoints can be added to a test as you record it or after the fact via the Active Screen. It is much easier and faster to add the checkpoints during the recording process. Broadening the scope of your test by replacing fixed values with parameters lets you check how your application performs the same operations with multiple sets of data. Adding logic and conditional statements to your test enables you to add sophisticated checks to your test.
14. Debugging your test - If changes were made to the script, you need to debug it to check that it operates smoothly and without interruption.
15. Running your test on a new version of your application - You run a test to check the behavior of your application. While running, Quick Test connects to your application and performs each step in your test.
16. Analyzing the test results - You examine the test results to pinpoint defects in your application.
17. Reporting defects - As you encounter failures in the application when analyzing test results, you will create defect reports in Defect Reporting Tool.
18. Explain the QTP Tool interface. - It contains the following key elements: Title bar, displaying the name of the currently open test, Menu bar, displaying menus of Quick Test commands, File toolbar, containing buttons to assist you in managing tests, Test toolbar, containing buttons used while creating and maintaining tests, Debug toolbar, containing buttons used while debugging tests. Note: The Debug toolbar is not displayed when you open Quick Test for the first time. You can display the Debug toolbar by choosing View — Toolbars — Debug. Action toolbar, containing buttons and a list of actions, enabling you to view the details of an individual action or the entire test flow. Note: The Action toolbar is not displayed when you open Quick Test for the first time. You can display the Action toolbar by choosing View — Toolbars — Action. If you insert a reusable or external action in a test, the Action toolbar is displayed automatically. Test pane, containing two tabs to view your test-the Tree View and the Expert View ,Test Details pane, containing the Active Screen. Data Table, containing two tabs, Global and Action, to assist you in parameterizing your test. Debug Viewer pane, containing three tabs to assist you in debugging your test-Watch Expressions, Variables, and Command. (The Debug Viewer pane can be opened only when a test run pauses at a breakpoint.) Status bar, displaying the status of the test
19. How does QTP recognize Objects in AUT? - Quick Test stores the definitions for application objects in a file called the Object Repository. As you record your test, Quick Test will add an entry for each item you interact with. Each Object Repository entry will be identified by a logical name (determined automatically by Quick Test), and will contain a set of properties (type, name, etc) that uniquely identify each object. Each line in the Quick Test script will contain a reference to the object that you interacted with, a call to the appropriate method (set, click, check) and any parameters for that method (such as the value for a call to the set method). The references to objects in the script will all be identified by the logical name, rather than any physical, descriptive properties.
20. What are the types of Object Repositories in QTP? - Quick Test has two types of object repositories for storing object information: shared object repositories and action object repositories. You can choose which type of object repository you want to use as the default type for new tests, and you can change the default as necessary for each new test. The object repository per-action mode is the default setting. In this mode, Quick Test automatically creates an object repository file for each action in your test so that you can create and run tests without creating, choosing, or modifying object repository files. However, if you do modify values in an action object repository, your changes do not have any effect on other actions. Therefore, if the same test object exists in more than one action and you modify an object’s property values in one action, you may need to make the same change in every action (and any test) containing the object.
21. Explain the check points in QTP? - A checkpoint verifies that expected information is displayed in an Application while the test is running. You can add eight types of checkpoints to your test for standard web objects using QTP. A page checkpoint checks the characteristics of an Application. A text checkpoint checks that a text string is displayed in the appropriate place on an Application. An object checkpoint (Standard) checks the values of an object on an Application. An image checkpoint checks the values of an image on an Application. A table checkpoint checks information within a table on a Application. An Accessibilityy checkpoint checks the web page for Section 508 compliance. An XML checkpoint checks the contents of individual XML data files or XML documents that are part of your Web application. A database checkpoint checks the contents of databases accessed by your web site
22. In how many ways we can add check points to an application using QTP? - We can add checkpoints while recording the application or we can add after recording is completed using Active screen (Note : To perform the second one The Active screen must be enabled while recording).
23. How does QTP identify objects in the application? - QTP identifies the object in the application by Logical Name and Class.
24. What is Parameterizing Tests? - When you test your application, you may want to check how it performs the same operations with multiple sets of data. For example, suppose you want to check how your application responds to ten separate sets of data. You could record ten separate tests, each with its own set of data. Alternatively, you can create a parameterized test that runs ten times: each time the test runs, it uses a different set of data.
25. What is test object model in QTP? - The test object model is a large set of object types or classes that Quick Test uses to represent the objects in your application. Each test object class has a list of properties that can uniquely identify objects of that class and a set of relevant methods that Quick Test can record for it. A test object is an object that Quick Test creates in the test or component to represent the actual object in your application. Quick Test stores information about the object that will help it identify and check the object during the run session.
26. What is Object Spy in QTP? - Using the Object Spy, you can view the properties of any object in an open application. You use the Object Spy pointer to point to an object. The Object Spy displays the selected object’s hierarchy tree and its properties and values in the Properties tab of the Object Spy dialog box.
27. What is the Diff between Image check-point and Bit map Check point? - Image checkpoints enable you to check the properties of a Web image. You can check an area of a Web page or application as a bitmap. While creating a test or component, you specify the area you want to check by selecting an object. You can check an entire object or any area within an object. Quick Test captures the specified object as a bitmap, and inserts a checkpoint in the test or component. You can also choose to save only the selected area of the object with your test or component in order to save disk Space. For example, suppose you have a Web site that can display a map of a city the user specifies. The map has control keys for zooming. You can record the new map that is displayed after one click on the control key that zooms in the map. Using the bitmap checkpoint, you can check that the map zooms in correctly. You can create bitmap checkpoints for all supported testing environments (as long as the appropriate add-ins are loaded). Note: The results of bitmap checkpoints may be affected by factors such as operating system, screen resolution, and color settings.
28. How many ways we can parameterize data in QTP? - There are four types of parameters: Test, action or component parameters enable you to use values passed from your test or component, or values from other actions in your test. Data Table parameters enable you to create a data-driven test (or action) that runs several times using the data you supply. In each repetition, or iteration, Quick Test uses a different value from the Data Table. Environment variable parameters enable you to use variable values from other sources during the run session. These may be values you supply, or values that Quick Test generates for you based on conditions and options you choose. Random number parameters enable you to insert random numbers as values in your test or component. For example, to check how your application handles small and large ticket orders, you can have Quick Test generate a random number and insert it in a number of tickets edit field.
29. How do u do batch testing in WR & is it possible to do in QTP, if so explain? - Batch Testing in WR is nothing but running the whole test set by selecting Run Test set from the Execution Grid. The same is possible with QTP also. If our test cases are automated then by selecting Run Test set all the test scripts can be executed. In this process the Scripts get executed one by one by keeping all the remaining scripts in Waiting mode.
30. If I give some thousand tests to execute in 2 days what do u do? - Adhoc testing is done. It Covers the least basic functionalities to verify that the system is working fine.
2. How to handle the exceptions using recovery scenario manager in QTP? - There are 4 trigger events during which a recovery scenario should be activated. A pop up window appears in an opened application during the test run: A property of an object changes its state or value, A step in the test does not run successfully, An open application fails during the test run, These triggers are considered as exceptions.You can instruct QTP to recover unexpected events or errors that occurred in your testing environment during test run. Recovery scenario manager provides a wizard that guides you through the defining recovery scenario. Recovery scenario has three steps: 1. Triggered Events 2. Recovery steps 3. Post Recovery Test-Run
3. What is the use of Text output value in QTP? - Output values enable to view the values that the application talks during run time. When parameterized, the values change for each iteration. Thus by creating output values, we can capture the values that the application takes for each run and output them to the data table.
4. How to use the Object spy in QTP 8.0 version? - There are two ways to Spy the objects in QTP: 1) Thru file toolbar, In the File Toolbar click on the last toolbar button (an icon showing a person with hat). 2) True Object repository Dialog, In Object repository dialog click on the button object spy. In the Object spy Dialog click on the button showing hand symbol. The pointer now changes in to a hand symbol and we have to point out the object to spy the state of the object if at all the object is not visible. or window is minimized then, hold the Ctrl button and activate the required window to and release the Ctrl button.
5. How Does Run time data (Parameterization) is handled in QTP? - You can then enter test data into the Data Table, an integrated spreadsheet with the full functionality of Excel, to manipulate data sets and create multiple test iterations, without programming, to expand test case coverage. Data can be typed in or imported from databases, spreadsheets, or text files.
6. What is keyword view and Expert view in QTP? - Quick Test’s Keyword Driven approach, test automation experts have full access to the underlying test and object properties, via an integrated scripting and debugging environment that is round-trip synchronized with the Keyword View. Advanced testers can view and edit their tests in the Expert View, which reveals the underlying industry-standard VBScript that Quick Test Professional automatically generates. Any changes made in the Expert View are automatically synchronized with the Keyword View.
7. Explain about the Test Fusion Report of QTP? - Once a tester has run a test, a Test Fusion report displays all aspects of the test run: a high-level results overview, an expandable Tree View of the test specifying exactly where application failures occurred, the test data used, application screen shots for every step that highlight any discrepancies, and detailed explanations of each checkpoint pass and failure. By combining Test Fusion reports with Quick Test Professional, you can share reports across an entire QA and development team.
8. Which environments does QTP support? - Quick Test Professional supports functional testing of all enterprise environments, including Windows, Web,..NET, Java/J2EE, SAP, Siebel, Oracle, PeopleSoft, Visual Basic, ActiveX, mainframe terminal emulators, and Web services.
9. What is QTP? - Quick Test is a graphical interface record-playback automation tool. It is able to work with any web, java or windows client application. Quick Test enables you to test standard web objects and ActiveX controls. In addition to these environments, Quick Test Professional also enables you to test Java applets and applications and multimedia objects on Applications as well as standard Windows applications, Visual Basic 6 applications and.NET framework applications
10. Explain QTP Testing process? - Quick Test testing process consists of 6 main phases:
11. Create your test plan - Prior to automating there should be a detailed description of the test including the exact steps to follow, data to be input, and all items to be verified by the test. The verification information should include both data validations and existence or state verifications of objects in the application.
12. Recording a session on your application - As you navigate through your application, Quick Test graphically displays each step you perform in the form of a collapsible icon-based test tree. A step is any user action that causes or makes a change in your site, such as clicking a link or image, or entering data in a form.
13. Enhancing your test - Inserting checkpoints into your test lets you search for a specific value of a page, object or text string, which helps you identify whether or not your application is functioning correctly. NOTE: Checkpoints can be added to a test as you record it or after the fact via the Active Screen. It is much easier and faster to add the checkpoints during the recording process. Broadening the scope of your test by replacing fixed values with parameters lets you check how your application performs the same operations with multiple sets of data. Adding logic and conditional statements to your test enables you to add sophisticated checks to your test.
14. Debugging your test - If changes were made to the script, you need to debug it to check that it operates smoothly and without interruption.
15. Running your test on a new version of your application - You run a test to check the behavior of your application. While running, Quick Test connects to your application and performs each step in your test.
16. Analyzing the test results - You examine the test results to pinpoint defects in your application.
17. Reporting defects - As you encounter failures in the application when analyzing test results, you will create defect reports in Defect Reporting Tool.
18. Explain the QTP Tool interface. - It contains the following key elements: Title bar, displaying the name of the currently open test, Menu bar, displaying menus of Quick Test commands, File toolbar, containing buttons to assist you in managing tests, Test toolbar, containing buttons used while creating and maintaining tests, Debug toolbar, containing buttons used while debugging tests. Note: The Debug toolbar is not displayed when you open Quick Test for the first time. You can display the Debug toolbar by choosing View — Toolbars — Debug. Action toolbar, containing buttons and a list of actions, enabling you to view the details of an individual action or the entire test flow. Note: The Action toolbar is not displayed when you open Quick Test for the first time. You can display the Action toolbar by choosing View — Toolbars — Action. If you insert a reusable or external action in a test, the Action toolbar is displayed automatically. Test pane, containing two tabs to view your test-the Tree View and the Expert View ,Test Details pane, containing the Active Screen. Data Table, containing two tabs, Global and Action, to assist you in parameterizing your test. Debug Viewer pane, containing three tabs to assist you in debugging your test-Watch Expressions, Variables, and Command. (The Debug Viewer pane can be opened only when a test run pauses at a breakpoint.) Status bar, displaying the status of the test
19. How does QTP recognize Objects in AUT? - Quick Test stores the definitions for application objects in a file called the Object Repository. As you record your test, Quick Test will add an entry for each item you interact with. Each Object Repository entry will be identified by a logical name (determined automatically by Quick Test), and will contain a set of properties (type, name, etc) that uniquely identify each object. Each line in the Quick Test script will contain a reference to the object that you interacted with, a call to the appropriate method (set, click, check) and any parameters for that method (such as the value for a call to the set method). The references to objects in the script will all be identified by the logical name, rather than any physical, descriptive properties.
20. What are the types of Object Repositories in QTP? - Quick Test has two types of object repositories for storing object information: shared object repositories and action object repositories. You can choose which type of object repository you want to use as the default type for new tests, and you can change the default as necessary for each new test. The object repository per-action mode is the default setting. In this mode, Quick Test automatically creates an object repository file for each action in your test so that you can create and run tests without creating, choosing, or modifying object repository files. However, if you do modify values in an action object repository, your changes do not have any effect on other actions. Therefore, if the same test object exists in more than one action and you modify an object’s property values in one action, you may need to make the same change in every action (and any test) containing the object.
21. Explain the check points in QTP? - A checkpoint verifies that expected information is displayed in an Application while the test is running. You can add eight types of checkpoints to your test for standard web objects using QTP. A page checkpoint checks the characteristics of an Application. A text checkpoint checks that a text string is displayed in the appropriate place on an Application. An object checkpoint (Standard) checks the values of an object on an Application. An image checkpoint checks the values of an image on an Application. A table checkpoint checks information within a table on a Application. An Accessibilityy checkpoint checks the web page for Section 508 compliance. An XML checkpoint checks the contents of individual XML data files or XML documents that are part of your Web application. A database checkpoint checks the contents of databases accessed by your web site
22. In how many ways we can add check points to an application using QTP? - We can add checkpoints while recording the application or we can add after recording is completed using Active screen (Note : To perform the second one The Active screen must be enabled while recording).
23. How does QTP identify objects in the application? - QTP identifies the object in the application by Logical Name and Class.
24. What is Parameterizing Tests? - When you test your application, you may want to check how it performs the same operations with multiple sets of data. For example, suppose you want to check how your application responds to ten separate sets of data. You could record ten separate tests, each with its own set of data. Alternatively, you can create a parameterized test that runs ten times: each time the test runs, it uses a different set of data.
25. What is test object model in QTP? - The test object model is a large set of object types or classes that Quick Test uses to represent the objects in your application. Each test object class has a list of properties that can uniquely identify objects of that class and a set of relevant methods that Quick Test can record for it. A test object is an object that Quick Test creates in the test or component to represent the actual object in your application. Quick Test stores information about the object that will help it identify and check the object during the run session.
26. What is Object Spy in QTP? - Using the Object Spy, you can view the properties of any object in an open application. You use the Object Spy pointer to point to an object. The Object Spy displays the selected object’s hierarchy tree and its properties and values in the Properties tab of the Object Spy dialog box.
27. What is the Diff between Image check-point and Bit map Check point? - Image checkpoints enable you to check the properties of a Web image. You can check an area of a Web page or application as a bitmap. While creating a test or component, you specify the area you want to check by selecting an object. You can check an entire object or any area within an object. Quick Test captures the specified object as a bitmap, and inserts a checkpoint in the test or component. You can also choose to save only the selected area of the object with your test or component in order to save disk Space. For example, suppose you have a Web site that can display a map of a city the user specifies. The map has control keys for zooming. You can record the new map that is displayed after one click on the control key that zooms in the map. Using the bitmap checkpoint, you can check that the map zooms in correctly. You can create bitmap checkpoints for all supported testing environments (as long as the appropriate add-ins are loaded). Note: The results of bitmap checkpoints may be affected by factors such as operating system, screen resolution, and color settings.
28. How many ways we can parameterize data in QTP? - There are four types of parameters: Test, action or component parameters enable you to use values passed from your test or component, or values from other actions in your test. Data Table parameters enable you to create a data-driven test (or action) that runs several times using the data you supply. In each repetition, or iteration, Quick Test uses a different value from the Data Table. Environment variable parameters enable you to use variable values from other sources during the run session. These may be values you supply, or values that Quick Test generates for you based on conditions and options you choose. Random number parameters enable you to insert random numbers as values in your test or component. For example, to check how your application handles small and large ticket orders, you can have Quick Test generate a random number and insert it in a number of tickets edit field.
29. How do u do batch testing in WR & is it possible to do in QTP, if so explain? - Batch Testing in WR is nothing but running the whole test set by selecting Run Test set from the Execution Grid. The same is possible with QTP also. If our test cases are automated then by selecting Run Test set all the test scripts can be executed. In this process the Scripts get executed one by one by keeping all the remaining scripts in Waiting mode.
30. If I give some thousand tests to execute in 2 days what do u do? - Adhoc testing is done. It Covers the least basic functionalities to verify that the system is working fine.
Testing Interview Question 1
1. What is the Difference between Project and Product testing? What difference you have observed while testing the Clint/Server application and web server application
2. What are the differences between interface and integration testing? Are system specification and functional specification the same? What are the differences between system and functional testing?
3. What is Multi Unit testing?
4. What are the different types, methodologies, approaches, methods in software testing
5. What is the difference between test techniques and test methodology?
6. What is meant by test environment,… what is meant by DB installing and configuring and deploying skills?
7. What is logsheet? And what are the components in it?
8. What is Red Box testing? What is Yellow Box testing? What is Grey Box testing?
9. What is business process in software testing?
10. What is the difference between Desktop application testing and Web testing?
11. Find the values of each of the alphabets. N O O N S O O N + M O O N J YOU N E
12. With multiple testers how does one know which test cases are assigned to them? • Folder structure • Test process
13. What kind of things does one need to know before starting an automation project?
14. What is difference between a Test Plan, a Test Strategy, A Test Scenario, and A Test Case? What’s is their order of succession in the STLC?
15. How many functional testing tools are available? What is the easiest scripting language used?
16. Which phase is called as the Blackout or Quite Phase in SDLC?
17. When an application is given for testing, with what initial testing the testing will be started and when are all the different types of testing done following the initial testing?
18. What is difference between test plan and use case?
19. In an application if I enter the delete button it should give an error message “Are you sure you want to delete†but the application gives the message as “Are you sureâ€. Is it a bug? And if it is how would you rate its severity?
20. Who are the three stake holders in testing?
21. What is meant by bucket testing?
22. What is test case analysis?
23. The recruiter asked if I have Experience in Pathways. What is this?
24. What is the difference between GUI testing and black box testing
25. What are the main things we have to keep in mind while writing the test cases? Explain with format by giving an example
26. How we can write functional and integration test cases? Explain with format by giving examples.
27. Explain the water fall model and V- model of software development life cycles with block diagrams.
28. For notepad application can any one write the functional and system test cases?
29. Can you give me the exact answer for Test Bug?
30. What is the difference between Use Case and test case?
31. What is installation shield in testing
32. What is one key element of the test case?
33. What are the management tools we have in testing?
34. Can we write Functional test case based on only BRD or only Use case?
35. What’s main difference between smoke and sanity testing? When are these performed?
36. What Technical Environments have you worked with?
37. Have you ever converted Test Scenarios into Test Cases?
38. What is the ONE key element of ‘test case’?
39. What is the ONE key element of a Test Plan?
40. What is SQA testing? tell us steps of SQA testing
41. How do you promote the concept of phase containment and defect prevention?
42. Which Methodology you follow in your test case?
43. What are the test cases prepared by the testing team
44. During the start of the project how will the company come to an conclusion that tool is required for testing or not?
45. Define Bug Life Cycle? What is Metrics
46. What is a Test procedure?
47. What is the difference between SYSTEM testing and END-TO-END testing?
48. What is Traceability Matrix? Is there any interchangeable term for Traceability Matrix? Are Traceability Matrix and Test Matrix same or Different?
49. What is the difference between an exception and an error?
50. Correct bug tracking process - Reporting, Re-testing, Debugging, …..?
51. What is the difference between bug and defect?
52. How much time is/should be allocated for testing out of total Development time based on industry standards?
53. What are test bugs?
54. Define Quality - bug free, Functionality working or both?
55. What is the purpose of software testing’s - Bug removal, System’s functionality working, quality or all?
56. What is the major difference between Web services & client server environment?
57. Is there any tool to calculate how much time should be allocated for testing out of total development?
58. What is Scalability testing? Which tool is used?
59. Define Reliability?
60. Best to solve defects - requirements, plan, design, code / testing phase?
61. Cost of solving a bug from requirements phase to testing phase - increases slowly, decreases, increases steeply or remains constant?
62. What is scalability testing? What are the phases of the scalability testing?
63. What is the difference between end to end testing and system testing.
64. What kind of things does one need to know before starting an automation project?
65. Have you worked with data pools and what is your opinion on them? Give me an example as to how a script would handle the data pool.
66. What is difference between a Test Plan, a Test Strategy, A Test Scenario, and A Test Case? What’s is their order of succession in the STLC?
67. How many functional testing tools are available? What is the easiest scripting language used?
68. If we found the bug in SRS or FRS, how to categorize that bug?
69. What is the difference between end to end testing and system testing.
70. What is the difference between a defect and an enhancement?
71. Project is completed. Completed means that UAT testing is going. In that situation as a tester what will you do?
2. What are the differences between interface and integration testing? Are system specification and functional specification the same? What are the differences between system and functional testing?
3. What is Multi Unit testing?
4. What are the different types, methodologies, approaches, methods in software testing
5. What is the difference between test techniques and test methodology?
6. What is meant by test environment,… what is meant by DB installing and configuring and deploying skills?
7. What is logsheet? And what are the components in it?
8. What is Red Box testing? What is Yellow Box testing? What is Grey Box testing?
9. What is business process in software testing?
10. What is the difference between Desktop application testing and Web testing?
11. Find the values of each of the alphabets. N O O N S O O N + M O O N J YOU N E
12. With multiple testers how does one know which test cases are assigned to them? • Folder structure • Test process
13. What kind of things does one need to know before starting an automation project?
14. What is difference between a Test Plan, a Test Strategy, A Test Scenario, and A Test Case? What’s is their order of succession in the STLC?
15. How many functional testing tools are available? What is the easiest scripting language used?
16. Which phase is called as the Blackout or Quite Phase in SDLC?
17. When an application is given for testing, with what initial testing the testing will be started and when are all the different types of testing done following the initial testing?
18. What is difference between test plan and use case?
19. In an application if I enter the delete button it should give an error message “Are you sure you want to delete†but the application gives the message as “Are you sureâ€. Is it a bug? And if it is how would you rate its severity?
20. Who are the three stake holders in testing?
21. What is meant by bucket testing?
22. What is test case analysis?
23. The recruiter asked if I have Experience in Pathways. What is this?
24. What is the difference between GUI testing and black box testing
25. What are the main things we have to keep in mind while writing the test cases? Explain with format by giving an example
26. How we can write functional and integration test cases? Explain with format by giving examples.
27. Explain the water fall model and V- model of software development life cycles with block diagrams.
28. For notepad application can any one write the functional and system test cases?
29. Can you give me the exact answer for Test Bug?
30. What is the difference between Use Case and test case?
31. What is installation shield in testing
32. What is one key element of the test case?
33. What are the management tools we have in testing?
34. Can we write Functional test case based on only BRD or only Use case?
35. What’s main difference between smoke and sanity testing? When are these performed?
36. What Technical Environments have you worked with?
37. Have you ever converted Test Scenarios into Test Cases?
38. What is the ONE key element of ‘test case’?
39. What is the ONE key element of a Test Plan?
40. What is SQA testing? tell us steps of SQA testing
41. How do you promote the concept of phase containment and defect prevention?
42. Which Methodology you follow in your test case?
43. What are the test cases prepared by the testing team
44. During the start of the project how will the company come to an conclusion that tool is required for testing or not?
45. Define Bug Life Cycle? What is Metrics
46. What is a Test procedure?
47. What is the difference between SYSTEM testing and END-TO-END testing?
48. What is Traceability Matrix? Is there any interchangeable term for Traceability Matrix? Are Traceability Matrix and Test Matrix same or Different?
49. What is the difference between an exception and an error?
50. Correct bug tracking process - Reporting, Re-testing, Debugging, …..?
51. What is the difference between bug and defect?
52. How much time is/should be allocated for testing out of total Development time based on industry standards?
53. What are test bugs?
54. Define Quality - bug free, Functionality working or both?
55. What is the purpose of software testing’s - Bug removal, System’s functionality working, quality or all?
56. What is the major difference between Web services & client server environment?
57. Is there any tool to calculate how much time should be allocated for testing out of total development?
58. What is Scalability testing? Which tool is used?
59. Define Reliability?
60. Best to solve defects - requirements, plan, design, code / testing phase?
61. Cost of solving a bug from requirements phase to testing phase - increases slowly, decreases, increases steeply or remains constant?
62. What is scalability testing? What are the phases of the scalability testing?
63. What is the difference between end to end testing and system testing.
64. What kind of things does one need to know before starting an automation project?
65. Have you worked with data pools and what is your opinion on them? Give me an example as to how a script would handle the data pool.
66. What is difference between a Test Plan, a Test Strategy, A Test Scenario, and A Test Case? What’s is their order of succession in the STLC?
67. How many functional testing tools are available? What is the easiest scripting language used?
68. If we found the bug in SRS or FRS, how to categorize that bug?
69. What is the difference between end to end testing and system testing.
70. What is the difference between a defect and an enhancement?
71. Project is completed. Completed means that UAT testing is going. In that situation as a tester what will you do?
Wednesday, April 23, 2008
Software Testing Interview Question 11
Q Can you provide me the correct answer for Test Bug?
The idea of testing is to expose defects/Bugs. A defect/BUG is a difference from a desired product characteristic. Two categories of defects/Bugs are- Variance from product specifications- Variance from customer/user anticipation.
Q What is the ONE major factor of 'test case'?
Test case hold the elements like; test case no, test case explanation, expected result, actual result, Status, remark. According to me, the one key element is actual result.
Q Cost of cracking a bug from requirements phase to testing phase - boosts slowly, decreases, increases steeply or remains constant?
Cost of solving a bug from requirements phase to testing phase - increases slowly
Q What is Bug Tracking Process, Reporting, Re-testing and Debugging?
First step : Bug finding
Second Step : Bug Reporting
Third Step : Bug De-bugging(fixing)
Fourth Step : Re verification of the reported bug (Regression)
This is the process of Bug cycle
Q What are the management tools we have in testing?
We have management tools like Test Director, Team rack, Rational Clear Quest, Bug Zilla etc.,
Q What are the test cases prepared by the testing team ?
- Functional Unit Teset cases (FUT), 2. Integration Test cases (IT), 3. System Test cases (ST), 4. User Inerface Test cases, 5. Validations
Q Can we write Functional test case based on only BRD or only Use case?
We can write down the test cases using the BRD, but we may not obtain the full flow information and exact functionality of the business from BRD. According to me, we can start writing the functional test cases using the BRD, but we cannot baseline the test cases on the basis of BRD.
Q In an application if i press the delete button it should give an error message "Are u sure u want to delete" but the application gives the message as "Are u sure". is it a bug? And if it is how you would rate its severity.
Severity should be minor
Q Best to solve defects - requirements, plan, design, code / testing phase?
Best to solve Defect is Requirement Phase
Q During the start of the project how will the company come to an conclusion that tool is required for testing or not?
There are lots of things which will decide the Automation tool at the time of Project Initialization...1.Requirements2.Project Budget3.Project size4.Head counts5.Time
Q Tell difference between GUI Testing and Black box Testing?
GUI testing fall under black box testing, where we are going to make sure whether the alignments of the objects are placed correctly or not.. like look and feel we can also state that this is cosmetic testing
Black box testing is testing the overall functionality of a system without any collision on the internal code of an application. here you are going to carry out the usability, GUI, functionality, validation, security, system, performance and user acceptance testing.
Tuesday, April 22, 2008
Software Testing Interview Question 10
Q. Explain bug life cycle?
A: —
New: When tester reports a defect
Open: When developer admit that it is a bug or if the developer neglect the defect, then the status is updated into “Rejected”
Fixed: When developer make modifications to the code to correct the bug…
Closed/Reopen: When tester tests it again. If the probable result shown up, it is turned into “Closed” and if the problem still exists, it’s “Reopen”
Q. What is deferred status in defect life cycle?
A: — Deferred status means the developer accepted the bug, but it is planned to correct in the next build
Q. What is smoke test?
A; — Testing the application whether it’s performing its fundamental functionality correctly or not, so that the test team can go forward with the application.
Q. Do you use any automation tool for smoke testing?
A: - Absolutely can use.
Q. What is Verification and validation?
A: — Verification is static. No code is executed. Say, analysis of requirements etc. Validation is dynamic. Code is executed with scenarios present in test cases.
Q. Explain test plan and its contents?
A: — Test plan is a document which contains the scope for testing the application and what to be tested, when to be tested and who to test.
Q. Advantages of automation over manual testing?
A: — Time, resource and Money
Q. What is ADhoc testing?
A: — Doing something which is not planned.
Q. What is mean by release notes?
A: — It’s a document released beside the product which give details about the product. It also contains about the bugs that are in deferred status.
Q. Scalability testing comes under in which tool?
A: — Scalability testing comes under performance testing. Load testing, scalability testing both are same.
Q. What is the difference between Bug and Defect?
A: — Bug: Difference from the expected result.
Defect: Problem in algorithm leads to failure.
A Mistake in code is called Error.
Due to Error in coding, test engineers are getting mismatches in application is called defect.
If defect accepted by development team to solve is called Bug.
Q. What is hot fix?
A: — A hot fix is a solitary, collective package that contains one or more files that are used to tackle a problem in a software product. Usually, hot fixes are made to address a exact customer circumstances and may not be spread outside the customer organization.
Bug found at the customer place which has high priority.
Q. What is the difference between functional test cases and compatibility test cases?
A: —In Compatibility we have no Test Cases. Like we are Testing an application in different Hardware and software.
Q. What is Acid Testing??
A: — ACID Means:
ACID testing is related to testing a transaction.
A-Atomicity
C-Consistent
I-Isolation
D-Durable
Mostly this will be done database testing.
Q. What is the main use of set up a traceability matrix?
A: — To Cross confirm the ready test cases and test scripts with user requirements.
To observe the changes, enhance occurred during the development of the project.
Traceability matrix is arranged in order to cross check the test cases planned against each requirement, hence giving an prospect to confirm that all the necessities are covered in testing the application.
Software Testing Interview Questions
Note: Click on Link to open/visit that Page
Software Testing Interview Question
Software Testing Interview Question 1
Software Testing Interview Question 2
Software Testing Interview Question 3
Software Testing Interview Question 4
Software Testing Interview Question 5
Software Testing Interview Question 6
Software Testing Interview Question 7
Software Testing Interview Question 8
Software Testing Interview Question 9
Software Testing Interview Question 10
Software Testing Interview Question 11
Winrunner Interview Question
Winrunner Interview Question
Software Testing Interview Question
Software Testing Interview Question 1
Software Testing Interview Question 2
Software Testing Interview Question 3
Software Testing Interview Question 4
Software Testing Interview Question 5
Software Testing Interview Question 6
Software Testing Interview Question 7
Software Testing Interview Question 8
Software Testing Interview Question 9
Software Testing Interview Question 10
Software Testing Interview Question 11
Winrunner Interview Question
Winrunner Interview Question
Software Testing Interview Questions 9
Q. If we have no SRS, BRS but we have test cases does you execute the test cases blindly or do you follow any other process?
A: — Test case would have detail steps of what the application is made-up to do. SO
1) Functionality of application is acknowledged.
2) In addition you can refer to Backend, I mean glance into the Database. To gain more information of the application
Q. How to execute test case?
A: — There are two ways to execute test case:
1. Manual Runner Tool for manual execution and updating of test status.
2. Automated test case execution by specifying Host name and other automation pertaining details.
33. Difference between re testing and regression testing?
A: — Retesting: –
Re-execution of test cases on same application put up with different input values is retesting.
Regression Testing:
Re-execution of test cases on updated form of build is called regression testing…
Q. What is the difference between bug log and defect tracking?
A; — Bug log is a document which keep the information of the bug where as bug tracking is the process.
Q. Who will change the Bug Status as Differed?
A: — Bug will be in open position while developer is working on it Fixed after developer completes his work if it is not fixed correctly the tester puts it in reopen After fixing the bug properly it is in closed state.
Q. What is smoke testing and user interface testing ?
A: — ST:
Smoke testing is non-exhaustive software testing, as pertaining that the most critical functions of a program work, but not worry with higher details. The term comes to software testing from a similarly basic type of hardware testing.
UIT:
I did a bit or R n D on this…. some says it’s nothing but Usability testing. Testing to find out the simplicity with which a user can learn to work, input, and interpret outputs of a system or component.
Smoke testing is nothing but to make sure whether essential functionality of the build is stable or not?
I.e. if it possesses 70% of the functionality we say build is stable.
User interface testing: We verify all the fields whether they are existing or not as per the format we check spelling graphic font sizes the whole thing in the window present or not|
Q. What is bug, defect, issue and error?
A: — Bug: — Bug is recognized by the tester.
Defect:– Whenever the project is received for the analysis phase ,may be some requirement neglected to get or know most of the time Defect itself come with the project (when it comes).
Issue: — Client site error most of the time.
Error: — When something is happened wrong in the project from the development side i.e. called as the error, most of the time this knows by the developer.
Bug: a fault or defect in a system or machine
Defect: an imperfection in a device or machine;
Issue: An issue is a major problem that will slow down the development of the project and cannot be determined by the project manager and project team without outside help
Error:
Error is the deviation of a measurement, observation, or calculation from the truth
Q. What is the diff b/w functional testing and integration testing?
A: — functional testing is testing the complete functionality of the system or the application whether it is meeting the functional terms
Integration testing means testing the functionality of integrated module when two different modules are integrated for this we use top-down approach and bottom up approach
Q. What sort of testing you make in organization while you do System Testing, give clearly?
A: — Functional testing
User interface testing
Usability testing
Compatibility testing
Model based testing
Error exit testing
User help testing
Security testing
Capacity testing
Performance testing
Sanity testing
Regression testing
Reliability testing
Recovery testing
Installation testing
Maintenance testing
Accessibility testing, including compliance with:
Americans with Disabilities Act of 1990
Section 508 Amendment to the Rehabilitation Act of 1973
Web Accessibility Initiative (WAI) of the World Wide Web
Consortium (W3C)
Q. What is the major use of prepare Traceability matrix and clarify the real time usage?
A: — A traceability matrix is formed by associating necessities with the work products that satisfy them. Tests are linked with the requirements on which they are based and the product tested to assemble the requirement.
A traceability matrix is a statement from the requirements database or repository.
Q. How can you do the following 1) Usability testing 2) scalability Testing
A:–
UT:
Testing the simplicity with which users can learn and use a product.
ST:
It’s a Web Testing allows web site ability development.
PT:
Testing to find out whether the system/software meets the specified portability requirements.
Q. What does you mean by Positive and Negative testing & what is the difference between them. Can anyone explain with an example?
A: — Positive Testing: Testing the application functionality with suitable inputs and confirming that output is right
Negative testing: Testing the application functionality with unacceptable inputs and verifying the output.
Difference is nothing but how the application perform when we enter some unacceptable inputs suppose if it accepts invalid input the application Functionality is wrong
Positive test: testing meant to show that s/w work i.e. with applicable inputs. This is also called as “test to pass’
Negative testing: testing aimed at showing s/w doesn’t work. Which is also know as ‘test to fail” BVA is the best example of -ve testing.
Q. What is change request, how u use it?
A: — Change Request is an attribute or part of Defect Life Cycle.
Now when you as a tester find a defect and report to your DL…he in turn informs the Development Team.
The DT says it’s not a defect it’s an extra implementation or says not part of requirement. Its newscast has to pay.
Here the status in your defect report would be Change Request
I think change request controlled by change request control board (CCB). If any changes required by client after we start the project, it has to come thru that CCB and they have to approve it. CCB got full rights to accept or reject based on the project schedule and cost.
Q. What is risk analysis, what type of risk analysis u did in u r project?
A: — Risk Analysis:
A systematic use of accessible information to decide how frequently specified events and unspecified events may happen and the magnitude of their likely consequences4
Software Testing Interview Questions 8
Q. High severity, low priority bug?
A: — A page is not often accessed, or some activity is executed rarely but that thing outputs some essential Data wrongly, or corrupts the data, this will be a bug of H severity L priority
Q. If project wants to release in 3months what type of Risk analysis you do in Test plan?
A: – Use risk analysis to decide where testing should be focused. Since it’s not often possible to test every possible portion of an software/application, every probable combination of events, every dependency, or everything that could go wrong, risk analysis is suitable to most software development projects. This involve judgment skills, common sense, and experience.
Considerations can include:
• Which functionality is most chief to the project’s intended purpose?
• Which functionality is most visible to the user?
• Which functionality has the largest safety impact?
• Which functionality has the largest financial impact on users?
• Which aspects of the application are most important to the customer?
• Which aspects of the application can be tested early in the development cycle?
• Which parts of the code are most complex, and thus most subject to errors?
• Which parts of the application were developed in rush or panic mode?
• Which aspects of similar/related previous projects caused problems?
• Which aspects of similar/related previous projects had large maintenance expenses?
• Which parts of the requirements and design are unclear or poorly thought out?
• What do the developers think are the highest-risk aspects of the application?
• What kinds of problems would cause the worst publicity?
• What kinds of problems would cause the most customer service complaints?
• What kinds of tests could easily cover multiple functionalities?
• Which tests will have the best high-risk-coverage to time-required ratio
48. Test cases for IE 6.0 ?
A:– Test cases for IE 6.0 i.e Internet Explorer 6.0:—
1)First I go for the Installation part, means that –
Is it working with all versions of Windows ,Netscape or other software(s) in other words we can say that IE must check with all hardware and software parts.
2) Secondly go for the Text Part means that all the Text part appears in regular and smooth manner.
3) Thirdly go for the Images Part means that all the Images come into view in regular and smooth manner.
4) URL must run in a better way.
5) Suppose Some other language used on it then URL take the Other Characters, Other than Normal Characters.
6)Is it working with Cookies frequently or not.
7) Is it in relation to with different script like JScript and VBScript.
8)HTML Code work on that or not.
9) Troubleshooting works or not.
10) All the Tool bars are work with it or not.
11) If Page has Some Links, than how much is the Max and Min Limit for that.
12) Test for Installing Internet Explorer 6 with Norton Protected Recycle Bin enabled.
13) Is it working with the Un-installation Process?
14) Last but not the least test for the Security System for the IE 6.0
Q. Where you involve in testing life cycle, what type of test you perform?
A:– Normally test engineers concerned from entire test life cycle i.e, test plan, test case preparation, execution, reporting. Generally system testing, regression testing, adhoc testing etc.
Q. What is Testing environment in your company, means how testing process start?
A:– testing process is going as follows
Quality assurance unit
Quality assurance manager
Test lead
Test engineer
Q. Who prepares the use cases?
A:– In Any company apart from the small company Business analyst prepares the use cases. But in small company Business analyst prepares along with team lead.
Q. What methods have you used to develop test cases?
A:– Usually test engineers uses 4 types of methodologies
1. Boundary value analysis
2.Equivalence partition
3.Error guessing
4.Cause effect graphing
Q. Why we call it as a regression test nor retest?
A:– If we test whether defect is closed or not i.e Retesting But here we are checking the impact also regression means repeated times
54. Is automated testing better than manual testing. If so, why?
A:– Automated testing and manual testing have there own advantages as well as disadvantages
Advantages: It boost the efficiency of testing process speed in process
reliable
Flexible
Disadvantage’s
Tools should have compatibility with our development or deployment tools need lot of time at first If the necessities are changing endlessly then Automation is not suitable
Manual: If the requirements are changing endlessly Manual is suitable Once the build is stable with manual testing then only we go 4 automation
Disadvantages:
Time Consuming
We can not do some type of testing manually
E.g Performances
Q. What is the exact difference between a product and a project? Give an example?
A:– Project Developed for specific client necessities are defined by client. Product developed for market necessities are defined by company itself by conducting market survey
Example
Project: the shirt which we are interested stitching with tailor as per our specifications is project
Product: Example is “Ready made Shirt” where the particular company will imagine particular measurements they made the product
Mainframes is a product
Product has many mo of versions
but project has fewer versions i.e depends upon change request and enhancements
Q. Define Brain Storming and Cause Effect Graphing? With example.
A: – Brain Storming:
A learning technique involving open group discussion intended to expand the range of available ideas.
OR
A meeting to generate creative ideas. At PEPSI Advertising, daily, weekly and bi-monthly brainstorming sessions are held by various work groups within the firm. Our monthly I-
Power brainstorming meeting is attended by the entire agency staff.
OR
Brainstorming is a highly planned process to help make ideas. It is based on the principle that you cannot generate and calculate ideas at the same time. To use brainstorming, you must first gain agreement from the group to try brainstorming for a fixed interval (eg six minutes).
CEG :
A testing technique that aids in selecting, in a systematic way, a high-yield set of test cases that logically relates causes to effects to produce test cases. It has a beneficial side effect in pointing out incompleteness and ambiguities in specifications.
Q. Actually by using severity u should know which one u need to solve so what is the need of priority?
A:– I guess severity replicate the seriousness of the bug where as priority refers to which bug should rectify first. of course if the severity is high the same case is with priority in normal.
Severity decided by the tester where as priority decided by developers. Which one need to answer first knows through priority not with severity. How serious of the bug knows through severity.
Severity is nothing collision of that bug on the application. Priority is nothing but weight to resolve the bug yeah of course by looking severity we can judge but sometimes high severity bug doesn’t have high priority At the same time High priority bug don’t have high severity. So we need both severity and priority
Q. What do u do if the bug that you bring into being is not accepted by the developer and he is saying its not reproducible. Note: The developer is in the on site location ?
A:– once again we will check that condition with all causes. Then we will attach screen shots with strong reasons. Then we will clarify to the project manager and also clarify to the client when they contact us
Sometimes bug is not reproducible it is because of different environment suppose development team using other environment and you are using different environment at this situation there is chance of bug not reproducing. At this situation please check the environment in the base line documents that is functional documents if the environment which we r using is correct we will raise it as defect We will take screen shots and sends them with test procedure also.
Q. What is the difference between three tier and two tier application?
A:– Client server is a 2-tier application. In this, front end or client is connected to
‘Data base server’ through ‘Data Source Name, front end is the monitoring level.
Web based architecture is a 3-tier application. In this, browser is connected to web server through TCP/IP and web server is connected to Data base server, browser is the monitoring level. In general, Black box testers are concentrating on monitoring level of any type of application.
All the client server applications are 2 tier architectures.
Here in these architecture, all the “Business Logic” is stored in clients and “Data” is stored in Servers. So if user request anything, business logic will b performed at client, and the data is retrieved from Server(DB Server). Here the problem is, if any business logic changes, then we
need to change the logic at each any every client. The best ex: is take a super market, i have branches in the city. At each branch i have clients, so business logic is stored in clients, but the actual data is store in servers.If assume i want to give some discount on some items, so i
need to change the business logic. For this i need to goto each branch and need to change the business logic at each client. This the disadvantage of Client/Server architecture.
So 3-tier architecture came into picture:
Here Business Logic is stored in one Server, and all the clients are dumb terminals. If user requests anything the request first sent to server, the server will bring the data from DB Sever and send it to clients. This is the flow for 3-tier architecture.
Assume for the above. Ex. if i want to give some discount, all my business logic is there in Server. So i need to change at one place, not at each client. This is the main advantage of 3-tier architecture.
Monday, April 21, 2008
Software Testing Interview Questions 7
Q. What is Impact analysis? How to perform impact analysis in the project?
A: — Impact analysis means when we are performing regressing testing at that time we are inspecting that the bug fixes are working correctly, and by fixing these bug other components are working fine as per their requirements are they got disturbed.
Q. How to test a web application by manual testing?
A: — Web Testing
During testing the websites the following scenarios should be considered.
Functionality
Performance
Usability
Server side interface
Client side compatibility
Security
Functionality:
In the functionality testing of the web sites the following should be tested.
Links
Internal links
External links
Mail links
Broken links
Forms
Field validation
Functional chart
Error message for wrong input
Optional and mandatory fields
Database
Testing will be done on the database integrity.
Cookies
Testing will be done on the client system side, on the temporary internet files.
Performance:
Performance testing can be carried out to know the web site’s scalability, or to target the performance in the environment of third party products such as servers and middle ware for potential purchase.
Connection speed:
Tested over various Networks like Dial up, ISDN etc
Load
What is the no. of users per time? How many users website can handle at single time.
Check for peak loads & how system behaves.
Large amount of data accessed by user.
Stress
Continuous load
Performance of memory, cpu, file handling etc.
Usability :
Usability testing is the process by which the human-computer communication characteristics of a system are measured, and flaws are identified for correction. Usability can be defined as the degree to which a given piece of software assists the person sitting at the keyboard to accomplish a task, as different to becoming an additional impediment to such success. The broad goal of usable systems is often assessed using several
Criteria:
Ease of learning
Navigation
Subjective user satisfaction
General appearance
Server side interface:
In web testing the server side interface should be tested.
This is done by confirm that communication is done properly.
Compatibility of server with software, hardware, network and database should be tested.
The client side compatibility is also tested in various platforms, using various browsers etc.
Security:
The main reason for testing the security of an web is to make out potential vulnerabilities and then repair them.
The following types of testing are described in this section:
Network Scanning
Vulnerability Scanning
Password Cracking
Log Review
Integrity Checkers
Virus Detection
Performance Testing
Performance testing is a rigorous usability estimate of a working system under levelheaded conditions to identify usability troubles and to evaluate measures such as success rate, task time and user satisfaction with requirements. The objective of performance testing is not to find bugs, but to do away with bottlenecks and establish a baseline for future regression testing.
To conduct performance testing is to connect in a carefully controlled process of measurement and analysis. Ideally, the software under test is already established sufficient so that this process can carry on smoothly. A clearly defined set of expectations is necessary for meaningful performance testing.
For example, for a Web application, you need to know at least two things:
expected load in terms of concurrent users or HTTP connections
acceptable response time
Load testing:
Load testing is generally defined as the process of exercising the system under test by feeding it the largest tasks it can operate with. Load testing is sometimes called volume testing, or longevity/endurance testing
Examples of volume testing:
testing a word processor by editing a very large document
testing a printer by sending it a very large job
testing a mail server with thousands of users mailboxes
Examples of longevity/endurance testing:
testing a client-server application by running the client in a loop against the server over an extended period of time
Goals of load testing:
Depiction bugs that do not surface in superficial testing, such as memory management bugs, memory leaks, buffer overflows, etc. Make sure that the application meets the performance baseline established during Performance testing. This is done by running regression tests against the application at a specified maximum load.
Although performance testing and load testing can seen parallel, their objectives are different. On one hand, performance testing uses load testing techniques and tools for measurement and benchmarking reason and uses a variety of load levels whereas load testing operates at a predefined load level, the highest load that the system can accept while still functioning correctly.
Stress testing:
Stress testing is a type of testing that is used to find out the constancy of a given system or entity. This is designed to test the software with nonstandard circumstances. Stress testing attempts to find the restrictions at which the system will fail through nonstandard quantity or frequency of inputs.
Stress testing tries to break the system under test by overpowering its resources or by taking resources away from it (in which case it is sometimes called negative testing).
The main idea behind this madness is to make sure that the system fails and recovers benevolently — this quality is known as recoverability.
Stress testing does not break the system but instead it allows monitor how the system reacts to failure. Stress testing observes for the following.
Does it save its state or does it crash suddenly?
Does it just hang and freeze or does it fail gracefully?
Is it able to recover from the last good state on restart?
Compatibility Testing
A Testing to make sure compatibility of an application or Web site with multiple browsers, OS and hardware platforms. Different versions, configurations, display resolutions, and Internet connect speeds all can impact the behavior of the product and introduce costly and embarrassing bugs. We test for compatibility using real test environments.
That is testing how will the system performs in the particular software, hardware or network environment. Compatibility testing can be carry out manually or can be determined by an automated functional. The idea of compatibility testing is to disclose issues related to the product & interaction session test suite.
With other software as well as hardware. The product compatibility is estimated by first identifying the hardware/software/browser components that the product is designed to support. Then a hardware/software/browser matrix is designed that indicates the configurations on which the product will be tested. Then, with input from the client, a testing script is designed that will be sufficient to evaluate compatibility between the product and the hardware/software/browser matrix. Finally, the script is executed against the matrix and any anomalies are investigated to decide exactly where the incompatibility lies.
Some typical compatibility tests include testing your application:
On various client hardware configurations
Using different memory sizes and hard drive space
On various Operating Systems
In different network environments
With different printers and peripherals (i.e. zip drives, USBs, etc.)
62. Which comes first test strategy or test plan?
A:– Test strategy comes first and this is the high level document…. and advance. Testing starts from test strategy and then based on this the test lead set up the
test plan….
Q. As a testers point of view what is the difference between web based application and client server application ?
A:– According to Tester’s Point of view——
1) Web Base Application (WBA)is a 3 tier application ;Browser, Back end and Server.
Client server Application(CSA) is a 2 tier Application ;Front End ,Back end .
2) In the WBA tester test for the Script error like java script error VB script error etc, that shown at the page. In the CSA tester does not test for any script error.
3) Because in the WBA once changes perform return at every machine so tester has less work for test. Whereas in the CSA every time application need to be install hence ,it maybe possible that some machine has some problem for that Hardware testing as well as software testing is needed.
63. What is the significance of doing Regression testing?
A:– To check for the bug fixes. And this fix should not disturb other functionality
To guarantee the newly added functionality or existing modified functionality or developer fixed bug come up with any new bug or affecting any other side effect. this is called regression test and ensure already PASSED TEST CASES would not arise any new bug.
64. What are the diff ways to check a date field in a website?
A:– There are different ways like :–
1) you can check the field width for minimum and maximum.
2) If that field only take the Numeric Value then check it’ll only take Numeric no other type.
3) If it takes the date or time then check for other.
4) Same way like Numeric you can check it for the Character, Alpha Numeric and all.
5) And the most significant if you click and hit the enter key then some time page may give the error of JavaScript, that is the big fault on the page .
6) Check the field for the Null value.
ETC…………………
The date field we can check in different ways
Positive testing: first we enter the date in given format
Negative Testing: We enter the date in unacceptable format suppose if we enter date like 30/02/2006 it should show some error message and also we use to check the numeric or text
Tuesday, April 8, 2008
Software Testing Interview Questions 6
- Explain SDLC and STLC?
- When will you start the testing process?
- What is Test Plan and Test Case?
- What is the difference between Integration Testing and System Testing?
- If an ATM machine is given to you for testing, how will you move toward to test it and also ensure that right information is updated in the database or not?
- If a screen is provided to you and the enter data in that screen is getting updated into one table. What all types of test case you will make and how will you ensure in the database whether the enter data is updated properly or not?
- What are Performance Testing, Stress Testing and Load Testing?
- What is the hardest test case you have written?
- What are the top priority bugs you have found out in your preceding projects?
- Explain functional testing?
- What are Testing Methodologies.
Software Testing Interview Questions 5
1. What you mean by Win Registry and what is its purpose?
2. What is the command to call up Win Registry?
3. What is IIS?
4. What is XML?
5. Dissimilarity between WELL form XML and XML?
6. Automation Tools – Win-Runner
7. How can you carry out load and stress testing on a single ATM machine?
8. What are ACID properties?
9. What is replication? Tell various kinds of replications?
10. Write a sql query to get ‘Last Day’ of the last month.
11. How can you test a ‘calculator’?
12. How can you test a ‘Coke’ machine?
13. What are all Test deliverables?
14. What are the different components or folders which exist at ‘Regedit’ and What is all their purpose and usage?
15. Explain about ‘Web Server’, ‘Web Service’, IIS and security constraints?
16. What is ‘Log file’ in SQL Server?
17. What are the tuning techniques for SQL Server?
18. What is use of ‘Query Profiler?’
19. How can you guarantee when testing a ‘Form’ of saving data to db? Without having any SRS/client’s specifications.
20. Difference between Remoting and Web services and describe each in short.
Subscribe to:
Posts (Atom)