<T> MC <#>Simple <Q> Testing should be stopped when: <C> All the planned tests have been run

<C> Time has run out <C> All faults have been fixed correctly <C+> I depends on the risks for the system being tested <T> MC <#> Complex <Q> Which of the following is the main purpose of the integration strategy for integration testing in the small? <C> To ensure that all of the small modules are tested adequately <C> To ensure that the system interfaces to other systems and networks <C+> To specify which modules to combine when and how many at once <C> To ensure that the integration testing can be performed by a small team <T> MC <#>Simple <Q> Which of the following is NOT part of configuration management: <C> Status accounting of configuration items <C+> Auditing conformance to ISO9001 <C> Identification of test versions <C> Record of changes to documentation over time <T> MC <#>Simple <Q> In software quality assurance work there is no difference between software v erification and software validation. <C>True <C+>False <T> MC <#>Medium <Q> Class testing of object-oriented software is equivalent to unit testing for traditional software. <C+>True <C>False <T> MC <#>Simple <Q> Regression testing should be performed: v) Every week w) After the software has changed x) As often as possible y) When the environment has changed z) Wwhen the project manager says <C> v & w are true, x z are false <C> w, x & y are true, v & z are false <C+> w & y are true, v, x & z are false <C> w is true, v, x y and z are false <T> MC <#>Simple <Q> A tool that supports traceability, recording of incidents or scheduling of t ests is called: <C> A dynamic analysis tool <C> A test execution tool <C> A debugging tool

<C+> A configuration management tool <T> MC <#>Simple <Q> The cost of fixing a fault: <C> Is not important <C+> Increases as we move the product towards live use <C> Decreases as we move the product towards live use <C> Is more expensive if found in requirements than functional design <T> MC <#>Simple <Q> Order numbers on a stock control system can range between 10000 and 99999 inclusive. Which of the following inputs might be a result of designing tests fo r only valid equivalence classes and valid boundaries: <C> 1000, 5000, 99999 <C> 9999, 50000, 100000 <C+> 10000, 50000, 99999 <C> 9999, 10000, 50000, 99999, 10000 <T> MC <#>Simple <Q> When what is visible to end-users is a deviation from the specific or expect ed behavior, this is called: <C> An error <C> A fault <C+> A failure <C> A defect <T> MC <#>Complex <Q> Which expression best matches the following characteristics or review processes: 1. Led by author 2. Undocumented 3. No management participation 4. Led by a trained moderator or leader 5. Uses entry exit criteria s) Inspection t) Peer review u) Informal review v) Walkthrough <C> s = 4, t = 3, u = 2 and 5, v = 1 <C+> s = 4 and 5, t = 3, u = 2, v = 1 <C> s = 1 and 5, t = 3, u = 2, v = 4 <C> s = 5, t = 4, u = 3, v = 1 and 2 <T> MC <#>Complex <Q> Given the following: Switch PC on Start "outlook" IF outlook appears THEN Send an email Close outlook <C> 1 test for statement coverage, 1 for branch coverage <C+> 1 test for statement coverage, 2 for branch coverage <C> 1 test for statement coverage. 3 for branch coverage

<C> 2 tests for statement coverage, 2 for branch coverage <T> MC <#>Simple <Q> By collecting software metrics and making use of existing software reliabili ty models it is possible to develop meaningful guidelines for determining when s oftware testing is finished. <C+>True <C>False <T> MC <#>Simple <Q> Drivers and stubs are not needed for unit testing because the modules are te sted independently of one another. <C>True <C+>False <T> MC <#>Simple <Q> Test managers should not: <C> Report on deviations from the project plan <C> Sign the system off for release <C+> Re-allocate resource to meet original plans <C> Rise incidents on faults that they have found <T> MC <#>Simple <Q> Which of the following is NOT part of system testing: <C> Performance, load and stress testing <C> Requirements-based testing <C> Usability testing <C+> Top-down integration testing <T> MC <#>Simple <Q> When a new testing tool is purchased, it should be used first by: <C+> A small team to establish the best way to use the tool <C> Everyone who may eventually have some use for the tool <C> The independent testing team <C> The managers to see what projects it should be used in <T> MC <#>Simple <Q> Which of the following is not part of performance testing: <C> Measuring response time <C> Measuring transaction rates <C+> Recovery testing <C> Simulating many users <T> MC <#> Medium <Q> What is the purpose of test completion criteria in a test plan: <C> To know when a specific test has finished its execution <C> To ensure that the test case specification is complete <C> To know when test planning is complete <C+> To plan when to stop testing <T> MC <#>Complex

