Testing Concepts Wipro FAP Dumps

8/12/2019 Testing Concepts Wipro FAP Dumps

http://slidepdf.com/reader/full/testing-concepts-wipro-fap-dumps 1/69

1. Big bang model of testing

-Concentrates on each …..something like dis

-concentrates on each model… something kike dis

2. Test plan captures

Different milestones

3. A manual testing technique in which the author presents/tells the logic code and programe

module to a group of persons /colleagues, error detection but not correction

Walkthrough

4. A technique in which of persons discuss for creatie and !something solution

".#efect is deviation from standards

$.%ocalisation testing is

Target particular locale/culture

Target any locale/culture

&.'hat are testing actiities inoled in design phase

(.The testing that inoled internal logic/code white bo.

).Blac* bo+ testing chec*s the re!uirements

1.-ne more question on white bo+ testing!

11.oot cause analsis is done in acceptance testing.

12.Testing team should hae

#omain *nowledge

#ata base *nowledge

Tools 0+pertise

"ll

13.'hich is not done b test manager test eecution

14.Test case priorit depends upon

ustomer priorittabilit if functions

mpacted functionalit

1".on5statistical technique of testing

6istogram

7lowchart

catter chart

un chart

1$.generall to chec* to memor oerflow stress testing can be used



1&.8olume testing chec*s the physical and logical limits of system capacity

1(.The testing for a new software to chec* whether it can handle ma9or testing eents

!..something li*e this. #anity testing

1).what is another name for functional testing:

2.Desk check$

8erification technique conducted b the author of the artifact to erif the

completeness.

21. ost of qualit;

<one spend aboe and beond e+pected production costs, this inoles

preention,appraisal,internal=e+ternal failure costs

22. Test strateg;

t is statement of oerall approach of testing to meet the business and testob9ecties . it identifies the methods , techniques and tools to be used for testing.

A test strateg will tpicall coer the following aspects

#efinition of test ob9ectietrateg to meet the specified ob9ectie

-erall testing approach

Test enironment

Test automation requirements

<etric plan

is* identification, <itigation and contingenc plan

#etails of tools usage

pecific #ocument templates used in testing

23. 6ow identif the test case:

Test case %D t is unique number gien to test case in order to be identified.

24. Test e+ecution consist of following actiities to be performed

reation of test setup or testbed0+ecution of test cases on the setup

Test methodolog used

ollection of metrics

#efect trac*ing and reportingegression testing

2". There are two approaches in integration testing

Top5down>stubs?

Bottom5up>>driers?

2$. ntegration testing;

Tests partial sstems composed of integrated components.



2&.Bottom5up approach @using test driers

2(.stem testing;

Test cases are based on the sstem specification

t is critical part of the testing process as the sstem is erified as a whole.

2). enerall to chec* memor oerflow5sstem testing can be used.

3.'hat ma*es a good test engineer:

A strong desire for qualit, and an attention to detail.

31. -rder of testing

nit, integration, sstem, alidation..>the changed the order. will find correctl?

32. &eview is an actiit carried out to erif the documents at different stages foe its

completeness, correctness = consistenc.

33.n which phase it is least cost to correct the errors

Analsis = #esign

34. 7unctional testing is black bo testing

3". The graphical representation of the test data sets 'lowchart

3$. Cualit control is a validation process.

3&. Test e+ecution consist of

reation of test setup/bed, e+ecution of test cases, defect trac* and report.

3(.Actiites done in requirement phase testing Templates, test plan, test strateg, acceptance criteria

3).8alidation means

Assures that the end product meets the userDs needs.

4.Test case contains; nput = e+pected output.

41. cost of qualit definition.

42. -b9ectie of formal reiew is to find defects.

43. <itigation plan @ (ow to avoid risk

44.The e+ecution order of test case depends on

7unctional interdependenc

Test case priorit

Both a = b

4". 7unctional testing tools



ational robot

'in runner

8isual test

All of the aboe

4$. Test case sheet contains

Test case #, e+ecution procedure, function to be tested, results

4&. #eising of test cases basing on functionalit is )lack bo testing

4(. A bit li*e!.. There are some screens how u test it:

sing winrunner

4).harecteristics of a good test

Tests are li*el it catch bugs

o redundanc

ot to simple or too comple+

"ll the above

". 0quialence class is a subset of data that is representative of large class.

"1. ontingenc5what to do if the risk were to occur

"2. )ug reporter is medium of communicator b/w tester and deeloper.

"3. )eta testing is done outside organiEation

"4. CA load is performance testing

""!!!!..testing are done during test plan .

nit and integration

stem = regression Acceptance

"ll the above

"$.Test plan is the one that describes oerall approach of testing .

"&.%oad test is 0+amines ss performance at abnormal frequenc, load, olume

0+amines whether ss performance at threshold limit pass/fail

)oth a * b

"(. <emor profile is done using which tool +oad runner

"). Testing comes to an end when

Test cases e+ecuted with certain F passed

Test budget depleted

#onDt remember

"ll the above

$. Gerformance testing is done to erif

6ardware = software performance



-ptimum configuration

esponse time brea*

"ll the above

$1.Test plan contains its direct quest

$2.is* mitigation specifies how to avoid risks

$3. #es* chec* is verification techni!ue conducted by author to verify completeness

$4. static analsis is done for

equirements

coding

design

all the above

$". Testing team should hae

#omain *nowledge

#atabase *nowledge Tools e+pertise

"ll

$$. 'hat should be done after ris* identificationis* mitigation = contingenc plan

mpact analsis = procedures

ewrite test cases

)oth a * b

$&. nstallation testing is

To ensure that necessar components of application are installed

To chec* whether the uninstallation wor*s fine of the installed sstem.

$(. Grimar purpose of testing is

To ensure that product meets the userDs requirements specification.

$). olume testing is used

To determeine logical and functional limits of a sstem

&.'ipro template is a reference used of

000 std. (2)51)(3

&1. Grogram code siEe can be determined from ,+C

&2. 0+haustie testing is impossible

&3. Testing is stopped when!!!..

&4. Cualit ontrol comes under alidation process

&". win runner is a 'unctional automation testing tool



&$. %ocaliEation testing is

"dapting graphics for a specific culture/locale.

roduct0s !uality for a particular target culture/locale.

11. &egression testing is …………….

12. Test plan is …….. ans$all of the above

13. There are some 45 test cses to be eecuted and to complete it do you "c!uire 45 testers.

"c!uire 64 testers.

Use a win runner automation tool.

Do not use win runner !utomation tool.

25. capture and replay are !utomation tools of

Tcl7tk

Winrunner

8pect

"ll of the above

29. Which testing techni!ue re!uires devised test cases in order to test internal logic of code

White box testing

)lack bo testing:rey bo testing

#ome option

