A. Parameter type mismatches.

B. Errors in requirements.

C. Undeclared variables.

D. Uncalled functions.

A. Number of undetected defects.

B. Total number of defects in the product.

C. Number of test cases not yet executed.

D. Effort required to fix all defects.

A. $4000; $5000; $5500.

B. $32001; $34000; $36500.

C. $28000; $28001; $32001.

D. $4000; $4200; $5600.

A. i, iii, iv.

B. i, ii, iii.

C. ii, iv, v.

D. ii, iii, v.

A. After the software or system has been produced.

B. During development.

C. As early as possible.

D. During requirements analysis.

A. Expected outcomes are defined by the software's behaviour

B. Expected outcomes are derived from a specification, not from the code

C. Expected outcomes should be predicted before a test is run

D. Expected outcomes may include timing constraints such as response times

A. Testing that the system functions with other systems

B. Testing that the components that comprise the system function together

C. Testing the end to end functionality of the system as a whole

D. Testing the system performs functions within specified response times

A. Operating systems

B. Test documentation

C. Live data

D. User requirement documents

A. Setting up forms and databases

B. Analysing metrics and improving processes

C. Writing the documents to be inspected

D. Time spent on the document outside the meeting

A. Black box test design techniques all have an associated test measurement technique

B. White box test design techniques all have an associated test measurement technique

C. Cyclomatic complexity is not a test measurement technique

D. Black box test measurement techniques all have an associated test design technique

A. To find faults in the software

B. To prove that the software has no faults

C. To give confidence in the software

D. To find performance problems

A. Component testing

B. Non-functional system testing

C. User acceptance testing

D. Maintenance testing

A. Walkthrough

B. Inspection

C. Management review

D. Post project review

A. Updating tests when the software has changed

B. Testing a released system that has been changed

C. Testing by users to ensure that the system meets a business need

D. Testing to maintain business advantage

A. I,ii,iii are true and iv is false

B. i,iii,iv are true and ii is false

C. ii,iii are true and i and iv are false

D. i,ii are false and iii , iv are true

A. Desk check

B. Manual support testing

C. Walkthrough

D. Compiler based testing

A.I, II &III

B.I, II &IV

C.II, III&IV

D.I, III&IV

A. Equivalence partitioning

B. Boundary value analysis

C. Decision table

D. Hybrid analysis

A. I, II and III

B. I, II and IV

C. II, III and IV

D. I, III and IV

A. Baseline identification

B. Configuration auditing

C. Change control

D. Version control

A. System Testing

B. Big-Bang Testing

C. Integration Testing

D. Unit Testing

A. Tell to the development team to deliver the system in time so that testing activity will be finish in time.

B. Extend the testing plan, so that you can accommodate the slip going to occur

C. Rank the functionality as per risk and concentrate more on critical functionality testing

D. Add more resources so that the slippage should be avoided

A. Integrity, Response time

B. Concurrency test, Scalability

C. Update & Rollback, Response time

D. Concurrency test, Integrity

A. Error Guessing

B. Boundary Value Analysis

C. Decision Table testing

D. Equivalence partitioning

A. Statement coverage usually requires more test case suites

B. 100 % statement coverage guarantees 100 % decision coverage

C. 100 % decision coverage implies 100 % statement coverage

D. Decision tables cannot be used to list statement coverage values

A. It includes functional testing

B. It includes loop testing

C. It is usually done after black-box testing

D. It is usually done during the integration testing phase

A. Horizontal tracebility

B. Depth tracebility

C. Vertical tracebility

D. Horizontal & Vertical tracebilities

A. 5

B. 4

C. 2

D. 3

A. Regression testing

B. Inter system testing

C. Re-testing

D. Integration testing

A. I, II&III

B.II, III&IV

C.I, II&IV

D.I, III&IV

A. Narrow band Delphi

B. Wide band Delphi

C. Bespoke Delphi

D. Robust Delphi

A. A high level document describing the principles, approach and major objectives of the organization regarding testing

B. A distance set of test activities collected into a manageable phase of a project

C. A test environment comprised of stubs and drives needed to conduct a test

D. A set of several test cases for a component or system under test

A. Preventing the defects by inspection

B. Fixing the defects by debugging

C. Adding known defects by seeding

D. A process of fixing the defects by tester

A. Establish a relationship with the customer

B. Learn the project objectives and the existing project plan

C. Modify the project' s organizational structure to meet the manager's management style

D. Ensure that the project proceeds at its current pace

A. Water fall model

B. Spiral model

C. Incremental model

D. V-Model

A. The extent to which the software can be used in other applications

B. The extent to which the software can be used by many different users

C. The capability of the software to be moved to a different platform

D. The capability of one system to be coupled with another system

A.I, II&III

B.II, III &IV

C.I, III &IV

D.I, II & IV

A. I and II only

B. II and III only

C. I and III only

D. I, II and III

A. The number of defects identified in a component or system divided by the size of the component or the system

B. The number of defects found by a test phase divided by the number found by that test phase and any other means after wards

C. The number of defects identified in the component or system divided by the number of defects found by a test phase

D. The number of defects found by a test phase divided by the number found by the size of the system

A. Exploratory testing

B. Usability testing

C. Component testing

D. Maintainability testing