<Q> Given the following code, which is true: IF A > B THEN C = A B ELSE C = A + B ENDIF Read D IF C = D Then Print "Error" ENDIF <C> 1 test for statement coverage, 3 for branch coverage <C+> 2 tests for statement coverage, 2 for branch coverage <C> 2 tests for statement coverage. 3 for branch coverage <C> 3 tests for statement coverage, 3 for branch coverage <T> MC <#>Simple <Q> Unreachable code would best be found using: <C+> Code reviews <C> Code inspections <C> A coverage tool <C> A test management tool <T> MC <#> Medium <Q> What information need not be included in a test incident report: <C+> How to fix the fault <C> How to reproduce the fault <C> Test environment details <C> Severity, priority <T> MC <#>Simple <Q> Which of the following is NOT included in the Test Plan document of the Test Documentation Standard: <C> Test items (i.e. software versions) <C> What is not to be tested <C> Test environments <C+> Quality plans <T> MC <#>Complex <Q> IEEE 829 test plan documentation standard contains all of the following exce pt: <C> Test deliverables <C> Test tasks <C> Test environment <C+> Test specification <T> MC <#>Simple <Q> Functional testing is mostly <C+> Validation techniques <C> Verification techniques <C> Both of the above <C> None of the above <T> MC <#>Simple <Q> Performance testing is only important for real-time or embedded systems.

<C>True <C+>False <T> MC <#>Simple <Q> Debugging is not testing, but always occurs as a consequence of testing. <C+>True <C>False <T> MC <#>Simple <Q> Branch Coverage <C+> Another name for decision coverage <C> Another name for all-edges coverage <C> Another name for basic path coverage <C> All the above <T> MC <#> Medium <Q> The _________ Is the activity where general testing objectives are transform ed into tangible test conditions and test designs <C> Testing Planning <C> Test Control <C+> Test analysis and design <C> Test implementation <T> MC <#>Simple <Q> Integration testing where no incremental testing takes place prior to all th e system s components being combined to form the system. <C> System testing <C> Component Testing <C> Incremental Testing <C+> Big bang testing <T> MC <#>Simple <Q> A test case design technique for a component in which test cases are designe d to execute statements is called as? <C> State transition Testing <C> Static Testing <C> Transition testing <C+> Statement testing <T> MC <#>Complex <Q> Who should have technical and Business background. <C> Moderator <C> Author <C+> Reviewer <C> Recorder <T> MC <#>Simple <Q> A test plan defines <C> What is selected for testing <C+> Objectives and results

<C> Expected results <C> Targets and misses <T> MC <#>Simple <Q> Component integration testing can be done <C> Before Integration testing <C> After unit testing <C+> After component testing <C> After system testing <T> MC <#> Medium <Q> Test basis documentation is analyzed in which phase of testing <C+> Test Analysis <C> Test Design <C> Test Execution <C> Test Planning <T> MC <#>Simple <Q> Software validation is achieved through a series of tests performed by the u ser once the software is deployed in his or her work environment. <C>True <C+>False <T> MC <#>Simple <Q> Configuration reviews are not needed if regression testing has been rigorous ly applied during software integration. <C>True <C+>False <T> MC <#>Complex <Q> Which one is not the task of test leader? <C> Coordinate the test strategy and plan with project managers and others <C> Decide about the implementation of the test environment <C> Write test summary reports <C+> Review and contribute to test plans <T> MC <#>Simple <Q> if (condition1 && (condition2 function1())) statement1; else statement2; <C> Decision coverage <C+> Condition coverage <C> Statement coverage <C> Path Coverage <T> MC <#> Medium <Q> _________ reviews are often held with just the programmer who wrote the code and one or two other programmers or testers. <C> Formal Reviews <C+> Peer Reviews <C> Semi Formal Reviews <C> All of the above

