Manual testing interview questions and answers Ans.

How to define a standard process for the entire testing flow, how to explain challenging situations in manual testing career, What is the best way to go about getting a pay rise. Click above link for answers to these questions. Q. What is the most challenging situation you had during testing Q. How to perform testing if there are no documents Ans. Click here for the detailed post on how to answer these !" interview questions. Q. How to prepare for software testing#!" interview Ans. Click above link to know $ Where should % start with for preparation of interview %t&s almost ' years % have faced any interview. Q. Mock test to (udge your software testing interview skills Ans. )ake this mock test paper helpful for preparing testing interview as well as the C*)+ certification exam. Click above link for questions and answers. Q. Winrunner interview questions with answers Ans. ,reparing for Winrunner interview $ )hese are some important Winrunner interview questions frequently asked in automation testing interview. Winrunner questions -, questions ' and questions . Q. /ifferent "utomation )esting %nterview !uestions Ans. Click above link for automation interview questions like /ifference between Winrunner and )est /irector, What is )*0 What 120 is it similar too Q. What is difference between ,erformance )esting, 0oad )esting and *tress )esting +xplain with examples Ans. Many people are confused with these testing terminologies. Click here for the explanation of ,erformance, 0oad and *tress )esting with examples. Q. %*)!3 questions and answers 4more questions here and here5 "ns. Click above links to read %*)!3 paper pattern and tips on how to solve the questions quickly. %*)!3 67oundation level& sample questions with answers. Q. !), interview questions Ans. !uick )est ,rofessional8 %nterview !uestions and answers. Q. C*)+ questions with answers Q. What is /esk checking and Control 7low "nalysis Ans. Click here $ /esk checking and Control 7low "nalysis along with examples Q. What is *anity )est 4or5 3uild test Ans. 9erifying the critical 4important5 functionality of the software on new build to decide whether to carry further testing or not. Q. What is the difference between client:server testing and web based testing Ans. Click here for the answer. Q. What is black box testing Ans. 3lack box testing explained with types Q. What is white box testing Ans. Click here for the post explaining white box testing explained with types Q. What are different types of software testing Ans. Click here to refer the post explaining in detail all *oftware )esting )ypes

Q. What is /ynamic )esting Ans. %t is the testing done by executing the code or program with various input values and output is verified. Q. What is 2;% )esting Ans. 2;% or 2raphical user interface testing is the process of testing software user interface against the provided requirements#mockups#H)M0 designs. Q. What is 7ormal )esting Ans. *oftware verification carried out by following test plan, testing procedures and proper documentation with an approval from customer Q. What is <isk 3ased )esting Ans. %dentifying the critical functionality in the system then deciding the orders in which these functionality to be tested and applying testing. Q. What is +arly )esting Ans. Conducting testing as soon as possible in development life cycle to find defects at early stages of */0C. +arly testing is helpful to reduce the cost of fixing defects at later stages of *)0C. Q. What is +xhaustive )esting Ans. )esting functionality with all valid, invalid inputs and preconditions is called exhaustive testing. Q. What is /efect Clustering Ans. "ny small module or functionality may contain more number of defects $ concentrate more testing on these functionality. Q. What is ,esticide ,aradox Ans. %f prepared test cases are not finding defects, add#revise test cases to find more defects. Q. What is *tatic )esting Ans. Manual verification of the code without executing the program is called as static testing. %n this process issues are identified in code by checking code, requirement and design documents. Q. What is ,ositive )esting Ans. )esting conducted on the application to determine if system works. 3asically known as =test to pass> approach. Q. What is ?egative )esting Ans. )esting *oftware with negative approach to check if system is not =showing error when not supposed to> and =not showing error when supposed to>. Q. What is +nd:to:+nd )esting Ans. )esting the overall functionality of the system including the data integration among all the modules is called end to end testing. Q. What is +xploratory )esting Ans. +xploring the application, understanding the functionality, adding 4or5 modifying existing test cases for better testing is called exploratory testing. Q. What is Monkey )esting Ans. )esting conducted on a application without any plan and carried out with tests here