(2. #efect are classified as

#everity and priority

Test cases and priorit

ode and priorit

Test engineer and code

(3. apture and repla tools are used for

#atabase quer

:;% application

ome optionAll of the aboe

(4. T% stands for

oftware Testing %ife cle

oftware Technical %ife cle

ome thing one

(". A good tester has characteristics

Tact and diplomacAttention to detail

ood communication s*ill"ll of the above

($. oal of !!!!!. Testing is to handle international mar*et without an displa problem

:lobali<ation testing

ecurit testing

egression testing

ome option



(&. 'hich testing is to determine if a new software ersion is performing will enough to accept it

for ma9or testing effort

#anity testing

egression testing

-ption0tc

((. Hou hae " users which are to log into sstem simultaneousl. 'hat has to be done to

chec* behaiour of sstem

ecruits " testers

se tool li*e winrunner

;se tool like load runner

ome option

(). #efinition of audit

). 'hat has to be done in design phase

repare and verify test case and test script= prepare traceability matri as per re!uirement

Grepare test plan0tc

)1. which is not part of formal reiew

eiew is to be done in small groupsAn issues has to be prepared in adance

onducted b *nowledgeable member *nown as a moderator who is not an author of product

being reiewed or member of team

"uthor should always take part in review

)2. uppose there is a high seerit defect in sstem. 'hat should be done

#uspend testing until that defect is fied and again resume testing

)3. Test strateg is

%t is done in line to meet business and test ob>ectives

)4. 'hat is test case:

)". 'hat is reiew:t is an actiit carried out to chec* consistenc, completeness and correctness of documents at

different stages.

)$. 'hich one is not a alid blac* bo+ testing technique

8rror guessing

)&. 'ipro has specific templates in elociq

These templates are fleible and we can use client templates or by our own

)(. 7unctional testing also *nown as

)lack bo testing

)). )ug reporter is medium of communicator between tester and deeloper.



1. Test strateg definition:

11. !!! Testing is done outside organiEation

)eta

12. CA load is

erformance testing tool

13. !!!! testing are done during test plan

;nit=integration=system=regression=aceptance

14. !!!.. is the one that describes oerall approach of testing

Test plan

1". %oad test

8amines #ystem performance at abnormal fre!uency= load= volume and eamines whether

system performance at threshold limit pass or fail

1$. <emor Grofilling is done using which tool+oad runner

1&. Testing comes to an end when

Test cases eecuted with certain ? passed=Test budget depleted