<T> MC <#>Simple <Q> In ________ testing test cases i.e input to the software are created based o n the specifications languages <C> State Transition Testing <C> Random Testing <C+> Syntax Testing <C> Penetration testing <T> MC <#>Simple <Q> White Box Testing <C> Same as glass box testing <C> Same as clear box testing <C+> Both A. and B. <C> None of the above. <T> MC <#> Medium <Q> Verification activities during design stages are <C+> Reviewing and Inspecting <C> Inspecting and Testing <C> Reviewing and Testing <C> Reviewing, Inspecting and Testing. <T> MC <#>Simple <Q> Equivalence testing divides the input domain into classes of data from which test cases can be derived to reduce the total number of test cases that must be developed. <C+> True <C> False <T> MC <#>Simple <Q> Boundary value analysis can only be used to do white-box testing. <C> True <C+> False <T> MC <#>Simple <Q> Equivalence partitioning consists of various activities: <C+> Ensure that test cases test each input and output equivalence class at leas t once <C> Identify all inputs and all outputs <C> Identify equivalence classes for each input <C> All of the above <T> MC <#>Simple <Q> Static Analysis <C> Same as static testing <C> Done by the developers <C+> Both A. and B <C> None of the above <T> MC

<#> Medium <Q> Size of a project is defined in terms of all the following except <C> Person days <C> Person hours <C+> Calendar months <C> None of the above <T> MC <#>Complex <Q> Testing responsibilities: Tester 1 Verify that the program is able to display images clearly on all 10 of the monitors in the lab Tester 2 - Make sure the program instructions are easy to use Security concerns are important for which type of applications Tester 3 Verify that the calculation module works correctly by using both script s and ad hoc testing. Which term is used to refer to the testing that is performed by Tester 3 in the above scenario? <C> Unit testing <C> Algorithm specific testing <C> Compatibility testing <C+> Black box testing <T> MC <#> Medium <Q> Objective of review meeting is <C> To identify problems with design <C> To solve the problems with design <C+> Both A. and B <C> None of the above. <T> MC <#>Simple <Q> Which is not <C> Planning and <C> Test closure <C> Analysis and <C+> None

the fundamental test process control activities design

<T> MC <#>Simple <Q> The ________ and ________ are used within individual workbenches to produce the right output products. <C> Tools and techniques <C+> Procedures and standards <C> Processes and walkthroughs <C> Reviews and update <T> MC <#>Simple <Q> Which is not the software characteristics <C> Reliability <C> Usability <C+> Scalability <C> Maintainability <T> MC <#>Simple

<Q> The principle of Cyclomatic complexity, considering L as edges or links, N a s nodes, P as independent paths <C+> L-N +2P <C> N-L +2P <C> N-L +P <C> N-L +P <T> MC <#>Simple <Q> With thorough testing it is possible to remove all defects from a program pr ior to delivery to the customer. <C> True <C+> False <T> MC <#>Simple <Q> Program flow graphs are identical to program flowcharts. <C> True <C+> False <T> MC <#>Complex <Q> FPA is used to <C> To measure the functional requirements of the project <C+> To measure the size of the functionality of an Information system <C> To measure the functional testing effort <C> To measure the functional flow <T> MC <#>Simple <Q> A _____ is the step-by-step method followed to ensure that standards are met <C> SDLC <C> Project Plan <C> Policy <C+> Procedure <T> MC <#>Complex <Q> Which is not a test Oracle <C> The existing system (For a bench mark) <C+> The code <C> Individual s knowledge <C> User manual <T> MC <#>Simple <Q> PDCA is known as <C+> Plan, Do, Check, Act <C> Plan, Do, Correct, Act <C> Plan, Debug, Check, Act <C> Plan, Do, Check, Accept <T> MC <#>Simple <Q> Which is the non-functional testing <C+> Performance testing <C> Unit testing <C> Regression testing <C> Sanity testing