and there to find any system crash with an intention of finding tricky defects is called monkey testing. Q. What is ?on:functionality )esting Ans. 9alidating various non functional aspects of the system such as user interfaces, user friendliness security, compatibility, 0oad, *tress and ,erformance etc is called non functional testing. Q. What is ;sability )esting Ans. Checking how easily the end users are able to understand and operate the application is called ;sability )esting. Q. What is *ecurity )esting Ans. 9alidating whether all security conditions are properly implemented in the software 4or5 not is called security testing. Q. What is ,erformance )esting Ans. ,rocess of measuring various efficiency characteristics of a system such as response time, through put, load stress transactions per minutes transaction mix. Q. What is 0oad )esting Ans. "naly@ing functional and performance behavior of the application under various conditions is called 0oad )esting. Q. What is *tress )esting Ans. Checking the application behavior under stress conditions 4or5 <educing the system resources and keeping the load as constant checking how does the application is behaving is called stress testing. Q. What is ,rocess Ans. " process is set of a practices performed to achieve a give purposeA it may include tools, methods, materials and or people. Q. What is *oftware Configuration Management Ans. )he process of identifying, Brgani@ing and controlling changes to software development and maintenance. 4or5 " methodology to control and manage a software development pro(ect Q. What is )esting ,rocess # 0ife Cycle Ans. Write )est ,lan )est *cenarios )est Cases +xecuting )est Cases )est <esults /efect <eporting /efect )racking /efect Closing )est <elease Q. What is full form of CMM% Ans. Compatibility Maturity Model C %ntegration

Q. What is Code Walk )hrough Ans. %nformal analysis of the program source code to find defects and verify coding techniques. Q. What is ;nit 0evel )esting Ans. )esting of single programs, modules or unit of code. Q. What is %ntegration 0evel )esting Ans. )esting of related programs, Modules 4or5 ;nit of code. 4or5 ,artitions of the system ready for testing with other partitions of the system. Q. What is *ystem 0evel )esting Ans. )esting of entire computer system across all modules. )his kind of testing can include functional and structural testing. Q. What is "lpha )esting Ans. )esting of whole computer system before rolling out to the ;"). Q. What is ;ser "cceptance )esting 4;")5 Ans. )esting of computer system by client to verify if it adhered to the provided requirements. Q. What is )est ,lan Ans. " document describing the scope, approach, resources, and schedule of testing activities. %t identifies test items, features to be tested, testing tasks, who will do each task, and any risks requiring contingency planning. Q. What is )est *cenario Ans. %dentify all the possible areas to be tested 4or5 what to be tested. Q. What is +C, 4+quivalence Class ,artition5 Ans. %t is method for deriving test cases. http8##www.softwaretestinghelp.com#what:is:boundary:value:analysis:and:equivalence: partitioning# Q. What is a /efect Ans. "ny flaw imperfection in a software work product. 4or5 +xpected result is not matching with the application actual result. Q. What is *everity Ans. %t defines the important of defect with respect to functional point of view i.e. how critical is defect with respective to the application. Q. What is ,riority Ans. %t indicates the importance or urgency of fixing a defect Q. What is <e:)esting Ans. <etesting the application to verify whether defects have been fixed or not. Q. What is <egression )esting Ans. 9erifying existing functional and non functional area after making changes to the part of the software or addition of new features.

