Manual Testing Faqs 2

8/14/2019 Manual Testing Faqs 2

1/9

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 herefor 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 testto (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 herefor the

explanation of erformance, 0oad and *tress )esting with examples.

Q.%*)!3 questions and answers4more questions here and here5

"ns. Click above links to read %*)!3paper pattern and tips on how to solve the questionsquickly. %*)!367oundation 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 )est4or5 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 testingAns.Click herefor 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
http://www.softwaretestinghelp.com/software-testing-questions-and-answers-part2/http://www.softwaretestinghelp.com/some-interesting-software-testing-interview-questions/http://www.softwaretestinghelp.com/how-to-prepare-for-software-testing-interview/http://www.softwaretestinghelp.com/test-your-software-testing-knowledge-take-this-mock-test/http://www.softwaretestinghelp.com/most-frequently-asked-winrunner-interview-questions-with-answers/http://www.softwaretestinghelp.com/most-frequently-asked-winrunner-interview-questions-with-answers/http://www.softwaretestinghelp.com/winrunner-questions-from-interviewer-point-of-view/http://www.softwaretestinghelp.com/winrunner-automation-tool-preparation/http://www.softwaretestinghelp.com/short-automation-testing-interview-questions/http://www.softwaretestinghelp.com/what-is-performance-testing-load-testing-stress-testing/http://www.softwaretestinghelp.com/istqb-question-pattern-and-tips-to-solve/http://www.softwaretestinghelp.com/istqb-software-testing-certification-sample-question-paper-2/http://www.softwaretestinghelp.com/istqb-testing-certification-sample-question-papers-with-answers/http://www.softwaretestinghelp.com/recommended/ISTQBhttp://www.softwaretestinghelp.com/recommended/ISTQBhttp://www.softwaretestinghelp.com/preparation-of-qtp-interview-questions/http://www.softwaretestinghelp.com/cste-software-testing-certification-exam-question-patern/http://www.softwaretestinghelp.com/some-tricky-question-answers/http://www.softwaretestinghelp.com/smoke-testing-and-sanity-testing-difference/http://www.softwaretestinghelp.com/what-is-client-server-and-web-based-testing-and-how-to-test-these-applications/http://www.softwaretestinghelp.com/black-box-testing/http://www.softwaretestinghelp.com/white-box-testing/http://www.softwaretestinghelp.com/types-of-software-testing/http://www.softwaretestinghelp.com/software-testing-questions-and-answers-part2/http://www.softwaretestinghelp.com/some-interesting-software-testing-interview-questions/http://www.softwaretestinghelp.com/how-to-prepare-for-software-testing-interview/http://www.softwaretestinghelp.com/test-your-software-testing-knowledge-take-this-mock-test/http://www.softwaretestinghelp.com/most-frequently-asked-winrunner-interview-questions-with-answers/http://www.softwaretestinghelp.com/most-frequently-asked-winrunner-interview-questions-with-answers/http://www.softwaretestinghelp.com/winrunner-questions-from-interviewer-point-of-view/http://www.softwaretestinghelp.com/winrunner-automation-tool-preparation/http://www.softwaretestinghelp.com/short-automation-testing-interview-questions/http://www.softwaretestinghelp.com/what-is-performance-testing-load-testing-stress-testing/http://www.softwaretestinghelp.com/istqb-question-pattern-and-tips-to-solve/http://www.softwaretestinghelp.com/istqb-software-testing-certification-sample-question-paper-2/http://www.softwaretestinghelp.com/istqb-testing-certification-sample-question-papers-with-answers/http://www.softwaretestinghelp.com/recommended/ISTQBhttp://www.softwaretestinghelp.com/recommended/ISTQBhttp://www.softwaretestinghelp.com/preparation-of-qtp-interview-questions/http://www.softwaretestinghelp.com/cste-software-testing-certification-exam-question-patern/http://www.softwaretestinghelp.com/some-tricky-question-answers/http://www.softwaretestinghelp.com/smoke-testing-and-sanity-testing-difference/http://www.softwaretestinghelp.com/what-is-client-server-and-web-based-testing-and-how-to-test-these-applications/http://www.softwaretestinghelp.com/black-box-testing/http://www.softwaretestinghelp.com/white-box-testing/http://www.softwaretestinghelp.com/types-of-software-testing/