1(. Gerformance testing is done to erif

(ardware and software performance= optimum configuration= &esponse time break

1). Test plan contains!!!!.

11. is* mitigation specifies

(ow to avoid risks

111. 'hat is des* chec*:

erification techni!ue conducted by author to verfy completeness

112. tatic analsis is done for

&e!uirement= analysis=coding

113. Testing team should hae

Domain knowledge= database knowledge=tools epertise

114. 'hat should be done after ris* identification

&isk mitigation and contingerncy plan= %mpact analysis and procedures

11". #es* chec* testing:

11$. oles of pro9ect manager, team leader, team member:

11&. Test strateg, test plan concepts:

11(. eiew, wal* through:



11). 8arious tpes of testing tools:

Testing techniques;

Alpha

Betanit

ntegrationtress, load

Acceptance

Gerformance

12. 8erfication and alidation:

121. 7ull form of 000:

122. Bench mar* testing

123. localiEation or globaliEation:

124. 'hich tool is used for performance testing

+oad runner

12". 'hat is the reason for bug:

rogramming error= software compleity

12$. Big bang model of testing:

12&. 'hat is acceptance testing:

12(. 'hat are the tools used for load testing:

Winrunner= loadrunner= robust

12). 'hat is the need of separate testing team:

#trangers can do the testing more accurately

Conflict of interest between developers and testers reduces

13. 'hat is reiew:

131. 'hat is qualit assurance:

132. 6ow will ou identif a test case:

;sing test case id

133. 'hats not there in a test plan:

#7w re!uirements= test environment= test re!uirements management

134. 'hat is the need of Cualit ontrol:

13". 'hat is test strateg:



1. Preparation for the review meeting is mandatory in which form of review.a. Code Inspectionb. Code Walkthroughc. Technical Review

d. None of the above. !uthor shall not act as """""""""""" in Code #nspection.

a. #nspection $eaderb. Reader c. Both a and bd. None of the above

%. Code #nspection team can have minimum """""""" no. of participants.a. 3b. &c. d. '

(. Who should not participate in the Code #nspection meeting)a. Testing Team $eader b. Program Managerc. *oth a and bd. None of the above

+. What is true about Comparison Testing)a. Run all versions in parallel with a real-time comparison of results.b. Run different versions one by one with a real,time comparison of results.c. -se same teams to develop independent versions of the software.

d. Test each version with different test data

&. pecification based testing is aa. Testing techniue b. Test trategyc. Test case designd. None of the above

/. 0ollowing is NT a testing techni2uea. pecification basedb. Code,basedc. Bread testingd. pecific techni2ue

'. Client3erver Testing is aa. pecification based Test Techni2ueb. Code,based Test Techni2uec. Thread testing Test Techni2ued. !omain "pecific test techniue

4. *lack bo5 test design is also called asa. Re2uirement,based test designb. 0unctional test designc. Both a and bd. None of the above

16. The purpose of Re2uirement,based testing is only toa. 0ind incorrect or missing functionalityb. 7radicate Performance errorsc. 0ind presence of #nitiali8ation and termination errorsd. #ll of the above



11. Re2uirement,based testing guarantees testing againsta. Positive testingb. Negative testingc. -se case testingd. #ll of the above

1. 0ollowing is NT a re2uirement,based test case design techni2uea. 72uivalent Partitioningb. Branch Coveragec. *oundary 9alue !nalysisd. Cause 7ffect :raphing

1%. ! possible programming element to determine e2uivalent input classa. Rangeb. 9aluec. a or bd. nly a

1(. ;ividing the input domain in to classes of data to arrive at test cases is aa. Code based techni2ueb. Reuirement based techniuec. *oth a and bd. None of the above

1+. When a programming element has valid value and valid length< to derive test cases were2uire techni2ue

a. 72uivalence Class Rangeb. $uivalence Class %aluec. 72uivalence Class etd. 72uivalence Class *oolean

1&. Complementary techni2ue of *oundary 9alue !nalysis isa. $uivalent Partitioningb. Cause 7ffect :raphingc. *ranch coverage analysisd. Cyclomatic Comple5ity

1/. Possible tests for a range of values bounded by a and b area. =a,1>< a< =a?1>

b. =b,1>< b< =b?1>c. a and bd. a or b

1'. teps to arrive at test cases using Cause 7ffect :raphing Techni2ues area. decision table rules are converted to test casesb. ! cause@effect graph developedc. :raph converted to a decision tabled. "euence of steps as a& b& c

14. The techni2ue to test and arrive at test cases for Reliability of software isa. 72uivalent Partitioningb. Cause 7ffect :raphingc. *oundary 9alue analysisd. Comparison tests

6. White bo5 test case design is also called asa. Code-based test case designb. 0unctional Test case designc. *oth a and bd. No e2uivalent name

1. To arrive at Code,based test design the tester is ideally e5pected to havea. Aigh level designb. 'ow level designc. *oth a and bd. !rchitecture of the Product design



. The purpose of Code,based testing is only toa. 0ind typographical errorsb. 0ind logical errorsc. -nderstand the programming obBective to arrive at test casesd. #ll of the above

%. Code,based testing guarantees testing againsta. Path coverageb. Condition coveragec. yntactical and typographical errorsd. #ll of the above

(. ! re2uirement to achieve Code,based testing is to havea. Code walkthrough and Code inspection checklistb. Traceability matri5c. Both a and bd. nly a

+. 0ollowing is not a code,based test case design techni2uea. tatement coverageb. *ranch Coveragec. Boundar( %alue #nal(sisd. Condition coverage

&. 7lementary statements of a program are e5ecuted at least once ina. "tatement coverageb. *ranch Coveragec. Condition coveraged. Cyclomatic Comple5ity

/. *oolean e5pressions3Conditions are tested ina. *oundary 9alue !nalysisb. Condition coveragec. Cyclomatic Comple5ityd. 7dge Coverage

'. 7very path3iterations in the control flow graph e5ecution is covered in which of thefollowing design

a. 7dge coverage

b. path Coveragec. tatement coveraged. *ranch coverage

4. ! techni2ue adopted for evaluating the comple5ity of programming logic isa. 72uivalent partitioningb. *oundary value analysisc. Comparison testingd. C(clomatic Comple)it(

%6. 0or a Control flow graph< the Cyclomatic Comple5ity is defined to bea. v*+, e - n /b. e D v=:> , n ? c. v=:> D e @ n ? (d. v=:> D n ? ? e

%1. White *o5 testing and *lack *o5 testing area. Phases of testingb. Cycles of testingc. T(pes of Testingd. Eethods of testing

%. ne of the following appropriately represents White *o5 testinga. Code level testingb. tructural testingc. Both a and bd. None



%%. White *o5 testing reports deviation froma. Coding standardsb. $ogic and Programming stylec. Comple5ity of Coded. #ll of the above

%(. Two categories of White bo5 testing area. Basic Path testing and C(clomatic Comple)it(b. Cyclomatic Comple5ity and 72uivalence partitioningc. *asic Path Testing and *oundary 9alued. a and b

%+. 7dge coverage and path coverage are measures of a. 0hite Bo) Testing #deuac( criteriab. *lack *o5 Testing !de2uacy criteriac. *oth a and bd. None of the above

%&. *oundary value analysis is included ina. White *o5 Testingb. Blac1 Bo) Testingc. *oth a and bd. None of the above

%/. !nswer to the testerFs 2uestion, GAave # found all seeded errorsH isa. 0hite Bo) Testingb. *lack*o5 Testingc. *oth a and bd. None of the above

%'. !nswer to testerFs 2uestion GAave # applied all the inputsH isa. White *o5 Testingb. Blac1 Bo) Testingc. *oth a and bd. None of the above

%4. Test Preparation Checklist should contain one or more of the followinga. Correct number and version of the system under testb. Test #nput data readiness

c. Readiness of the test environmentd. #ll of the above

(6. Testing 7mbedded ystem is to test3confirma. nly oftwareb. nly hardwarec. #nterfacing with hardware and softwared. #ll of the above

(1. -nit testing with embedded system is achieved througha. Code walkthroughb. -sing debuggerFs scripting languagec. -sing test harnessd. #n( of the above depending on comple)it( of the s(stem

(. Which of the following is not a characteristic of 7mbedded ystem testing

a. Aighly comple5 systemb. 2on technical person can conduct testsc. Needs imulated environmentd. ;ifficult to test run time behavior

(%. ystem testing of embedded software is to testa. !ctual Aardware functionalityb. !ssume the oftware is interacting as e5pectedc. ne #nstrument and one functionality at a timed. all of the above



((. Characteristic of a Client3erver ystem isa. ave multiple processors4"erversb. Aave one processor3erver c. -niversal Client with ame d. all of the above

(+. Iey areas< a tester need to know while testing #nternet and web application area. *rowser Compatibilityb. 0unctional correctnessc. -sability and ecurityd. #ll of the above

(&. Primary test concerns for #nternet presence is to test applicationsa. Correctnessb. -sabilityc. *rowser Compatibilityd. #ll of the above

(/. 0ollowing is a Type of #nternet and Web !pplication Testinga. Component and #ntegration testingb. ystem testingc. -!Td. #ll of the above

('. Compatibility and Navigation testing are carried out duringa. Component testingb. Integration testingc. ystem testingd. -!T

(4. Which one of the following is an activity of Eicro Processa. Plan& !esign& !evelop& Review and $)ecute Test Casesb. Plan and 75ecute Test casesc. Review test casesd. 75ecute test cases

+6. *est method to conduct ystem level testing isa. Re2uirement based testingb. #ntegration testing

c. 5se case based testingd. Code based testing

+1. Which attributes are used whenever a *ug3;efect is detecteda. 7rror J faultb. ;efect J *ugc. "everit( 6 Priorit(d. poradic J Reproducible

+. Which of the following is relevant if a *-: is in its deferred statea. !eveloper will loo1 into it in ne)t release.b. Tester has identified a wrong bug.c. ;eveloper will not work on this bug.d. *ug will be resolved immediately

+%. ! *ug is a poradic bug if it

a. Can be reproduced accurately.b. Cannot be reproduced accuratel(.c. is not 2ualified.d. it is 0i5ed

+(. oftware test plan should consist of a. oftware Test 7nvironmentb. Test identificationc. Test chedulesd. #ll the above



++. ystem verview briefly states thea. Purpose and nature of the systemb. The software to which this document appliesc. Types or classes of tests that will be performedd. a 6 b

+&. ystem verview summari8es history of a. system development<b. operation and maintenance.c. None of the aboved. Both a 6 b

+/. """"""""""" shall summari8e the purpose and contents of the Test Plan documentand shall describe any security or privacy considerations associated with its use.

a. ystem overviewb. Referenced ;ocumentsc. !ocument 7verviewd. None of the above

+'. oftware items identifiesa. perating systemsb. Compilers and interpretersc. Communications software

d. 7nl( a&c+4. Procedures for manual< automatic and semi,automatic techni2ues for recording test

results is defined ina. Test $evelsb. Test Classesc. Test Progressiond. !ata Recording& Reduction& #nal(sis

&6. ! listing or chart depicting the sites at which the testing will be scheduled and the timeframes during which the testing will be conducted is described in

a. Test 7nvironmentb. Test "chedulingc. Test #dentificationd. Test $evels

&1. Code inspection and Code walk through fall under which type of testinga. ;ynamic testingb. "tatic testingc. ystem Testingd. None of the !bove

&. Reader in code inspection is the person whoa. Aas generated the codeb. 0ho runs through the code line b( linec. uggest solution to the anomaliesd. Aas sound technical knowledge

&%. Person who runs through the code in Code Walk through isa. Walkthrough leader b. Reader

c. Team membersd. Eoderator &(. Check list is used in code inspection to find

a. 0aultsb. :a8e a developer c. ;eviation from coding standardsd. Both a 6 c



&+. Work products that undergo reviews area. ystem buildb. Release notesc. ource coded. #ll of the above

&&. ! technical review is aa. 'ess formalb. 0ully 0ormalc. Can be done without a sound technical persond. #s helpful only for automation testing

&/. ;uring code inspection the a. chec1 list is reuired

b. Eanager should participate.c. Code is e5ecuted to find faultsd. Eeeting could e5tend for a full day

&'. !s per :-# standards Title names of the menu bar must begin witha. -pper case letter followed by lower case letterb. -nder line the character that represent hotkeyc. nly upper cased. a 6 b

&4. !n author in code inspection cannot play the role ofa. Readerb. #nspector c. Recorder d. #ll of the above

/6. Re2uirements are collected bya. ystem !nalystb. Kuality manager c. ubBect Eatter 75pertd. a 6 c

/1. Complete preparation on code prior to review is mandatory for a. Code Inspection b. Code Walk Through

c. Technical Reviewd. !ll of the above

/. ! good :-#a. Eust be comple5b. :rouped unrelated components together c. Balance the displa( of items on screend. None of the above

/%. Which of the following is most appropriate feature of Eanual testinga. 7asy to repeatb. Can run unattendedc. !lways reliabled. Time consuming

/(. Which of the following is most appropriate feature of !utomation testing

a. Reliableb. -nable to simulate all scenariosc. Cannot run unattendedd. ;ifficult to report

/+. oftware test automation refers to activities and efforts that intend to automatea. Processb. Tasksc. $ngineering Tas1sd. *oth a J b



/&. elect the best option for the Eanual Testing from the followinga. !lways reliableb. Not costlyc. Certain scenarios practically possibled. 2one of the above

//. elect the best option for the !utomation Testing from the followinga. Not able to generate scenariosb. Not reliablec. Not Repeatabled. +ood Return on Investment if properl( planned.

/'. The main obBective of !utomation testing processa. To completely eliminate the manual testing processb. Not to achieve better test coveragec. To speed up a software testing processd. None of the above

/4. 0irst phase in the !utomation testing process life cycle isa. ;esign Test !utomation strategies and solutionsb. elect and evaluate available Test automation toolc. ;evelop and implement test automation solutionsd. Plan for "oftware test automation.

'6. White bo5 testing tools testsa. 0unctionality of the softwareb. Performance of the softwarec. -ser acceptance criteriad. Coding standards and memor( lea1s

'1. Which of the following is White bo5 testing toolsa. WinRunnerb. !stra Kuick testc. K! Rund. Rational purifier and Rational uantifier

'. 0unctionality Testing tools verifies for thea. Code coverageb. Parameteri8ation

c. Code comple5ityd. 2one of the above

'%. *atch Testing in the 0unctionality testing tools is used for a. 75ecute single testb. -sed to parameteri8ec. 5sed to e)ecute group of test scripts.d. -sed to handle errors

'(. 9erification points are also called asa. Parameteri8ationb. 7rror Aandlingc. Chec1 pointsd. None of the above

'+. Eain obBective of the Web Testing is one of the following

a. Test for the only functionalityb. Test for the bro1en lin1sc. Test for the memory leaksd. Test for the code coverage

'&. Which of the following is 0unctionality test automation tool.a. $oad Runnerb. Rational purifierc. Rational robotd. None of the above



'/. Test management tools address one of the following belowa. 0unctionalityb. Performancec. !efects trac1ing and Reuirements gatheringd. None of the above

''. Which of the following is a test management toola. Win runnerb. Kuick test professionalc. K! Rund. Rational test manger

'4. Response time and capacity both area. ;irectly proportional to each otherb. 72ual to each otherc. Inverse proportional to each other d. None of the above

46. -se cases mainly consists of a. Transitionsb. #ctorsc. 7ventsd. None of the above

41. 75pand the word !P#a. !utomated programming interfaceb. #pplication programming interfacec. !utomated performance interfaced. None of the above

4. 75pand the word #;7a. #nternational ;evelopment 7nvironmentb. Integrated !evelopment $nvironmentc. #nternational ;elivery 7nvironmentd. None of the above

4%. Performance of the web sites are tested using which techni2uea. Eanual testingb. #utomation testing

c. -nit Testingd. #ntegration Testing

4(. Web based applications are developed under which """"""""""""$anguagea. tructured programming languageb. 7b8ect 7riented Programming languagec. cripting languagesd. None of the above

4+. calability comes under which category of testinga. 0unctionalb. 2on 9 :unctionalc. Regressiond. -nit Testing

4&. G9erify system from user perspectiveH this statement is appropriate to which type of

Testing a. 0ield Testb. Regression Testc. Performance Testd. #cceptance Test

4/. Which of the one mentioned below can be the correct definition for 0ield Testa. verif( that the s(stems wor1 in actual user environment.b. 9erification from the userFs perspectivec. *oth a J cd. The purpose is to verify the system meets the performance re2uirements.



4'. GPilot system should work during a problemH< is an e5pectation made ina. #nterface Testb. Performance Testc. !cceptance Testd. :ield Test

44. cope of the ProBect is mentioned ina. Test 7nvironmentb. Traceability Eatri5c. Test Pland. Test chedule

166. #dentification of numbers< titles< abbreviations< version numbers and release numbersare mentioned in

a. Test scheduleb. "copec. Test 7nvironmentd. Test Plan

161. Which document covers the -nit re2uirements in all applicable oftwareRe2uirements pecifications

a. Test Caseb. Test #dentification

c. Traceabilit( Matri)d. Test ;esign

16. Preparation of review< and approval of the oftware Test Report=TR> is done duringa. Test 7nvironmentb. Test "chedulingc. Test #dentificationd. Test Cases ;esign

16%. #RFs refers toa. #ntermittent Re2uirements pecificationsb. #nternal Re2uirements pecificationsc. Interface Reuirements "pecificationsd. #ntermittent Re2uirement software

16(. Which of the following is test case generation tool

a. Rational robotb. WinRunner c. Caliber RBTd. None of the above

16+. !utomated testing is mainly carried out in which type of the testinga. -nit Testingb. anity testingc. -ser acceptanced. Regression testing

16&. Which of the following is the Performance toola. Rational R*Tb. ilk testc. Kuick Test professional

d. 'oad Runner 16/. Performance testing is carried mainly usinga. Eanual testingb. 75plorative testingc. #utomated Testing toolsd. None of the above



16'. !utomated testing tools generates LLL..scriptsa. Non,Reusable scriptsb. Re,usable scriptsc. Reliable scriptsd. Both b 6 c

164. Capacity under the performance testing deals witha. !mount of timeb. Concurrent usersc. $oadd. Performance

116. Throughput under the performance deals witha. #mount of time b. Concurrent usersc. $oadd. Performance

111. Response time under the performance testing deals witha. Time ta1en for the server to respond to the client reuest.b. Time taken for the client to respond to the server.c. !ll of the aboved. None of the above

11. !utomation 0rame work should be LLLL. f Toolsa. ;ependentb. Independentc. *oth of the aboved. None of the above

11%. Win Runner uses which type of the scripting languagea. Perlb. TC$c. 9*d. T"'

11(. Who will be contacted3used as ubBect matter 75pertsa. !omain $)pertb. ProBect manager

c. Team leadd. ystem !nalyst

11+. 0unctionality testing tool GTest partnerH ;eveloped byLL.. Companya. Eercuryb. eguec. Rationald. Compuware

11&. Which of the following is an open source tool for the ;efect Trackinga. Test ;irector b. Bug;illac. $oad Runner d. WinRunner

11/. Which of the following is server side Testing Tool

a. Perlb. T$c. 9*d. None of the above

11'. Which of the following Tool is used to maintain 7ntire testing artifacts =CentralRepository>

a. WinRunner b. $oad Runner c. Kuick test professionald. Test !irector



114. oftware Configuration includesa. "oftware Reuirements "pecification& a !esign "pecification and source

code.b. oftware Re2uirements pecification< a Test Plan and source code.c. Test Plan< a ;esign pecification and source code.d. oftware Re2uirements pecification< a ;esign pecification and Test

Plan16. ! test configuration includes

a. Test Plan and Procedures< ;esign pecification and testing tools.b. Test Plan and Procedures& test cases and testing toolsc. Test Plan and Procedures< test cases and source coded. Test Plan and Procedures J test cases only

11. #t is difficult to schedule the Test 0low becausea. #t is difficult to predict the time re2uired to analy8e the re2uirementsb. It is difficult to predict the time to debug the codec. #t is difficult to predict the time re2uired for test pland. #t is difficult to predict the time re2uired to report the *ugs

1. The details of how the testing team will evaluate the work products< systems andtesting activities and results are mentioned in

a. Test 75it Criteria

b. Test Casesc. Test "trateg(d. Test 7nvironment

1%. The approach to all testing types and phases and the activities for which they areresponsible are mentioned separately in

a. Test Planb. Test "trateg(c. Traceability Eatri5d. Test Cases

1(. Test trategy for Eaintenance includes a greater focus on a. 0unctional Testingb. Regression Testingc. Performance Testing

d. 0ield Testing1+. The main inputs for Test trategy are

a. Priorit( 6 criticalit(b. Test Participationc. Test 7nvironmentsd. 9erification of -n,testable Re2uirements.

1&. Test taffing< Testing of CT< Poor Re2uirements are some of the e5amples fora. Test strategyb. Test related issuesc. Test Pland. Test ;esign

1/. pecification based testing is also called asa. White bo5 testing

b. Blac1 bo) testingc. Code *ased Testingd. tatic Testing

1'. Which are the ones clubbed under Testing Techni2uesa. 5sage based Testingb. Test issuesc. Test trategyd. Test #dentification



14. Code *ased Testing is also called asa. 0hite bo) testingb. tatic Testingc. *lack *lock Testingd. 0unctional Testing

1%6. bBect riented Testing< Component *ased Testing are """"""""""""" TestingTechni2ues

a. -sage *asedb. "pecific Techniuec. Code *asedd. 0unctional Testing

1%1. 7rror :uessing< Eutation< 0ault eeding are"""""""" Testing Techni2uesa. -sage *asedb. pecific Techni2uec. Code *asedd. :ault Based

1%. *lack *o5 Test Case ;esign Techni2ue consists of a. $uivalence Partitioningb. Path Coveragec. Cyclomatic Comple5ity

d. Code #nspection1%%. 0ormal pecification *ased< Control 0low *ased Criteria< ;ata 0low based criteria

are """"""""""""""testing techni2uesa. White *o5b. Blac1 bo)c. pecific Techni2ued. -sage based

1%(. tatistical testing< =EusaFs>R7T are """""""""""testing techni2uesa. 0ault *asedb. *lack bo5c. pecific Techni2ued. 5sage based

1%+. Test ;ata !de2uacy Criteria is mainly categori8ed in

a two t(pesb. three typesc. Not categori8edd. ;epends on the Re2uirements

1%&. Test preparation Checklist mainly consists of a. Test #db. #nput ;*c. 9ersiond. -sers !3ce. #ll of these

1%/. Reset ystem< Test 7nvironment< take Aolders< and chedule are the contents ofa. Test data !de2uacy Criteriab. Test Preparation Chec1list

c. Test Pland. Test 7nvironment1%'. Test ;esign pecification is

a. Code *ased Test Case ;esignb. Re2uirement *ased Test Case ;esignc. Both a6 bd. Test data !de2uacy Criteria

1%4. Purposes of Test ;esign pecification are



a. Test #dentificationb. tudy *usiness Re2uirements< !rrive at Aigh $evelc. ;ecide !utomation Re2uirementsd. Reuirements of Test #pproach& Identif( the features to be tested& #rrive

at igh 'evel1(6. tudy *usiness Re2uirements< !rrive at 7nvironmental Re2uirements are the

""""""""""followed in Test ;esign pecificationa. #pproachb. Contentsc. Purposed. Coverage

1(1. Code based testing can derive the test cases to ensurea. !ll the bugs have been detectedb. #ll independent paths are e)ercised at least once.c. !ll the re2uirements have been metd. !ll the standards have been met

1(. !pproach of the proBect is mentioned undera. Test copeb. Test 7nvironmentc. Test Plan

d. Test trategy



Testing oncepts5<i%I

ection A; <ultiple hoices

1? esponse time under the performance testing deals withTime taken for the server to respond to the client re!uest

2? 'hich document coers the nit requirements in all applicable oftwareequirements pecifications

Test ase

Test dentification

Traceabilit <atri+

Test Design

3? JJJJJJJJJJassure that the software continues to perform according to specifications

after it has been modifiedompatabilit Testing

mo*e Testing

&egression testing

Gerformance Testing

4? n < abeKs clomatic omple+it 8>?, 8 refers to

The Cyclomatic @umber in graph Theory

omple+it is a function of graph

Both of the aboe one of the aboe

::"? ompatibilit and aigation testing are carried out duringomponent testing

ntegration testing

stem testing

;"T

$? #uring code inspection the

Check list is re!uired

<anager should participate

ode is e+ecuted to find faults

<eeting could e+tend for a full da

::&? 'hich one of the following is true related to Automating tests through

#ifficultostl

8asier

Both A and B



(? 'hich attributes are used wheneer a Bug/#efect is detected

0rror = fault

#efect = Bug

#everity * riority

poradic = eproducible

)? The purpose of equirement5based testing is onl to

7ind incorrect or missing functionalit

0radicate Gerformance errors7ind presence of nitialiEation and termination errors

"ll of the above

1? 7ollowing is -T a requirement5based test case design technique0quialent Gartitioning

)ranch Coverage

Boundar 8alue Analsis

ause 0ffect raphing

11? 'hich framewor* is an application independent framewor*

,eyword driven testing and table driven testing

Ieword drien tesing and test script modularit

Table drien testing and librar archetectureAll of the aboe

12? A good

<ust be comple+rouped unrelated components together

)alance the display of items on screen

one of the aboe

13? 'hite Bo+ testing reports deiation from

oding standards%ogic and Grogramming stle

omple+it of ode

"ll of the above

14? cope of the Gro9ect is mentioned in

Test 0nironment

Traceabilit <atri+

Test lan

Test chedule

1"? 7ormal pecification Based, ontrol 7low Based riteria, #ata 7low based criteria

are JJspecification basedJJJJJJJJJJJJtesting techniques

White )o

Blac* bo+



pecific Technique

sage based

1$? JJJJJJJJJJJ will be facilitating an resources required for the testing team

Test lead

Test AanagerTest 0ngineer

lient

1&? 0lementar statements of a program are e+ecuted at least once in

#tatement coverage

Branch oerage

ondition coerageclomatic omple+it

1(? 'hen the complete set of functionalit is ta*en for one module and tested is called

(ori<ontal first testing8ertical first testing

Both a =b one of the aboe

1)? Test management tools address one of the following below7unctionalit

Gerformance

Defects tracking and &e!uirements gathering

one of the aboe

2? AT%< tands for

Automated Testing %ifeccle <odel

"utomation Tesing +ifecycle methodology

one of the aboe

Application Tesingn %ifecle <ethods

21? Blac*bo+ Testing find errors in

ncorrect or missing functions

nitialiEation and Termination 0rrors

)oth of the above

one of the aboe

::22? t is difficult to schedule the Test 7low because

t is difficult to predict the time required to analEe the requirements

t is difficult to predict the time to debug the codet is difficult to predict the time required for test plan

%t is difficult to predict the time re!uired to report the )ugs



23? hoose the reason for failure in Test Automation

%ac* of structured automation methodolog

<aintaining <odularit in autmation scripts

)oth " and )

Test sutomatin is treated as a pro9ect with proper pro9ect planning

24? oftware test automation refers to actiities and efforts that intend to automate

Grocess

Tas*s0ngineering Tas*s

)oth a * b

2"? To arrie at ode5based test design the tester is ideall e+pected to hae6igh leel design

+ow level design

Both a and b

Architecture of the Groduct design

2$? 7ind the test ob9ecties below;1F code coerage

Testing entire application

eporting all the bugs in the application

"ll of the above

2&? JJJJJJJJJleads to a selection of testcases that e+ercise bounding alues

0G0+tracted Testcases

%ogical stem

)"

ection B; True/7alse 2( Automation improes the test coerage

True 7alse

2) 7unctionalit Testing is a balc*bo+ oriented because programs internal structure is

ta*en as consideration

True 'alse

3 Applications that are business critical, high frequenc usage and logn life span are the

right candidates for Automation

True 7alse



1? Tpical tests e+ecuted as part of <aintenance and upport Gro9ects

7unctional/stem testing

Bug fi+es testingegression testing

"ll of the above

2? elect the best option for the Automation Testing from the following

ot able to generate scenarios

ot reliable ot epeatable

:ood &eturn on %nvestment if properly planned

3? 'hile creating test cases which attributes we need to ta*e care#efect detection effectieness

0+emplar

ost consideration

"ll of the above

4? 'hat is true about omparison Testing:

&un all versions in parallel with a real-time comparison of results

un different ersions one b one with a real5time comparison of results

se same teams to deelop independent ersions of the softwareTest each ersion with different test data

"? <etrics ma be used for

cheduleiEe/omple+it

Cualit

"ll the above

$? Gurposes of Test #esign pecification are

Test dentificationtud Business equirements, Arrie at 6igh %eel

#ecide Automation equirements

&e!uirements of Test "pproach= %dentify the features to be tested= "rrive at (igh

+evel

&? The main ob9ectie of Automation testing process

To completel eliminate the manual testing process ot to achiee better test coerage

To speed up a software testing process

one of the aboe

(? oftware test plan should consist of

oftware Test 0nironment

Test identification



Test chedules

"ll of the above

)? #uring code inspection the

Check list is re!uired

<anager should participateode is e+ecuted to find faults


1? -ne of the following appropriatel represents 'hite Bo+ testing

ode leel testing

tructural testing

)oth a and b

one

11? nit testing uses JJJJJJJJJ design description as a guide

6igh leelComponent +evel

Both of the aboe one of the aboe

12? 7ollowing is a Tpe of nternet and 'eb Application Testingomponent and ntegration testing

#ystem testing

AT

All of the aboe

13? 'hile Assessing Application nder Test for Automation which are points we need to

consider umber of Automatable Tests

#eeloper Bac*ground

Build and elease tabilit and 7requenc

)oth " and C

14? 'hat are Test 0stimation nfluencing factors

Tester *ill leel, locationLTest equirement scope,

rocess= &isk

All of the aboe

1"? ode5based testing guarantees testing against

Gath coerageondition coerage

ntactical and tpographical errors

"ll of the above



1$? Gerformance testing chec*s for

esponse time brea*s

-ptimum configuration6ardware and software performance

"ll of the above

1&? 7ollowing is not a code5based test case design technique

tatement coerage

Branch oerage

)oundary alue "nalysis

ondition coerage

1(? Greparation for the reiew meeting is mandator in which form of reiew:

Code %nspection

ode 'al*through

Technical reiew

one of the aboe

1)? ser acceptance testing is the responsibilt of#oeloper

Test 0ngineer

;ser representative Teams

All of the aboe

2? eader in code inspection is the person who

6as generated the code

Who runs through the code line by line

uggest solution to the anomalies

6as sound technical *nowledge

21? se cases mainl consists of

Transitions

"ctors

0ents

one of the aboe

22? egression Testing can be done b

<anuall

Automated Testing tools

)oth a * b

one of the aboe

23? 'hich of the mentioned point is best suited for Test Automation 7ramewor*:

" test automation framework is a set of assumptions= concepts= and practices that

provide support for automated software testing.

A Test automation is a set of ules and onstraints



Both A and B

one of the aboe

24? 'ho resoles the Technical issues for the product group

Test <anager

Test 0ngineer#eeloper

Test +ead

2"? 'hen the complete set of functionalit is ta*en for one module and tested is called

(ori<ontal first testing

8ertical first testing

Both a =b one of the aboe

2$? Automated testing tools generates !!!..scripts

on5eusable scriptse5usable scripts

eliable scripts

)oth b * c

2&? 'hat ma be the common mista*e the tester ma*e in test automation:nderestimating the cost of automation

creating test scripts that is difficult to maintain for long term

nderestimating the need for stall training

"ll of the above

ection B; True/7alse 2( Automate those thing which human cannot do

True 7alse

2) 'e can e+ecute the scripts generated in CTG using Cualit enter

True 7alse

3 Automate those thing which human cannot do

True 7alse

ote; Gar2 3 Cuestions wrong

CuestionsMMM

2?JJJJJare interchangeable terms that refer to an application5independent wor*:



,eyword driven * Table-Driven Testing

en testing = #ata #rien testing

en testing = #ata #rien testing

3?8erfication points are also called as

GarameteriEation

0rror 6andling

Check points

one of the aboe

4? n Automation trends, cripts mapped to actions performed against a class of ob9ectsomes under which categor:

Action 'ord5based

'indow5Based

Class-)ased-b9ect5Based

"?pecification based testing is a

Testing techni!ue

Test tratergTest case design

one of the aboe

Ans b

$?equirement5based testing guarn

Gostting testing egatie testing

se case testing

"ll of the above

Ans c

&?n which pahse of Test Automation process, the design!!#eeloped and testied as qualit tools and also ma!!!

eliable and reusable with good documentation:

Test Automation Glanning

Test Automation #esign

Test tool development

Test tool



(?n an automation 7ramewor* Approach, who builds the model to capture required

behaior and logical ariations of data and control:

Gro9ect %eadTest %ead

Test 8ngineer

All the aboe

Ans c

)?Best method to conduct stem le!!..

&e!uirement based testing

ntergration testing

se case basd testingode based testing

Ans b

1?Test librar architecture diided

cripts

rocedures and 'unctions

-nl a

Both a=b

11?ational Gurifier belongs to which

7unctionalit Testing tool

Whitee )o Testing Tool

Test5case eneration Tool

14?Greperation for the reiew meeting is mandator in which form of reiew

Code %nspection

ode 'al*through

Technical 0ie

All the aboe

1"?A possible programming element to determine

ange

8alue

" or b

-nl a

1$? #iiding the input domain in to classes of data to



ode based technique

&e!uirement based techni!ue

Both a and b one of the aboe

1)?'hat are the *e properties considered for Automationeliablilit

ntegrit

<aintainabilit

"ll the above

2?calabilit comes under which categor of testing

7unctional

@on-'unctional

egression

nit Testing

21?dentification of number, titles, abbreiation are mentioned in

Test chedulecope

Test 0nironment

Test lan

22?oftware test plan should consist of

oftware Test 0nironment

Test identificationTest chedules

"ll the above

Ans c

23? stem -eriew briefl states theGurpose and nature of the sstem

The software to which this docume..

Tpes or classes of test that will

A and b

24?Grocedures for manual, automatic and semiautomatic!results is defined in

Test %eelsTest lasses

Test Grogression

#ata ecordin, eduction

2"? A listing or chart depicting the site at which the tes!frames during which the testing

will be conducted is!



Test 0nironment

Test #cheduling

Test dentificationTest %eels

Ans d

2$?n which phase of test automation ..deeloped and tested as qualit to !reliable and

reusable with good docu

Test Automation GlanningTest Automation #esign

Test Tool Development

Test Tool #eploment

2&? 7ollowing is -T a requirement5base test case

0quialent Gartitoning

)ranch Coverage

Boundar 8alue Analsisause 0ffect raphing

3?#uring code inspection the

check list is re!uired

<anager should participateode is e+ecuted to find faults


31?'hite bo+ test case design is also called as

Code based test case design

7unctional Test case design

Both a and b o equialent name

Ans s

32?To arrie at ode5based test design the tester is ideall e+pected to hae

6igh %eel design

%ow %eel design

)oth a and b

Architecture of the ptoduct design

Ans c

33?Boolean e+pressions/onditons are tested inBoundar alue analsis

Condition Coverage

clomatic omple+it

0dge oerage



Ans b

34?n which Automation Trend, Actions/*eword are recorded or generated:

apture/Glabac*

,eyword Driven "pproach#ata #rien Approach

All the aboe

3"?ofware onfiguration include

a?oftware equirements specification , a design specification and source

oftware equirement, specidfication, a test plan and source codeTest plan, a #esign !.cification and source code

oftware equirements ..specification , a design specification and test !!plan

3$?Answer to testerDs question N6ae applied all the inputsO is'hite Bo+ Testing

)lack )o Testing

Both a and b

one of the aboe

3&?Two categories of white bo+ testing are

)asic ath testing and Cyclomatic Compleity

clomatic omple+it and 0quialence partitioning

Basic Gath testing and Boundar 8alueAns a and b

3(?'hich one of the following is an actiit of <icro GrocessGGlan, #esign,#eelop , eiew and e+ecute test cases

Glan and e+ecute test cases

eiew test cases0+ecute test cses

3)?'hich attributes are used wheneer a Bug/#efect is detected.:

0rror and fault#efect and Bug

#everity and riority

poradic and eproducible

Ans 5555confirmed

4?'hich document coers the nit requirements in all applicable ofware requirement

pecifications

Test ase

Test identification



Traceablilt <atri+

Test Design #pecification

41?..describe te qualit of a test case:

!effectieness and e+emplar

..= 0olable

42?!which software testing tool

..testing tool!ting tool

..ent tool

ation tool

44?Test %ibrar Architecture !

caripts

Grocedures

either a or bBoth a and b

4$?'hat are the attributest that..

#efect detection efficienc

ost onsideration either a or b

Both a and b

4&?7ollowing are two possible programming element ..we can derermin equialent inputclasses

lasses5alues

lasses @ range

4(?comparison testing is not to catch errors in the specification but to understand how

reliable the software is under arious test enironments

4)?ondition coerage definition

odition coerage is a combination of edge coerage and more detached conditions

"?code based test case design

ode based testing inoles statement coerage, edge coerage condition coerage path

coerage and cclometric comple+it

"1?lassifcation of the bugs. 7ollowing twor attributes are used whener a bug defect is

detectedeerit >ritical/serius/minor?

Grior > high/medium/low?



1.1. Greparation is mandator for which tpe of reiew

a. ode nspection

b. Technical reiewc. ode wal* through

d. one of the aboe

2.2. 'hich of the following testing will ensure the reliabilit of software

a. omparison testing

b. ntegration testingc. nit testing

3.3. equirements5Based Test ase #esign includes;equirements5Based Test ase #esign includes; Gositie Testing

egatie Testing

se ase testing

All of the aboe

4.4. Automation testing is used for

a. To decrease the time of testing b. To completel remoe manual testing

c. ..

d. ..

".". stem -eriew contains

a. Gurpose and nature of the sstem b. stem decribed in the document.

c. Both a and b

d. one of the aboe

$. There are 4 attributes that describe qualit of a test case.

Ans; #efect detection effectieness, 0+emplar, ost consideration

=0olable

&. Test tool deelopment ;

At this step, the designed test automation solutions are deeloped and tested as qualittools and facilities. The *e in this step is to ma*e sure that the deeloped tools are

reliable and reusable with good documentation.

(.Actions/*ewors are generated ina.*eword drien

b.ecord and plabac*

c!.

).who builds the model to capture required behaiour and logical ariations of date and

controla. Test 0ngineer



1. Ieword5drien testing and table5drien testing are interchangeable terms that refer to an

application5independent automation framewor*

11.'hite bo+ testing tool1.rational purifier

12. Test librar architecture diides the application5under5test into procedures and functions

instead of scripts.

13.Title,Abbreation,release ersion of product will be in which document

a.Test plan b.Test taterg

14.software configuration containsa.equirement specification,#esign specification,source code

b. equirement specification,#esign specification,test plan

1". <icro processor testing

a.0+ecute testcases

b.eiew the testcasesc.specification,design ,e+ecute!

1$.calabilit comes under which testing

a.7unctional testing b.on 7unctional testing

1&. 6ae applied all the inputs: equirement5based Testing

1(.Tracebilt matri+

a.alues are unique

1).A tester should *now for code based testing

a.6igh leel design

b.%ow leel designc.Both a = b

2.'hich will indicate when the testing should be started

a.Test plan b.test straterg

c.Test schedule

21.'hat are all the code based testing techniques

1.Gath coerage2.clomatic comple+it



22.The programming elements that determine the input classes.

a.0quialence portioning b.Boundar alue analsis.

23.8erification points are also calleda.chec*points

b.0rror handling

24.lass -b9ects;cripts mapped to actions performed against a class of ob9ects

2".Boolean is used in

a.0quialence portioning

2$.ode based testing technique is also called as

a.'hite bo+ testing

b.Blac* bo+ testing

2&.equirment based testing is aa.Testing technique

b.Testing design technique



1. client/serer testing is a

specification based

code baseddomain

thread

2. who should not participate in the code inspection

testing team leader program manger

a and b

none

answer will be there in int 11

3. scope of the pro9ect is described in

test plan

test strateg

4. performance testing is mainl used in

e+ploratie testing

manual testingautomated testing

all

". field testing is for

to erif the sstem wor*s in the user enironment

to erif in the user perspectiea and b

to chec* the performance

$. naigation and compatibilit is done at

integration testing

sstem testingAT

&. two attributes are used wheneer a Bug/#efect is detected;two attributes are used wheneer a Bug/#efect is detected;

eerit and Grioriteerit and Griorit

(. ob9ect oriented testing and component based testing is a

specific techniques



). 6ae found all seeded errors:

ode5based Testing

1. omparison Testing

un all ersions in parallel with a real5time comparison of results.

11. Test Automation5 #efinitionTest Automation5 #efinition

Actiities and efforts that intend to automate engineering tas*s andActiities and efforts that intend to automate engineering tas*s and

operations in software test process.operations in software test process.

'ell5defined strategies and sstematic solutions.'ell5defined strategies and sstematic solutions.

Both a and b

12. attributes that describe qualit of a test case.

#efect detection effectieness and 0+emplar

ost consideration and 0olable

13. The primar ob9ectie of this step is to draw out the detailed test

automation solutions to achiee the ma9or ob9ecties and meet the gien

requirements in a test automation plan.

Test automation planning

Test automation #esign

Test tool deploment

13. Test cript deeloped fromTest cript deeloped from

•• Ieword / Table #rien ArchitectureIeword / Table #rien Architecture

•• #ata #rien Architecture#ata #rien Architecture

•• 6brid Architecture6brid Architecture

•• Translated modelTranslated model

14. procedures for manual, automatic and semi5automatic is described in

Test leels

Test classes

Test progression

1". Automation 7ramewor* onsiderationsAutomation 7ramewor* onsiderations



<aintainabilit, eiewabilit, reliabilit, ntegrit, independence and performance<aintainabilit, eiewabilit, reliabilit, ntegrit, independence and performance

1$. white bo+ testing reports the deiation from1$. white bo+ testing reports the deiation from

oding standardsoding standards%ogical errors%ogical errors

omple+it of the codeomple+it of the code

All of the aboeAll of the aboe

1&.1&. 7unctionalit Testing Tools;57unctionalit Testing Tools;5

ecord and Glabac* capabilitecord and Glabac* capabilit

-b9ect ecognition = -b9ect epositor-b9ect ecognition = -b9ect epositor

A and b

one

1(. cripts mapped to actions performed against a class of ob9ects

lass based

-b9ect based'indow based

1). n *eword drien architecture, which dries the AT:

a. test script

b. ariablesc. a and bd. none

2. wh the testing is done in offshore

a. reduce staffing

b. increase qualitc. a and b

d. !!.

21. triple. <eeting confidence!!!!

a. #elphi

b. 6bridc. Test automation

d. !!.

22. what is ris*



a. becoE something happens that affects the ob9ecties.

b. !.c. none

23. how testing is done, e+ecute, results!!

a. test strateg

b. test casec. test plan

24. A#8ATA0 of automation

a. integrit b. maintainabilit

c. reliabilitd. all

2". manual testing can be related to

a. Time consuming

b. eliabilit

c. nattendedd. All

2$. thethe reasons for failure in automationreasons for failure in automation

a.a. modulariEationmodulariEation

automation strategiesautomation strategies

!!.

all

7ew <-0 questions;

2&. 7unctional Testing is a *ind of !!!!!!!.2&. 7unctional Testing is a *ind of !!!!!!!. a.blac* bo+ testinga.blac* bo+ testing

b.white bo+ b.white bo+

2(. !!!!!!.to2(. !!!!!!.to erif the sstem wor*s in the actual user enironment

a.7ield Testing

b.nterface Testing



2).2). The two attributes are used wheneer a Bug/#efect is detected are !!!!!The two attributes are used wheneer a Bug/#efect is detected are !!!!!

a.Griorit = eerita.Griorit = eerit

3.3. f the defect is not consistentl reproducible it is called poradic

31.31. clomatic comple+it, >? P e 5 n Q 2

32. se separate teams to deelop independent ersions of the software and un all

ersions in parallel with a real5time comparison of results omparison testing.

33. Checklist is used to fnd aults in Code inspection

34. 6ae applied all the inputs: equirement5based Testing 3". ode5Based Test ase #esign ;Gath oerage and clomatic comple+it

3$. Ieword5drien testing and table5drien testing are interchangeable terms that refer to

an application5independent automation framewor*

3&. lass -b9ects;cripts mapped to actions performed against a class of ob9ects

3(.<icro processor testing ; software metrics and productiit.>not sure chec* the

answer once again?

3). Test librar architecture diides the application5under5test into procedures and

functions instead of scripts.

4. Automation Trends 5 apture and Glabac*.

41. There are 4 attributes that describe qualit of a test case. Ans; #efect detection effectieness, 0+emplar, ost consideration =0olable

42. Test tool deelopment ;

At this step, the designed test automation solutions are deeloped and tested as

qualit tools and facilities. The *e in this step is to ma*e sure that the deeloped

tools are reliable and reusable with good documentation.

43. equirements5Based Test ase #esign includes;equirements5Based Test ase #esign includes; Gositie Testing

egatie Testing

se ase testing

All of the aboe

44. sing 0quialence lasses5Boolean is used in 0quialent Gartioning.

4". 4". Test automation planning;

The ma9or tas* here is to charter a plan that specifies the identified test automation

focuses, ob9ecties, strategies, requirements, schedule and budget.



















9B 'ormal #pecification )ased= Control 'low )ased Criteria= Data 'low

based criteria are testing techni!ues

'hite Bo+

Blac* bo+

pecific Technique

sage based

6B Work products that undergo reviews are

stem build

elease notes

ource code

All of the aboe

B )lack bo test design is also called as

equirement5based test design

7unctional test design

Both a and b

one of the aboe

EB erification points are also called as

GarameteriEation

0rror 6andling

hec* points

one of the aboe

4B #ystem verview summari<es history of

sstem deelopment

operation and maintenance



one of the aboe

Both a = b

FB )ridges the gap between user and developer

<

ource code

#esign

1B To arrive at Code-based test design the tester is ideally epected to have

6igh leel design

%ow leel design

Both a and b

Architecture of the Groduct design

2B Which of the following is most appropriate feature of "utomation testing

eliable

nable to simulate all scenarios

annot run unattended

#ifficult to report

3B #ystem verview briefly states the

Gurpose and nature of the sstem

The software to which this document applies

Tpes or classes of tests that will be performed

a = b

95B assure that the software continues to perform according to

specifications after it has been modified



ompatabilit Testing

mo*e Testing

egression testing

Gerformance Testing

99B During code inspection the

hec* list is required

<anager should participate

ode is e+ecuted to find faults


96B Which are the Disadvantages of key word driven method

0asier to construct and maintain than the functional decomposition scripts.

The test automation team can reuse the e+isting >manual? test cases.

Building the core utilit scripts requires a er degree of proficienc in the

testing tool being used.

-nce the generic utilit scripts are in place, building the erification scripts

ta*e a much shorter period of time.

9B ;se cases mainly consists of

Transitions

Actors

0ents

one of the aboe

9EB While selecting automation tool which are the things we need to

considerG

upport from the endor

7unctionalities of the tool



Both A and B

one of the aboe

94B What is #T"'

stem Test Automation 7ramewor*

oftware Test Automation 7ramewor*

oftware Test Automation 7unction

one of the aboe

9FB &ational &obot and &ational 'unctional Tester are used for which type

of Testing

7unctional Testing

'hite Bo+ Testing

equirement Testing

Gerformance Testing

91B The main ob>ective of "utomatin testing process

To completel eliminate the manual testing process

ot to achiee better test coerage

to speed up a software testing process

one of the aboe

92B Design must be translated into a machine readable form by taking

input as

<

ource code



93B Testing components put together is called

nit Testing

7ield testing

ntegration Testing

ser acceptance testing

65B What are Test 8stimation %nfluencing factors

Tester *ill leel, location

LTest equirement scope,

Grocess, is*

All of the aboe

69B Why do we document our testsG

for repeatable = controllable

for adequate test coerage

Both a = b

one of the aboe

66B Code based testing can derive the test cases to ensure

All the bugs hae been detected

All independent paths are e+ercised at least once.

All the requirements hae been met

All the standards hae been met

6B 'ollowing is not a code-based test case design techni!ue

tatement coerage

Branch oerage

Boundar 8alue Analsis



ondition coerage

6EB Which of the following is the erformance tool

ational BT

il* test

Cuic* Test professional

%oad unner

64B Choose the reason for failure in Test "utomation

%ac* of structured automation methodolog

<aintaining <odularit in autmation scripts

Both A and B

Test sutomatin is treated as a pro9ect with proper pro9ect planning

6FB Win &unner uses which type of the scripting language

Gerl

T%

8B

T%

61B Test management tools address one of the following below

7unctionalit

Gerformance

#efects trac*ing and equirements gathering

one of the aboe

ection B; True/7alse

62 We can eecute the scripts generated in HT using Huality Center

True 7alse



63 "utomate those thing which human cannot do

True 7alse

5 "pplications that are business critical= high fre!uency usage and logn life

span are the right candidates for "utomation

True 7alse



















Documents

Testing Concepts Wipro FAP Dumps