Q. What is <ecovery )esting Ans. Checking if the system is able to handle some unexpected unpredictable situations is called recovery testing. Q. What is 2lobali@ation )esting Ans. ,rocess of verifying software whether it can be run independent of its geographical and cultural environment. Checking if the application is having features of setting and changing language, date, format and currency if it is designed for global users. Q. What is 0ocali@ation )esting Ans. 9erifying of globali@ed application for a particular locality of users, cultural and geographical conditions. Q. What is %nstallation )esting Ans. Checking if we are able to install the software successfully 4or5 not as per the guidelines given in installation document is called installation testing. Q. What is ;n:installation )esting Ans. Checking if we are able to uninstall the software from the system successfully 4or5 not is called ;ninstallation )esting Q. What is Compatibility )esting Ans. Checking if the application is compatible to different software and hardware environment or not is called compatibility testing. Q. What is )est *trategy Ans. %t is a part of test plan describing how testing is carried out for the pro(ect and what testing types needs to be performed on the application. Q. What is )est Case Ans. " )est case is a set of preconditions steps to be followed with input data and expected behavior to validate a functionality of a system. Q. What is 3usiness 9alidation )est Case "ns. " test case is prepared to check business condition or business requirement is called business validation test case. Q. What is a 2ood )est Case Ans. " )est case that have high priority of catching defects in called a good test case. Q. What is ;se Case )esting Ans. 9alidating a software to confirm whether it is developed as per the use cases or not is called use case testing. Q. What is /efect "ge Ans. )he time gap between date of detection C date of closure of a defect. Q. What is *howstopper /efect Ans. " defect which is not permitting to continue further testing is called *howstopper /efect Q. What is )est Closure Ans. %t is the last phase of the *)0C, where the management prepares various test summary reports that explains the complete statistics of the pro(ect based on the testing carried out.

Q. What is 3ucket )esting Ans. 3ucket testing is also know as "#3 testing. %t is mostly used to study the impact of the various product designs in website metrics. )wo simultaneous versions are run on a single or set of web pages to measure the difference in click rates, interface and traffic. Q. What is What is +ntry Criteria and +xit Criteria *oftware )esting Ans. )he +ntry Criteria is the process that must be present when a system begins, like, *<* $ *oftware 7<* ;se Case )est Case )est ,lan )he +xit criteria ensures whether testing is completed and the application is ready for release, like, )est *ummary <eport, Metrics /efect "nalysis <eport. Q. What is Concurrency )esting Ans. )his is a multiple user testing to access the application at the same time to verify effect on code, module or /3. mainly used to identify locking and deadlocking situations in the code. Q. What is Web "pplication )esting Ans. Web application testing is done on a website to check $ load, performance, security, 7unctionality, %nterface, Compatibility and other usability related issues. Q. What is ;nit )esting Ans. ;nit testing is done to check whether the individual modules of the source code are working properly or not. Q. What is %nterface )esting Ans. %nterface testing is done to check whether the individual modules are communicating properly as per specifications. %nterface testing is mostly used to test the user interface of 2;% applications. Q. What is 2amma )esting Ans. 2amma testing is done when the software is ready for release with specified requirements, this testing is done directly by skipping all the in:house testing activities. Q. What is )est Harness Ans. )est Harness is configuring a set of tools and test data to test an application in various conditions, which involves monitoring the output with expected output for correctness. )he benefits of )esting Harness are8 ,roductivity increase due to process automation and increase in product quality Q. What is *calability )esting Ans. %t is used to check whether the functionality and performance of a system, whether system is capable to meet the volume and si@e changes as per the requirements *calability testing is done using load test by changing various software, hardware configurations and testing environment.

Q. What is 7u@@ )esting Ans. 7u@@ testing is a black box testing technique which uses a random bad data to attack a program to check if anything breaks in the application. Q. What is /ifference between !", !C and testing Ans. !" %t is process oriented "im is to prevent defects in an application !C *et of activities used to evaluate a developed work product %t is product oriented )esting +xecuting and verifying application with the intention of finding defects Q. What is /ate /riven )esting Ans. %t is "utomation testing process in which application is tested with multiple set of data with different preconditions as an input to the script.

What makes a good test engineer?

A good test engineer has a 'test to break' attitude, an ability to take the point of view of the customer, a strong desire for quality, and an attention to detail. Tact and diplomacy are useful in maintaining a cooperative relationship with developers, and an ability to communicate with both technical (developers) and non technical (customers, management) people is useful. !revious software development e"perience can be helpful as it provides a deeper understanding of the software development process, gives the tester an appreciation for the developers' point of view, and reduce the learning curve in automated test tool programming. #udgment skills are needed to assess high risk areas of an application on which to focus testing efforts when time is limited.
What makes a good Software QA engineer?

The same qualities a good tester has are useful for a $A engineer. Additionally, they must be able to understand the entire software development process and how it can fit into the business approach and goals of the organi%ation. &ommunication skills and the ability to understand various sides of issues are important. 'n organi%ations in the early stages of implementing $A processes, patience and diplomacy are especially needed. An ability to find problems as well as to see 'what's missing' is important for inspections and reviews.
What makes a good QA or Test manager?