<T> MC <#>Complex <Q> A Test Plan Outline contains which of the following: i. Test Items ii. Test Scripts iii. Test Deliverables iv. Responsibilities <C> i,ii,iii are true and iv is false <C+> i,iii,iv are true and ii is false <C> ii,iii are true and i and iv are false <C> i,ii are false and iii , iv are true <T> MC <#>Medium <Q> Software testing activities should start <C> as soon as the code is written <C> during the design stage <C> when the requirements have been formally documented <C+> as soon as possible in the development life cycle <T> MC <#>Medium <Q> Faults found by users are due to: <C> Poor quality software <C+> Poor software and poor testing <C> bad luck <C> insufficient time for testing <T> MC <#>Medium <Q> What is the main reason for testing software before releasing it? <C> to show that system will work after release <C> to decide when the software is of sufficient quality to release <C> to find as many bugs as possible before release <C+> to give information for a risk based decision about release <T> MC <#>Complex <Q> which of the following statements is not true <C> performance testing can be done during unit testing as well as during the te sting of whole system <C> The acceptance test does not necessarily include a regression test <C+> Verification activities should not involve testers (reviews, inspections e tc) <C> Test environments should be as similar to production environments as possibl e <T> MC <#>Simple <Q> When reporting faults found to developers, testers should be: <C> as polite, constructive and helpful as possible <C> firm about insisting that a bug is not a feature if it should be fixed <C> diplomatic, sensitive to the way they may react to criticism <C+> All of the above <T> MC <#>Simple <Q> In which order should tests be run? <C+> the most important tests first

<C> the most difficult tests first(to allow maximum time for fixing) <C> the easiest tests first(to give initial confidence) <C> the order they are thought of <T> MC <#>Medium <Q> The later in the development life cycle a fault is discovered, the more expe nsive it is to fix. why? <C> the documentation is poor, so it takes longer to find out what the software is doing. <C> wages are rising <C+> the fault has been built into more documentation,code,tests, etc <C> none of the above <T> MC <#>Simple <Q> Which is not true-The black box tester <C> should be able to understand a functional specification or requirements docu ment <C+> should be able to understand the source code. <C> is highly motivated to find faults <C> is creative to find the system s weaknesses <T> MC <#>Simple <Q> A test design technique is <C+> a process for selecting test cases <C> a process for determining expected outputs <C> a way to measure the quality of software <C> a way to measure in a test plan what has to be done <T> MC <#>Complex <Q> Testware(test cases, test dataset) <C+> needs configuration management just like requirements, design and code <C> should be newly constructed for each new version of the software <C> is needed only until the software is released into production or use <C> does not need to be documented and commented, as it does not form part of th e released software system <T> MC <#>Simple <Q> An incident logging system <C> only records defects <C> is of limited value <C+> is a valuable source of project information during testing if it contains a ll incidents <C> should be used only by the test team. <T> MC <#>Simple <Q> Increasing the quality of the software, by better development methods, will affect the time needed for testing (the test phases) by: <C+> reducing test time <C> no change <C> increasing test time <C> can t say <T> MC

<#>Simple <Q> Coverage measurement <C> is nothing to do with testing <C+> is a partial measure of test thoroughness <C> branch coverage should be mandatory for all software <C> can only be applied at unit or module testing, not at system testing <T> MC <#>Medium <Q> When should you stop testing? <C> when time for testing has run out. <C> when all planned tests have been run <C+> when the test completion criteria have been met <C> when no faults have been found by the tests run <T> MC <#>Simple <Q> Which of the following is true? <C> Component testing should be black box, system testing should be white box. <C+> if u find a lot of bugs in testing, you should not be very confident about the quality of software <C> the fewer bugs you find,the better your testing was <C> the more tests you run, the more bugs you will find. <T> MC <#>Complex <Q> What is the important criterion in deciding what testing technique to use? <C> how well you know a particular technique <C+> the objective of the test <C> how appropriate the technique is for testing the application <C> whether there is a tool to support the technique <T> MC <#>Complex <Q> If the pseudo code below were a programming language ,how many tests are req uired to achieve 100% statement coverage? 1.If x=3 then 2. Display_messageX; 3. If y=2 then 4. Display_messageY; 5. Else 6. Display_messageZ; 7.Else 8. Display_messageZ; <C> 1 <C> 2 <C+> 3 <C> 4 <T> MC <#>Medium <Q> Using the same code example as question 17,how many tests are required to a chieve 100% branch/decision coverage? <C> 1 <C> 2 <C+> 3 <C> 4