2/9

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


3/9

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 )estingAns."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


4/9

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 providedrequirements.

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 riorityAns.%t indicates the importance or urgency of fixing a defect

Q.What is


5/9

Q.What is


6/9

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,

*


7/9

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 ofthe customer, a strong desire for quality, and an attention to detail. Tact and diplomacyare useful in maintaining a cooperative relationship with developers, and an ability tocommunicate with both technical (developers) and nontechnical (customers,management) people is useful. !revious software development e"perience can behelpful 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 toassess highrisk areas of an application on which to focus testing efforts when time islimited.

What makes a good Software QA engineer?The same qualities a good tester has are useful for a $A engineer. Additionally, theymust be able to understand the entire software development process and how it can fitinto the business approach and goals of the organi%ation. &ommunication skills and theability to understand various sides of issues are important. n organi%ations in the earlystages 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 inspectionsand reviews.

What makes a good QA or Test manager?A good $A, test, or $ATest(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


8/9

* 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 isinsufficient 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 nontechnical 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.) $Apractices 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 asystem for easily finding and obtaining documents and determining whatdocumentation will have a particular piece of information. &hange management fordocumentation 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" softwarepro+ect is to have poorly documented requirements specifications. /equirements are thedetails describing an application's e"ternallyperceived functionality and properties./equirements should be clear, complete, reasonably detailed, cohesive, attainable, andtestable. A nontestable requirement would be, for e"ample, 'userfriendly' (toosub+ective). A testable requirement would be something like 'the user must enter theirpreviouslyassigned password to access the application'. 0etermining and organi%ingrequirements details in a useful and efficient way can be a difficult effort1 differentmethods are available depending on the particular pro+ect. 2any books are availablethat 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 therequirements process. '&ustomers' could be inhouse personnel or out, and couldinclude endusers, customer acceptance testers, customer contract officers, customermanagement, future software maintenance engineers, salespeople, etc. Anyone whocould later derail the pro+ect if their e"pectations aren't met should be included ifpossible.rgani%ations vary considerably in their handling of requirements specifications. deally,the requirements are spelled out in a document with statements such as 'The productshall.....'. '0esign' specifications should not be confused with 'requirements'1 designspecifications should be traceable back to the requirements.n some organi%ations requirements may end up in high level pro+ect plans, functionalspecification documents, in design documents, or in other documents at various levelsof 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 clearcut way to determine if a softwareapplication is performing correctly.'Agile' methods such as 7! use methods requiring close interaction and cooperationbetween programmers and customersendusers to iteratively develop requirements.

The programmer uses 'Test first' development to first create automated unit testingcode, which essentially embodies the requirements.


9/9

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 othernecessary documents* btain budget and schedule requirements* 0etermine pro+ectrelated personnel and their responsibilities, reporting requirements,

required standards and processes (such as release processes, change processes, etc.)* dentify application's higherrisk aspects, set priorities, and determine scope andlimitations 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 (recordplayback tools, coverage analy%ers, testtracking, problembug 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 reviewsapprovals* 6rite test cases* 8ave needed reviewsinspectionsapprovals of test cases* !repare test environment and testware, obtain needed user manualsreferencedocumentsconfiguration guidesinstallation guides, set up test tracking processes, setup logging and archiving processes, set up or obtain test input data* btain and install software releases* !erform tests* 4valuate and report results* Track problemsbugs and fi"es* /etest as needed* 2aintain and update test plans, test cases, test environment, and testware through

life cycle

Manual Testing Faqs 2

Documents

Transcript of Manual Testing Faqs 2