A good $A, test, or $A(Test(combined) manager should) * be familiar with the software development process * be able to maintain enthusiasm of their team and promote a positive atmosphere, despite * what is a somewhat 'negative' process (e.g., looking for or preventing problems) * be able to promote teamwork to increase productivity * be able to promote cooperation between software, test, and $A engineers

* have the diplomatic skills needed to promote improvements in $A processes * have the ability to withstand pressures and say 'no' to other managers when quality is insufficient or $A processes are not being adhered to * have people +udgement skills for hiring and keeping skilled personnel * be able to communicate with technical and non technical people, engineers, managers, and customers. * be able to run meetings and keep them focused
What's the role of documentation in QA?

&ritical. (,ote that documentation can be electronic, not necessarily paper.) $A practices should be documented such that they are repeatable. -pecifications, designs, business rules, inspection reports, configurations, code changes, test plans, test cases, bug reports, user manuals, etc. should all be documented. There should ideally be a system for easily finding and obtaining documents and determining what documentation will have a particular piece of information. &hange management for documentation should be used if possible.
What's the big deal about 'requirements'?

.ne of the most reliable methods of insuring problems, or failure, in a comple" software pro+ect is to have poorly documented requirements specifications. /equirements are the details describing an application's e"ternally perceived functionality and properties. /equirements should be clear, complete, reasonably detailed, cohesive, attainable, and testable. A non testable requirement would be, for e"ample, 'user friendly' (too sub+ective). A testable requirement would be something like 'the user must enter their previously assigned password to access the application'. 0etermining and organi%ing requirements details in a useful and efficient way can be a difficult effort1 different methods are available depending on the particular pro+ect. 2any books are available that describe various approaches to this task. (-ee the 3ookstore section's '-oftware /equirements 4ngineering' category for books on -oftware /equirements.) &are should be taken to involve A55 of a pro+ect's significant 'customers' in the requirements process. '&ustomers' could be in house personnel or out, and could include end users, customer acceptance testers, customer contract officers, customer management, future software maintenance engineers, salespeople, etc. Anyone who could later derail the pro+ect if their e"pectations aren't met should be included if possible. .rgani%ations vary considerably in their handling of requirements specifications. 'deally, the requirements are spelled out in a document with statements such as 'The product shall.....'. '0esign' specifications should not be confused with 'requirements'1 design specifications should be traceable back to the requirements. 'n some organi%ations requirements may end up in high level pro+ect plans, functional specification documents, in design documents, or in other documents at various levels of detail. ,o matter what they are called, some type of documentation with detailed requirements will be needed by testers in order to properly plan and e"ecute tests. 6ithout such documentation, there will be no clear cut way to determine if a software application is performing correctly. 'Agile' methods such as 7! use methods requiring close interaction and cooperation between programmers and customers(end users to iteratively develop requirements. The programmer uses 'Test first' development to first create automated unit testing code, which essentially embodies the requirements.

What steps are needed to develop and run software tests?

The following are some of the steps to consider) * .btain requirements, functional design, and internal design specifications and other necessary documents * .btain budget and schedule requirements * 0etermine pro+ect related personnel and their responsibilities, reporting requirements, required standards and processes (such as release processes, change processes, etc.) * 'dentify application's higher risk aspects, set priorities, and determine scope and limitations of tests * 0etermine test approaches and methods unit, integration, functional, system, load, usability tests, etc. * 0etermine test environment requirements (hardware, software, communications, etc.) * 0etermine testware requirements (record(playback tools, coverage analy%ers, test tracking, problem(bug tracking, etc.) * 0etermine test input data requirements * 'dentify tasks, those responsible for tasks, and labor requirements * -et schedule estimates, timelines, milestones * 0etermine input equivalence classes, boundary value analyses, error classes * !repare test plan document and have needed reviews(approvals * 6rite test cases * 8ave needed reviews(inspections(approvals of test cases * !repare test environment and testware, obtain needed user manuals(reference documents(configuration guides(installation guides, set up test tracking processes, set up logging and archiving processes, set up or obtain test input data * .btain and install software releases * !erform tests * 4valuate and report results * Track problems(bugs and fi"es * /etest as needed * 2aintain and update test plans, test cases, test environment, and testware through life cycle