<T> MC <#>Medium <Q> Which of the following is NOT a type of non-functional test? <C+> State-Transition <C> Usability <C> Performance <C> Security <T> MC <#>Simple <Q> Which of the following tools would you use to detect a memory leak? <C> State analysis <C> Coverage analysis <C+> Dynamic analysis <C> Memory analysis <T> MC <#>Medium <Q> Which of the following is NOT a standard related to testing? <C> IEEE829 <C+> IEEE610 <C> BS7925-1 <C> BS7925-2 <T> MC <#>Medium <Q> which of the following is the component test standard? <C> IEEE 829 <C> IEEE 610 <C> BS7925-1 <C+> BS7925-2 <T> MC <#>Medium <Q> which of the following statements are true? <C> Faults in program specifications are the most expensive to fix. <C> Faults in code are the most expensive to fix. <C+> Faults in requirements are the most expensive to fix <C> Faults in designs are the most expensive to fix. <T> MC <#>Simple <Q> Which of the following is not the integration strategy? <C+> Design based <C> Big-bang <C> Bottom-up <C> Top-down <T> MC <#>Simple <Q> Which of the following is a black box design technique? <C> statement testing <C+> equivalence partitioning <C> error- guessing <C> usability testing <T> MC <#>Medium <Q> A program with high cyclometic complexity is almost likely to be: <C> Large

<C> Small <C> Difficult to write <C+> Difficult to test <T> MC <#>Medium <Q> Which of the following is a static test? <C+> code inspection <C> coverage analysis <C> usability assessment <C> installation test <T> MC <#>Simple <Q> Which of the following is the odd one out? <C> white box <C> glass box <C> structural <C+> functional <T> MC <#>Medium <Q> A program validates a numeric field as follows: values less than 10 are rejected, values between 10 and 21 are accepted, values greater than or equal to 22 are rejected which of the following input values cover all of the equivalence partitions? <C> 10,11,21 <C> 3,20,21 <C+> 3,15,22 <C> 10,21,22 <T> MC <#>Medium <Q> A program validates a numeric field as follows:values less than 10 are rejec ted, values between 10 and 21 are accepted, values greater than or equal to 22 a re rejected which of the following covers the MOST boundary values? <C> 9,10,11,22 <C+> 9,10,21,22 <C> 10,11,21,22 <C> 10,11,20,21 <T> MC <#> Medium <Q> We split testing into distinct stages primarily because: <C+> Each test stage has a different purpose. <C> It is easier to manage testing in stages. <C> We can run different tests in different environments. <C> The more stages we have, the better the testing. <T> MC <#> Medium <Q> Which of the following is likely to benefit most from the use of test tools providing test capture and replay facilities? <C+> Regression testing <C> Integration testing <C> System testing <C> User acceptance testing <T> MC

<#>Complex <Q>Which of the following statements is NOT correct? <C> A minimal test set that achieves 100% LCSAJ coverage will also achieve 100% branch coverage. <C> A minimal test set that achieves 100% path coverage will also achieve 100% statement coverage. <C> A minimal test set that achieves 100% path coverage will generally detect m ore faults than one that achieves 100% statement coverage. <C+> A minimal test set that achieves 100% statement coverage will generally det ect more faults than one that achieves 100% branch coverage. <T> MC <#>Simple <Q> When testing object-oriented software it is important to test each class ope ration separately as part of the unit testing process. <C>True <C+>False <T> MC <#>Simple <Q> The focus of validation testing is to uncover places that a user will be abl e to observe failure of the software to conform to its requirements. <C+>True <C>False <T> MC <#>Simple <Q>Which of the following requirements is testable? <C>The system shall be user friendly. <C>The safety-critical parts of the system shall contain 0 faults. <C+>The response time shall be less than one second for the specified design loa d. <C>The system shall be built to be portable.

<T> MC <#> Medium <Q> Error guessing: <C+> supplements formal test design techniques. <C> can only be used in component, integration and system testing. <C> is only performed in user acceptance testing. <C> is not repeatable and should not be used. <T> MC <#> Medium <Q> Which of the following is NOT true of test coverage criteria? <C> Test coverage criteria can be measured in terms of items exercised by a test suite. <C> A measure of test coverage criteria is the percentage of user requirements c overed. <C+>A measure of test coverage criteria is the percentage of faults found. <C> Test coverage criteria are often used when specifying test completion criter ia. <T> <#> <Q> <C> MC Medium In prioritizing what to test, the most important objective is to: find as many faults as possible.

<C+>test high risk areas. <C> obtain good test coverage. <C> test whatever is easiest to test. <T> MC <#>Complex <Q> Given the following sets of test management terms (v-z), and activity descr iptions (1-5), which one of the following best pairs the two sets? v test control w test monitoring x test estimation y incident management z configuration control 1 - calculation of required test resources 2 - maintenance of record of test results 3 - re-allocation of resources when tests overrun 4 - report on deviation from test plan 5 - tracking of anomalous test results <C> v-3,w-2,x-1,y-5,z-4 <C> v-2,w-5,x-1,y-4,z-3 <C+>v-3,w-4,x-1,y-5,z-2 <C> v-2,w-1,x-4,y-3,z-5 <T> MC <#> Medium <Q> Which one of the following statements about system testing is NOT true? <C> System tests are often performed by independent teams. <C> Functional testing is used more than structural testing. <C> Faults found during system tests can be very expensive to fix. <C+>End-users should be involved in system tests. <T> MC <#>Simple <Q> Which of the following is false? <C+>Incidents should always be fixed. <C> An incident occurs when expected and actual results differ. <C> Incidents can be analysed to assist in test process improvement. <C> An incident can be raised against documentation. <T> MC <#> Medium <Q> Enough testing has been performed when: <C> time runs out. <C+>the required level of confidence has been achieved. <C> no more faults are found. <C> the users won t find any serious faults. <T> MC <#> Medium <Q> Which of the following is NOT true of incidents? <C+>Incident resolution is the responsibility of the author of the software unde r test. <C> Incidents may be raised against user requirements. <C> Incidents require investigation and/or correction. <C> Incidents are raised when expected and actual results differ. <T> MC <#>Simple <Q> Graph-based testing methods can only be used for object-oriented systems

<C> True <C+> False <T> MC <#>Simple <Q> Use-cases can provide useful input into the design of black-box and state-ba sed tests of OO software. <C+> True <C> False <T> MR <#>Simple <Q>Which of the following is not described in a unit test standard? <C+> security testing <C> equivalence partitioning <C+>stress testing <C>modified condition/decision coverage

<T> MC <#> Medium <Q> Which of the following is false? <C> In a system two different failures may have different severities. <C+>A system is necessarily more reliable after debugging for the removal of a f ault. <C> A fault need not affect the reliability of a system. <C> Undetected errors may lead to faults and eventually to incorrect behaviour . <T> MC <#> Medium <Q> Which one of the following statements, about capture-replay tools, is NOT co rrect? <C> They are used to support multi-user testing. <C+>They are used to capture and animate user requirements. <C> They are the most frequently purchased types of CAST tool. <C> They capture aspects of user behavior. <T> MR <#> Medium <Q> How would you estimate the amount of re-testing likely to be required? <C+>Metrics from previous similar projects <C+>Discussions with the development team <C> Time allocated for regression testing <C> None of these <T> MC <#>Simple <Q> Which of the following is true of the V-model? <C> It states that modules are tested against user requirements. <C> It only models the testing phase. <C> It specifies the test techniques to be used. <C+>It includes the verification of designs. <T> MC <#>Complex <Q> The oracle assumption: <C> is that there is some existing system against which test output may be che

cked. <C+>is that the tester can routinely identify the correct outcome of a test. <C> is that the tester knows everything about the software under test. <C> is that the tests are reviewed by experienced testers. <T> MC <#> Medium <Q> Which of the following characterizes the cost of faults? <C+>They are cheapest to find in the early development phases and the most expen sive to fix in the latest test phases. <C> They are easiest to find during system testing but the most expensive to f ix then. <C> Faults are cheapest to find in the early development phases but the most e xpensive to fix then. <C> Although faults are most expensive to find during early development phases , they are cheapest to fix then. <T> MC <#>Simple <Q> Recovery testing is a system test that forces the software to fail in a vari ety of ways and verifies that software is able to continue execution without int erruption. <C>True <C+>False <T> MC <#>Simple <Q> Security testing attempts to verify that protection mechanisms built into a system protect it from improper penetration. <C+>True <C>False <T> MC <#> Medium <Q>Which of the following should NOT normally be an objective for a test? <C> To find faults in the software. <C> To assess whether the software is ready for release. <C> To demonstrate that the software doesn t work. <C+>To prove that the software is correct. <T> MR <#> Medium <Q>Which of the following is a form of functional testing? <C+>Boundary value analysis <C>Usability testing <C>Performance testing <C+> State Transition <T> MR <#>Simple <Q>Which of the following would NOT normally form part of a test plan? <C> Features to be tested <C+>Incident reports <C>Risks <C+> BugReport <T> MC <#> Medium <Q> Which of these activities provides the biggest potential cost saving from th

e use of <C> Test <C> Test <C+>Test <C> Test

CAST? management design execution planning

<T> MC <#> Medium <Q> Which of the following is NOT a white box technique? <C> Statement testing <C> Path testing <C> Data flow testing <C+>State transition testing <T> MC <#>Simple <Q> Data flow analysis studies: <C> possible communications bottlenecks in a program. <C> the rate of change of data values as a program executes. <C+>the use of data on paths through the code. <C> the intrinsic complexity of the code. <T> MC <#>Complex <Q> In a system designed to work out the tax to be paid: An employee has 4000 of salary tax free. The next 1500 is taxed at 10% The next 28000 is taxed at 22% Any further amount is taxed at 40% To the nearest whole pound, which of these is a valid Boundary Value Analysis te st case? <C> 1500 <C> 32001 <C+>33501 <C> 28000 <T> MC <#> Medium <Q> An important benefit of code inspections is that they: <C+>enable the code to be tested before the execution environment is ready. <C> can be performed by the person who wrote the code. <C> can be performed by inexperienced staff. <C> are cheap to perform. <T> MC <#> Medium <Q> Which of the following is the best source of Expected Outcomes for User Acc eptance Test scripts? <C> Actual results <C> Program specification <C+>User requirements <C> System specification <T> MC <#>Simple <Q> Stress testing examines the pressures placed on the user during system use i n extreme environments. <C>True <C+>False

<T> MC <#>Simple <Q> The software tester may or may not be involved in the actual acceptance test ing <C+> True <C> False <T> MC <#> Medium <Q> What is the main difference between a walkthrough and an inspection? <C> An inspection is lead by the author, whilst a walkthrough is lead by a trai ned moderator. <C> An inspection has a trained leader, whilst a walkthrough has no leader. <C> Authors are not present during inspections, whilst they are during walkthro ughs. <C+>A walkthrough is lead by the author, whilst an inspection is lead by a train ed moderator. <T> MC <#> Medium <Q> Which one of the following describes the major benefit of verification early in the life cycle? <C> It allows the identification of changes in user requirements. <C> It facilitates timely set up of the test environment. <C+>It reduces defect multiplication. <C> It allows testers to become involved early in the project. <T> MC <#>Simple <Q> Integration testing in the small: <C> tests the individual components that have been developed. <C+>tests interactions between modules or subsystems. <C>only uses components that form part of the live system. <C>tests interfaces to other systems. <T> MC <#> Medium <Q> Static analysis is best described as: <C>the analysis of batch programs. <C>the reviewing of test plans. <C+>the analysis of program code. <C>the use of black box testing. <T> MC <#> Medium <Q> Alpha testing is: <C>post-release testing by end user representatives at the developer s site. <C>the first testing that is performed. <C+>pre-release testing by end user representatives at the developer s site. <C>pre-release testing by end user representatives at their sites. <T> MC <#> Medium <Q> A failure is: <C> found in the software; the result of an error. <C+> departure from specified behavior. <C> an incorrect step, process or data definition in a computer program. <C>a human action that produces an incorrect result. <T> MC

<#>Complex <Q> In a system designed to work out the tax to be paid: An employee has 4000 of salary tax free. The next 1500 is taxed at 10% The next 28000 is taxed at 22% Any further amount is taxed at 40% Which of these groups of numbers would fall into the same equivalence class? <C> 4800; 14000; 28000 <C> 5200; 5500; 28000 <C> 28001; 32000; 35000 <C+>5800; 28000; 32000 <T>MC <#> Medium <Q> The most important thing about early test design is that it: <C> makes test preparation easier. <C> means inspections are not required. <C+> can prevent fault multiplication. <C> will find all faults. <T> MC <#> Medium <Q>Which of the following statements about reviews is true? <C> Reviews cannot be performed on user requirements specifications. <C> Reviews are the least effective way of testing code. <C>Reviews are unlikely to find faults in test plans. <C+> Reviews should be performed on specifications, code, and test plans.

<T> MC <#>Simple <Q> Test cases are designed during: <C> test recording. <C> test planning. <C>test configuration. <C+>test specification. <T> MC <#> Medium <Q> A configuration management system would NOT normally provide: <C> linkage of customer requirements to version numbers. <C+>facilities to compare test results with expected results. <C> the precise differences in versions of software component source code. <C> restricted access to the source code library. <T> MC <#> Medium <Q> A deviation from the specified or expected behavior that is visible to end-u sers is called: <C> an error <C> a fault <C+>a failure <C> a defect <T> MC <#> Medium <Q> Regression testing should be performed: v) every week w) after the software has changed x) as often as possible

y) when the environment has changed z) when the project manager says <C> v & w are true, x, y & z are false <C> w, x & y are true, v & z are false <C+>w & y are true, v, x & z are false <C> w is true, v, x, y & z are false <T> MC <#>Complex <Q> IEEE 829 test plan documentation standard contains all of the following exce pt <C> test items <C> test deliverables <C> test tasks <C+>test specifications <T> MC <#>Simple <Q> When should testing be stopped? <C> when all the planned tests have been run <C> when time has run out <C> when all faults have been fixed correctly <C+>it depends on the risks for the system being tested <T> MC <#> Medium <Q> Order numbers on a stock control system can range between 10000 and 99999 in clusive. Which of the following inputs might be a result of designing tests for only valid equivalence classes and valid boundaries? <C> 1000, 50000, 99999 <C> 9999, 50000, 100000 <C+> 10000, 50000, 99999 <C>10000, 99999, 100000 <T> MC <#> Medium <Q> Consider the following statements about early test design: i.early test design can prevent fault multiplication ii. faults found during early test design are more expensive to fix iii.early test design can find faults iv.early test design can cause changes to the requirements v.early test design normally takes more effort <C+> i, iii & iv are true; ii & v are false <C> iii & iv are true; i, ii & v are false <C> i, iii, iv & v are true; ii is false <C> i & ii are true; iii, iv & v are false <T> MR <#> Medium <Q> Non-functional system testing includes: <C> testing to see where the system does not function correctly <C+>testing quality attributes of the system including performance and usability <C> testing a system function using only the software required for that function <C+>testing the security feature of the product <T> MC <#> Medium <Q> Which of the following is NOT part of configuration management? <C+> auditing conformance to ISO 9000 <C> status accounting of configuration items

<C> identification of test versions <C> controlled library access <T> MC <#> Medium <Q>Which of the following is the main purpose of the integration strategy for in tegration testing in the small? <C>to ensure that all of the small modules are tested adequately <C>to ensure that the system interfaces to other systems and networks <C+>to specify which modules to combine when, and how many at once <C>to specify how the software should be divided into modules <T> MC <#> Medium <Q> What is the purpose of a test completion criterion? <C> to know when a specific test has finished its execution <C> to ensure that the test case specification is complete <C> to set the criteria used in generating test inputs <C+>to determine when to stop testing <T> MC <#> Medium <Q> Consider the following statements: i. an incident may be closed without being fixed. ii.incidents may not be raised against documentation. iii.the final stage of incident tracking is fixing. iv. the incident record does not include information on test environments. <C> ii is true, i, iii and iv are false <C+> i is true, ii, iii and iv are false <C> i and iv are true, ii and iii are false <C> i and ii are true, iii and iv are false