roever engineering college - perambalur, … - software... · roever engineering college elambalur,...

ROEVER ENGINEERING COLLEGE ELAMBALUR, PERAMBALUR- 621 212

DEPARTMENT OF INFORMATION TECHNOLOGY

REC SEM VIII Sy & QB

CS1016 - SOFTWARE TESTING

UNIT I TESTING BASICS 8 Testing as an engineering activity – Role of process in software quality – Testing as a process – Basic

definitions – Software testing principles – The tester’s role in a software development organization –

Origins of defects – Defect classes – The defect repository and test design – Defect examples –

Developer / Tester support for developing a defect repository. UNIT II TEST CASE DESIGN 11 Introduction to testing design strategies – The smarter tester – Test case design strategies – Using

black box approach to test case design – Random testing – Equivalence class partitioning – Boundary

value analysis – Other black box test design approaches – Black box testing and COTS – Using white

box approach to test design – Test adequacy criteria – Coverage and control flow graphs – Covering

code logic – Paths – Their role in white box based test design – Additional white box test design

approaches

– Evaluating test adequacy criteria.

UNIT III LEVELS OF TESTING 9 The need for levels of testing – Unit test – Unit test planning – Designing the unit tests – The class

as a testable unit – The test harness – Running the unit tests and recording results – Integration tests–

Designing integration tests – Integration test planning – System test – The different types –

Regression testing – Alpha, beta and acceptance tests. UNIT IVTEST MANAGEMENT 9 Basic concepts – Testing and debugging goals and policies – Test planning – Test plan components –

Test plan attachments – Locating test items – Reporting test results – The role of three groups in test

planning and policy development – Process and the engineering disciplines – Introducing the test

specialist – Skills needed by a test specialist – Building a testing group. UNIT V CONTROLLING AND MONITORING 8 Defining terms – Measurements and milestones for controlling and monitoring – Status meetings –

Reports and control issues – Criteria for test completion – SCM – Types of reviews – Developing a

review program – Components of review plans – Reporting review results. Total: 45

TEXT BOOKS 1. Ilene Burnstein, “Practical Software Testing”, Springer International Edition, 2003. 2. Renu Rajani and Pradeep Oak, “Software Testing – Effective Methods, Tools and Techniques”,

Tata McGraw Hill, 2003.

1


SUBJECT CODE: CS1016 SUBJECT NAME: SOFTWARE TESTING UNIT- I INTRODUCTION

PART –A (1 MARK) 1.To check whether we are developing the right product according to the customer requirements are not. It is a static process. a. Validation b. Verification c. Quality Assurance d. Quality Control 2.To check whether we have developed the product according to the customer requirements or not. It is a Dynamic process. a. Validation b. Verification c. Quality Assurance d. Quality Control 3.Staff development plan describes how the skills and experience of the project team members will be developed. a. True b. False 4.It is a set of levels that defines a testing maturity hierarchy. a. TIM (Testing Improving Model) b. TMM (Testing Maturity Model)

c. TQM (Total Quality Management) 5.A Non-Functional Software testing done to check if the user interface is easy to use and

understand. a. Usability Testing b. Security Testing c. Unit testing d. Block Box Testing 6.The review and approved document (i.e. Test plan, System Requirement Specification’s) is called as a. Delivery Document b. Baseline Document c. Checklist 7.It measures the quality of processes used to create a quality product. It is a system of

management activities, it is a preventive process, it applies for entire life cycle and deals with process.

a. Validation b. Verification c. Quality Assurance d. Quality Control

8.Variance from product specifications is called

a. Report b. Defect c. Requirement

9.Verification is

a. Process based b. Product based 10. Requirement and Analysis, Design, Development or Coding, Testing and Maintenance is

called as Software Development Life Cycle (SDLC)

a. False b. True

11. Phase Definition. It will come under

a. CMM Level 1 b. None c. CMM Level 2

12. The process that deals with the technical and management issues of software development

called as

a. Delivery Process b. Software Process c. Testing Process 13. Earlier a defect is found the cheaper it is to fix it. Is the above statement correct?

2


a. No b. Yes

14. Informing to the developer which bug to be fix first is called as

a. Traceability b. Priority c. Fixability d. Severity 15. Software Testing is a process of evaluating a system by manual or automatic means and

verify that it satisfies specified requirements or identity differences between expected and actual results. a. False b. True 16. SPICE Means a. Software Process Improvement and Capability Determination

b.Software Process Improvement and Control Determination c.

Software Process Invention and Compatibility Determination. d.Software Process Improvement and Compatibility Determination 17. It provides a set of levels and an assessment model, and presents a set of recommended

practices that allow organizations to improve their testing processes.

a. TQM (Total Quality Management) b. TMM (Testing Maturity Model)

c.TIM (Testing Improving Model)

18. Defects generally fall into the following categories.

a. All the below b. MISSING c. EXTRA d. WRONG

19. What is correct Software Process Cycle?

a. Plan (P)

-

-

--

-

- >Check(C) ------ >Act (A.

-

-

-

-

- >Do (D)

b.Plan (P) ------ >Do (D) ------ >Act (A. ----- >Check(C)

c. Plan (P) ------ >Do (D) ------ >Check(C) ----- >Act (A.

20. Integration, It will come under

a. CMM Level 1 b. None c. CMM Level 2 d. CMM Level 3

Answers:

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20

b a a b a b c b a b c b b b b a c a c d

PART –B (2 MARKS)

21. Compare validation and verification. (AU-MAY/JUNE’11)

a. Validation is the process of evaluating a software system or component during or at the end of the

development cycle in order to determine whether it satisfies specified requirements. Validation is

usually associated with traditional execution based testing, that is, exercising the code with test cases. b. To determine whether the products of a given development phase satisfy the conditions imposed

at the start of that phase. It is associated with activities such as inspections & reviews of s/w

deliverables.

22. Define software quality. (AU-APR/MAY 2008) Quality relates to the degree to which a system, system component, or process meets specified

requirements. Quality relates to the degree to which a system, system component, or process meets

3

customer or user needs, or expectations.

23. Define process in the context of software quality. (AU-NOV/DEC 2009) Process, in the software engineering domain, is the set of methods, practices, standards, documents,

activities, policies, and procedures that software engineers use to develop and maintain a software

system and its associated artifacts, such as project and test plans, design documents, code, and

manuals. 24. Define testing. Testing is generally described as a group of procedures carried out to evaluate some aspect of a piece

of software. Testing can be described as a process used for revealing defects in software, and for

establishing that the software has attained a specified degree of quality with respect to selected

attributes. 25. Write some of the benefits of test process improvement. •Smarter testers Higher quality software •The ability to meet budget and scheduling goals •Improved planning The ability to meet quantifiable testing goals 26. Describe error, defect and failure. An error is a mistake, misconception, or misunderstanding on the part of a software developer. A fault (defect or bugs) is introduced into the software as the result of an error. It is an anomaly in the

software that may cause it to behave incorrectly, and not according to its specification.

A failure is the inability of a software system or component to perform its required function within

specified performance requirements. 27. What is meant by test case? The usual approach to detecting defects in a piece of software is for the tester to select a set of input

data and then execute the software with the input data under a particular set of conditions. The tester

bundles this information into an item called a test case. 28. What is meant by test? a) A set of test inputs: These are data items received from an external source by the code under test.

The external source can be hardware, software, or human.

b) Execution conditions: These are conditions required for running the test, for example, a certain

state of a database, or a configuration of a hardware device.

c) Expected outputs: These are the specified results to be produced by the code under test. 29. Describe test oracle and test bed. A test oracle is a document or piece of software that allows testers to determine whether a test has

been passed or failed.

A test bed is an environment that contains all the hardware and software needed to test a software

component or a software system. 30. What is quality metric? A quality metric is a quantitative measurement of the degree to which an item possesses a given

quality attribute. 31. List out the quality attributes.

Correctness Reliability Usability Integrity

Portability Maintainability Interoperability Testability

4

REC SEM VIII Sy & QB 32. State some of the important test related issues. • There is a demand for software of high quality with low defects • Process is important in the software engineering discipline • Software testing is an important software development sub process • Existing software evaluation and improvement models have not adequately addressed

testing issues. 33. What is meant by maturity goals? The maturity goals identify testing improvement goals that must be addressed in order to achieve

maturity at that level. To be placed at a level, an organization must satisfy the maturity goals at that

level. 34. What is meant by ATR’s? Activities, Tasks and Responsibilities (ATR). The ATRs address implementation and organizational

adaptation issues at each TMM level. Supporting activities and tasks are identified, and

responsibilities are assigned to appropriate groups. 35. What is SQA? The software quality assurance group is a team of people with the necessary training and skills to

ensure that all necessary actions are taken during the development process so that the resulting

software conforms to established technical requirements. 36. What is meant by principle? A principle can be defined as: • A general or fundamental, law, doctrine, or assumption; A rule or code of conduct; • The laws or facts of nature underlying the working of an artificial device. 37. What are the four major classes of defects? (AU-MAY/JUN 2009) (AU-MAY/JUNE’11) Defects are assigned to four major classes reflecting their point of origin in the software life cycle –

the development phase in which they were injected. These classes are: •Requirements / specification defects Design defects, Code defects, Testing defects

PART –C

(16MARKS)

38. Give the internal structure of TMM and explain about its maturity goals at each level.

(AU-APR/MAY 2008)

39. Explain in detail about principles of software testing. (AU-NOV/DEC 2009) 40. Explain the following: i) Explain the tester’s role in a software development organization

ii) Origin of defects (AU-NOV/DEC 2009)

41. Explain in detail about defect classes, the defect repository, and test design. (AU-NOV/DEC 09) 42. Why is it important to meticulously inspect test result? Give example. (AU-MAY/JUN 2009) 43. Discuss the drawbacks incase if you fail to inspect. (AU-MAY/JUN 2009) 44. Why is it necessary to develop test cases for both valid and invalid input condition?( AU-

MAY/JUN2009)

5

REC SEM VIII Sy & QB 45. How important is document for product? How will you test requirement and design

document? (AU-MAY/JUN 2009)

46. Explain “Testing as a Process” with suitable example. (AU-APR/MAY’11) 47. Briefly discuss the tester’s role in a Software Development Organization. (AU-

MAY/JUNE’11)

UNIT-II TEST CASE DESIGN PART –A (1 MARK)

48. A useful tool to visualize, clarify, link, identify, and classify possible cause of a problem.

This is also called as “fishbone diagram” what is this?

a. Pareto Analysis b. Cause-and-Effect Diagram

49. White box testing is not called as___________

a. Glass box testing b. Clear box testing

c. Open box testing d. Closed box testing

50. The testing which is done by going thro' the code is known as

a. Unit testing b. Regression testing c. White box Testing d. Black box testing 51. This type of testing method attempts to find incorrect or missing functions, errors in data

structures or external database access, interface errors, Performance errors and initialization

and Termination errors. It is called as a. White Box Testing b. Grey Box Testing c. Open Box Testing d. Black Box Testing 52. Boundary value analysis belongs to which testing method? a. White Box testing b. Black Box testing c. Grey Box Testing d. Open box testing

53. A metric used to measure the characteristic of documentation and code called as

a. Process metric b. Test metric c. Product Metric

54. Which is Black-Box Testing method?

a. Equivalence partitioning b. Fault injection c. Code coverage

55. This Testing Technique examines the basic program structure and it derives the test data

from the program logic; Ensuring that all statements and conditions executed at least once called as

a. Closed Box testing b. White box testing c. Grey Box Testing d. Black box Testing

56. ------------- means under what test environment (Hardware, software set up) the application

will run smoothly

a. Checklist b. Checkpoint c. Code Walk through d. Test Bed 57. The testing technique that requires devising test cases to demonstrate that each program function is operational is called a. Black-box testing b. Glass-box testing c. Grey-box testing d. White-box testing 58. The testing technique that requires devising test cases to exercise the internal logic of a

software module is called a. behavioral testing b. black-box testing c. grey-box testing d. white-box testing

59. The cyclomatic complexity metric provides the designer with information regarding the

number of

6


a. cycles in the program b. errors in the program

c. independent logic paths in the program d. statements in the program

60. Condition testing is a control structure testing technique where the criteria used to design

test cases is that they

a. rely on basis path testing b. exercise the logical conditions in a program module c. select test paths based on the locations and uses of variables d. focus on testing the validity of loop constructs 61. Data flow testing is a control structure testing technique where the criteria used to design

test cases is that they a. rely on basis path testing b. exercise the logical conditions in a program module c. select test paths based on the locations and uses of variables d. focus on testing the validity of loop constructs 62. Loop testing is a control structure testing technique where the criteria used to design test cases is that they a. rely basis path testing b. exercise the logical conditions in a program module c. select test paths based on the locations and uses of variables d. focus on testing the validity of loop constructs 63. Black-box testing attempts to find errors in which of the following categories a. incorrect or missing functions b. interface errors

c. performance errors d. all of the above e. none of the above 64. 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.

a. True b. False

65. Boundary value analysis can only be used to do white-box

testing. a. True b. False

66. Test case design "in the small" for OO software is driven by the algorithmic detail of the individual operations.

a. True b. False

67. Scenario-based testing

a. concentrates on actor and software interaction b. misses errors in specifications

c. misses errors in subsystem interactions d. both a and b

Answers:

48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67

b d c d b c a b d a d c b c d d a b a a

PART –B (2

MARKS)

68. When we say test case is effective? ƒ A greater possibility of detecting defects. ƒ A more efficient use of organizational resources

7


ƒ A higher probability for test reuse ƒ The possibility for delivery of a higher quality software product 69. What are the two basic strategies used in test cases? There are two basic strategies that can be used to design test cases. These are i. Black Box ii. White Box

70. What is Black Box approach? Using this approach a tester considers the software under test to be an opaque box. There is no

knowledge of its inner structure. The tester only has no knowledge of what it does. The size of the

software using this approach can vary from a simple module, member function or object cluster to a

sub system or a complete software system. 71. What is white box approach? (AU-APR/MAY 2008) This approach focuses on the inner structure of the software to be tested. To design the test cases, the

tester must have knowledge of the structure. The code or a suitable pseudo code like representation

must be available. The tester selects test cases to exercise specific internal structural elements to

determine if they are working properly. 72. What are control flow graphs? (AU-NOV/DEC 2009) (AU-MAY/JUN 2009) Control flow graph is a graph that contains number of nodes represents sequential statements, as well

as decision and looping predicates. For simplicity, sequential statements are often omitted or

combined as a block that indicates that if the first statement in the block is executed, so are all the

following statements in block are executed. 73. Describe the following axioms. (AU-APR/MAY 2008) Monotonicity: If a test set T is adequate for program P, and if T is equal to, or a subset of T_, then

T_ is adequate for program P. Antiextensionality: There are programs P and Q such that P is equivalent to Q, and T is adequate

for P, but T is not adequate for Q.

74. What is random test? (AU-NOV/DEC 2009) (AU-MAY/JUNE’11) Each software module or system has an input domain from which test input data is selected. If a

tester randomly selects input from the domain, this is called random test 75. What are the conditions that are used in input specification?

i.It must consist of alpha numeric characters ii.The range for the total number of characters is between 3 and 15

iii.The first two characters must be letters. Steps for designing test cases.

iv.First we will identify input equivalence classes and give them each an identifier

v.Then we will augment these with the results from boundary value analyzes

vi.The tables will be used to organize and record our findings\ vii.Each will also be categorized as valid or invalid for the input domain 76. Describe usage profile and certification. The usage profiles are characterization of the population of intended uses of the software in its

intended environment. Certification refers to third party assurance that a product, process or service

meets a specific set of requirements 77. Write the application scope of test adequacy criteria.

8

REC SEM VIII Sy & QB 1.Helping testers to select properties of a program to focus on during test. 2.Helping testers to select test data set for a program based on the selected

properties 3.Supporting testers with the development of quantitative objectives for

testing 4.Indicating to testers whether or not testing can be stopped for that program 78. What is test data? (AU-MAY/JUNE’11) A test data set is a statement or branch, adequate if a test set T for a program P causes all the

statements or branches to be executed respectively. 79. What is meant by path? A path is a sequence of control flow nodes usually beginning from the entry node of a graph through

to the exit node

80. What is mutation test? It is another approach to test data generation that requires knowledge of the code structure but it is

classified as a fault based testing approach. It considers the possible faults that could occur in a

software component as the basis for test data generation and evaluation of testing effectiveness. 81. What is test set? A test set T is said to mutation adequate for program P provided that for every equivalent mutant Pi

of P there is an element ‘t’ in T such that Pi(t) is not equal P(t) 82. What is equivalence class partitioning? If a tester is viewing the software under test as black box with well defined inputs and outputs, a

good approach to select test input is to use a method called equivalence class partitioning. 83. What is boundary value analysis? The equivalence class partitioning gives the tester a useful tool with which to develop black box

based test cases for the software under test. The test cases developed based on equivalence class

partitioning can be strengthened by the use of a technique called boundary value analysis. 84. What is meant by STG chart?

i.STG / state chart are useful models of software behavior ii.These are commonly depicted by a set of nodes which represent states.

iii.These usually will have a name or number to identify the state.

iv.A set of arrows between the nodes indicate what inputs or events will cause a transition or

change between the two linked states. 85. What is state transition testing? It is useful for both procedural and object oriented development. It is based on the concept of states

and finite state machines and allows the tester to view the developing software in terms of its states,

transition between the states and the inputs and events that trigger state changes. 86. Write down the two major assumption of mutation testing. a) The competent programmer hypothesis: This states that a competent programmer writes programs

that are nearly correct

b) The coupling effect : This effect relates to questions a tester might have about how well mutation

testing can detect complex errors since the changes made to the code are very simple

9

REC SEM VIII Sy & QB 87. What is an axiom? Testers can use the axiom to recognize both strong and weak adequacy criteria; a tester may decide

to use a weak criterion, but should be aware of its weakness with respect to the properties described

by the axiom. It focuses attention on the properties that an effective test data adequacy criterion

should exhibit. PART –C

(16MARKS) 88. Explain about the following methods of black box testing with example:

i) Equivalence class partitioning ii) Boundary value analysis iii) Write a note on COTS components (AU-NOV/DEC 2009)

89. Explain the following black box test design approaches: i) Cause-and-effect graphing ii) State transition testing iii) Error guessing 90. Explain about the following methods of white box testing with example:

i) Test adequacy criteria ii) Coverage and control flow analysis

iii) Covering code logic (AU-NOV/DEC 2009)

91. Write a note on the following: i) Loop testing ii) Mutation testing 92. Explain in detail about to evaluate test adequacy criteria. 93. Explain briefly about path and cyclomatic complexity. (AU-APR/MAY 2008) 94. Develop black-box test cases using equivalence class partitioning and boundary value

analysis to test a module for ATM system. (AU-MAY/JUN 2009)

95. Imagine yourself as a developer of flight control system. Describe any three test

adequacy criteria you would consider applying to develop test cases for flight control system.

(AU-MAY/JUN 09) 96. Explain Black Box Testing and Commercial Off the Shelf (COTS) Components. (AU-

MAY/JUNE’11) 97. How to evaluate Test Adequacy Criteria of an application? (AU-MAY/JUNE’11)

UNIT-III LEVELS OF TESTING

PART –A (1 MARK)

98. What are the Testing Levels?

a. Unit Testing b. Integration Testing

c. System Testing and Acceptance Testing. d. All the above

99. Software testing which is done without planning and Documentation is known as

a. adhoc Testing b. Functional testing. c. Regression testing d. Unit Testing

100. Acceptance testing is known as

a. Beta Testing b. Grey box testing c. White box testing d. Test Automation

101. Retesting the entire application after a change has been made called as?

a. Retesting b. Unit Regression c. Regional Regression d. Full Regression Testing

102. What are the Types of Integration Testing?

a. Big Bang Testing b. All the above c. Top down testing d. Bottom up Testing 103. A metric used to measure the characteristic of documentation and code called as

10


a. Process metric b. Test metrics c. Product Metric 104. Which is non-functional software testing? a. Unit testing b. Regression testing c. Performance testing d. Block box testing 105. Executing the same test case on a modified build called as a. Regression testing b. Re testing c. Sanity testing d. Ad hoc Testing 106. Which is Black-Box Testing method?

a. Equivalence partitioning b. Fault injection c. Code coverage

107. Automation Testing should be done before starting manual testing.

Is the above statement correct?

a. No b. Yes 108. An Important metric is the number of defects found in internal testing compared to the

defects found in customer tests, Status of test activities against the plan, Test coverage achieved

so far, comes under

a. Process Metric b. Test Metric c. Product Metric

109. Alpha testing will be done at

a. Developers' site b. User's site 110. This type of test includes, how well the user will be able to understand and interact with the system

a. Beta Testing. b. User Acceptance Testing c. Alpha Testing d. Usability Testing

111. Defects generally fall into the following categories

a. All the below b. MISSING c. EXTRA d. WRONG 112. Conducted to validate that the application, database, and network they may be running on

can handle projected volumes of users and data effectively. The test is conducted jointly by

developers, testers, DBA’s and network associates after the system Testing called as a. Functional Testing b. Integration Testing c. Recovery Testing d. Stress/Load Testing 113. Which Software Development Life cycle model will require starting Testing Activities when starting development activities itself?

a. Spiral Model b. V-model c. Linear model d. Water fall model

114. A metric used to measure the characteristic of the methods, Techniques and tools

employed in developing, implementing and maintaining the software system called as

a. Test metric b. Product Metric c. Process metric

115. The name of the testing which is done to make sure the existing features are not affected

by new changes

a. Regression testing b. White box testing c. Unit testing d. Recursive testing

116. Unit testing will be done by

a. Testers b. End Users c. Developers d. Customer

117. Beta testing will be done at

a. Developers place b. User place

Answers:

98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117

d a a d b c c a a a b a d a d b c a c b

11


PART –B (2 MARKS)

118. What is unit testing? It is the smallest possible testable software component. It can be characterized in several ways. For

examples a unit in a typical procedure oriented software system: • performs a single cohesive function • can be compiled separately • is a task in a work breakdown structure • contains code that can fit on a single page or screen 119. List the tasks for unit test. a. plan the general approach to unit testing b. design the test cases and test procedures c. define relationships between the test d. prepare the auxiliary code necessary for unit test 120. What is meant by test harness? The auxiliary code developed to support testing of units and components is called a test harness. It

consists of drivers that call the target code and stubs that represent modules it calls. 121. What are the two major goals considered for integration testing? (MAY/JUNE’11)

a. To detect defects that occurs on the interfaces of units. b. To assemble the individual units into working sub systems and finally the complete system that

is ready for system test 122. What is meant by cluster? A cluster consist of classes that are related for example they may work together to support a required

functionality for the complete system

123. What is system test? System testing itself requires a large amount of resources. The goal is to ensure that the system

performs according to its requirements. The system test evaluates both functional behavior and

quality requirements such as reliability, usability, performance and security. 124. What are the types of system test available?

i.Functional testing ii.Performance testing iii.Stress testing

iv.Configuration testing v.Security testing viRecovery testing

vii.Reliability testing viii.Usability testing 125. What is meant by load and transaction? A load is a series of inputs that simulates a group of transactions. The transaction is a unit of work

seen from the system user’s view. A transaction consists of a set of operations that may be performed

by a person, software systems or a device that is outside the system. The use case can be used to

describe a transaction. 126. What is functional testing?

12

REC SEM VIII Sy & QB The functional test is black box in nature. The focus is on the inputs and proper outputs for each

function. Improper and illegal input must be handled by the system. All functions must be tested. 127. What is performance testing? The goal of system performance test is to see, if the software meets the performance requirements.

The testers also learn from performance test whether there are any hardware or software factors that

impact on the systems performance. This testing allows tester to tune the system; that is, to optimize

the allocation of system resources. 128. What is stress testing? When a system is tested with a load that causes it to allocate its resources in maximum amount, this is

called stress testing. For example if an operating system is required to handle 10 interrupt / sec and

the load causes 20 interrupt/sec, the system is being stressed. The goal of this test is to try to break the

system. This is sometimes called breaking the system. 129. What are the objectives of configuration testing?

i. Show that all the configuration changing commands and menus work properly. ii. Show that all interchangeable devices are really interchangeable, and that they each enter the

proper states for the specified condition

iii. Show that the systems’ performance level is maintained when devices are interchanged, or when

they fail. 130. What is security testing? Security testing evaluates systems characteristics that relates to availability, integrity and

confidentiality of the system data & services. Users or clients should be encouraged to make sure

their security needs are clearly known at requirements time, so that security issues can be addressed

by designers and testers. 131. What is recovery testing? Recovery testing subjects a system to losses of resources in order to determine if it can recover

properly from these losses. This type of testing is especially important for transaction systems, for

example, on-line banking software. 132. What is installation test? (AU-APR/MAY 2008) If the client’s site conditions are different from that of the developers, the developers must set up the

system so that it can interface with client software and hardware. Retesting may have to be done to

ensure that the software works as required in the client’s environment. This is called installation test.

133. What is regression testing? (AU-NOV/DEC 2009) It is not a level of testing, but it is the retesting of software that occurs when changes are made to

ensure that the new version of the software has retained the capabilities of the old version and that no

new defects have been introduced due to the changes. 134. What is alpha testing? (AU-MAY/JUNE’11) If the software has been developed for the mass market, then testing it for individual clients or users is

not practical or even possible in most cases. Very often this type of software undergoes two stages of

acceptance test. The first is called alpha testing. 135. What is beta testing?

13

REC SEM VIII Sy & QB Beta test sends the software to a cross section of users who install it and use it under real world

working conditions. The users send the records of problems with the software to the development

organization where the defects are repaired sometimes in time for the current release. 136. What is acceptance testing? Acceptance test must be rehearsed by the developers or testers. There should be no signs of

unprofessional behavior or lack of preparation. Clients do not appreciate surprises. The client should

be received in the development organization as respected guest. They should be provided with

documents and other materials to help them participate in the acceptance testing process and to

evaluate the results. 137. What are the issues to be considered in adequate test plan? Phase I: Identifies completeness requirements Phase II: Identifies unit features to be tested

Phase III: Add levels of details to the plan PART –C (16 MARKS)

138. Explain the various units in a program considered for unit testing. (AU-NOV/DEC 2009) 139. Explain the planning, design and execution of unit tests. (AU-NOV/DEC 2009) 140. Explain the integration testing in detail.

141. Explain in detail about the various types of system testing. (AU-NOV/DEC 2009)

142. Discuss the need for various levels of testing. (AU-NOV/DEC 2009)

143. Discuss the importance of following:

i. Security testing

ii. Alpha testing

iii. Beta testing

iv. Acceptance testing (AU-APR/MAY 2008) 144. Describe “The Class as a Testable Unit” in detail. (AU-MAY/JUNE’11)

145. Explain the types of System Tests in detail. (AU-MAY/JUNE’11)

UNIT-IV TEST MANAGEMENT PART –A (1 MARK)

146. The approach/document used to make sure all the requirements are covered when

writing test cases a. Test Matrix b. Checklist c.Traceability Matrix d. Test bed 147. Executing the same test case by giving the number of inputs on same build called

as a. Regression Testing b. Retesting c. Sanity Testing d. Ad hoc Testing

148. Control Charts is a statistical technique to assess, monitor, and maintain the stability of

a process. a. True b. False

149. Cost of quality = Prevention Cost + Appraisal cost + Failure

cost a. True b. False

150. Retesting of a single program or component after a change has been made? a. Full Regression Testing b. Retesting c. Regional Regression d. Unit Regression

14

REC SEM VIII Sy & QB 151. Configuration Management Plan describes the Configuration Management procedures and structures to be used.

a. False b. True

152. Business Risk affects The Organization developing or Procuring the software.

a. False b. True 153. Stratification is a Technique used to analyze/divide a universe of data into homogeneous groups (strata). a. False b. True 154. Standards and procedures for managing changes in an evolving software product are called as a. Confirmation Management b. Confederation Management

c. Compatibility Management d. Configuration Management

155. Path Tested = Number of Path Tested / Total Number of Paths

a. False b. True 156. Maintenance Plan predicts the maintenance requirements of the system, maintenance costs and effort required

a. False b. True 157. Check Sheet (Checklist) is considered a simple, but powerful statistical tool because

it differentiates between two extremes. a. False b. True 158. Application should be stable. Clear Design and Flow of the application is needed for Automation testing. a. True b. False 159. Quality plan describes the quality procedures and standards that will be used in a project. a. True b. False

160. How severely the bug is effecting the application is called as

a. Severity b. Traceability c. Fix ability d. Priority

Answers:

146 147 148 149 150 151 152 153 154 155 156 157 158 159 160

c b a a d b b b d b b b a a a

PART–B (2MARKS)

161. What is goal? A goal can be described as a statement of intent, or a statement of a accomplishment that an

individual or an organization wants to achieve. 162. What is meant by policy? A policy can be defined as a high-level statement of principle or course of action that is used to

govern a set of activities in an organization. 163. What is test plan? A plan is a document that provides a framework or approach for achieving a set of goals. 164. What is milestone?

15

REC SEM VIII Sy & QB Milestones are tangible events that are expected to occur at a certain time in the project’s lifetime.

Managers use them to determine project status. 165. What is meant by feature? Features may be described as distinguishing characteristics of a software component or system. 166. What is meant by WBS? A Work Breakdown Structure is a hierarchical or tree like representation of all the tasks that are

required to complete a project. 167. List down the responsibilities of test related task. •Transmitting the software-under-test; Developing test design specifications, and test cases; •Executing the tests and recording results; Tracking and monitoring the test efforts; •Checking results; Interacting with developers; Managing and providing equipment; •Developing the test harnesses; Interacting with the users/customers; •This group may include developers, testers, software quality assurance staff, system analysts, and

customers / users.

168. What is meant test cost? Test costs that should include in the plan are: • Costs of planning and designing the tests; • Costs of acquiring the hardware and software necessary for the tests; • Costs to support the test environment;Costs of executing the tests; • Cost of recording and analyzing test results 169. Enumerate the key characteristics of test cost impact system. 1. The nature of the organization, its testing maturity level and general maturity 2. The nature of the software product being developed 3. The scope of the test requirements 4. The level of the tester ability 5. Knowledge of the project problem domain 6. The level of tool support and training requirements

170. What is cost driver? A cost driver can be described as a process or product factor that has an impact on overall project

cost. 171. Write a note on COCOMO model. (AU-APR/MAY 2008) Project constant and cost drivers are available for overall project development effort. To use the

COCOMO model, a project manager must first estimate the size of the new project and identify its

type. This is facilitated by the availability of historical project data. 172. Write down the elements of WBS used in testing. i. Project startup ii. Management coordination iii. Tool Selection iv. Test planning v. Test design vi. Test development vii.Test execution viii. Test measurement & monitoring

16

REC SEM VIII Sy & QB ix. Test analysis and reporting x. Test process improvement 173. What is meant by test transmittal report? • It consist of version / revision number of the item • Location of the item • Person responsible for the item • Reference to the item documentation and test plan it is related to • Status of the item • Approvals – space for signature of staff that approve the transmittal. 174. What is test log? (AU-MAY/JUNE’11) The test log should be prepared by the person executing the tests. It is a diary of the events that take

place during the test. It supports the concept of a test as a repeatable experiment. In the experimental

world of engineers and scientists detailed logs are kept when carrying out experimental work.

Software engineers and testing specialists must follow this example to allow others to duplicate their

work. 175. Write down the skills needed by a test specialist. (AU-NOV/DEC 2009) On the personal and managerial level a test specialist must have: • Organizational and planning skill • The ability to keep track of, and pay attention to, details; • The determination to discover and solve problems • The ability to work with others and be able to resolve conflicts • The ability to mentor and train others 176. What is test summary report contains? i.Test summary ii. Variances iii. Comprehensiveness assessment iv. Summary of results v. Evaluation vi. Summary of activities vii. Approval

PART –C (16 MARKS) 177. Explain the testing and debugging goals and policies. 178. Explain the following:

i. Test planning ii. Test plan components (AU-NOV/DEC 2009)

179. Explain the test plan attachments in detail. (AU-NOV/DEC 2009) 180. What are the documents needed to report the test results. 181. Describe the role of the three critical groups in test planning & policy development. (AU-

NOV/DEC 09)

182. Describe the steps in forming a test group. (AU-NOV/DEC 2009) (AU-APR/MAY 2008) 183. Why is testing plan important for developing a repeatable and managed testing process?

Give example. (AU-MAY/JUN 2009)

184. Explain in brief about test cost impact items. (AU-APR/MAY 2008)

17

REC SEM VIII Sy & QB 185. Explain elaborately about the basic test plan components as described in IEEE 829-1983. 186. Explain the following:

i.Introducing the test specialist

ii.Skills needed by a test specialist

iii.Building a testing group (AU-NOV/DEC 2009) 187. Discuss in detail the Test Plan Components. (AU-MAY/JUNE’11) 188. Explain the skills needed by a Test Specialist. (AU-MAY/JUNE’11)

UNIT-V CONTROLLING AND MONITORING

PART –A (1 MARK)

189. Management and Measurement, It will come under

a. CMM Level 1 b. CMM Level 2 c. CMM Level 4 d. CMM Level 3

190. Adhoc testing is a part of

a. Unit Testing b. Performance Testing c. Exploratory Testing d. Regression Testing

191. Cost of Production = Right the First time cost (RTF) + Cost of Quality.

a. False b. True

192. Optimization, Defect Prevention, and Quality Control. It’s come under the

a. CMM Level 2 b. CMM Level5 c. CMM Level 4 d. CMM Level 3

193. A Plan to overcome the risk called as

a. Migration Plan b.Mitigation Plan c. Maintenance plan d. Master plan 194. Splitting project into tasks and estimate time and resources required to complete each task called as Project Scheduling a. False b. True 195. With thorough testing it is possible to remove all defects from a program prior to delivery to the customer.

a. True b. False

196. Which of the following are characteristics of testable software?

a. observability b. simplicity c. stability d. all of the above 197. What types of errors are missed by black-box testing and can be uncovered by white-box

testing? a. behavioral errors b. logic errors c. performance error d. typographical errors e. both b

and d 198. Program flow graphs are identical to program

flowcharts. a. True b. False

199. Loop testing is a control structure testing technique where the criteria used to design test cases is that they a. rely basis path testing b. exercise the logical conditions in a program module c. select test paths based on the locations and uses of variables d. focus on testing the validity of loop constructs

18


200. Tests derived from behavioral class models should be based on the

a. data flow diagram b. object-relation diagram

c. state diagram d. use-case diagram

201. Multiple class testing is too complex to be tested using random test cases.

a. True b. False

202. Deep structure testing is not designed to

a. examine object behaviors b. exercise communication mechanisms

c. exercise object dependencies d. exercise structure observable by the user

203. Scenario-based testing

a. concentrates on actor and software interaction b. misses errors in specifications

c. misses errors in subsystem interactions d. both a and b

204. Testing OO class operations is made more difficult by

a. encapsulation b. inheritance c. polymorphism d. both b and c

205. Fault-based testing is best reserved for

a. conventional software testing b. operations and classes that are critical or suspect

c. use-case validation d. white-box testing of operator algorithms

206. Boundary value analysis can only be used to do white-box testing.

a. True b. False 207. 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.

a. True b. False

208. Which of these techniques is not useful for partition testing at the class level

a. Attribute-based partitioning b. Category-based partitioning

c. Equivalence class partitioning d. State-based partitioning

Answers:

189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208

c c b b b b b d e b d c b d a d b b a c

PART –B (2 MARKS)

209. What is project monitoring? (AU-APR/MAY 2008) The project monitoring refers to the activities and task managers engage in to periodically check the

status of each project. Reports are prepared that compare the actual work done to the work that was

planned. 210. What is project controlling?

It consists of developing and applying a set of corrective actions to get a project on track when monitoring shows a deviation from what was planned. 211. List out the major task for controlling the project monitoring. (AU-MAY/JUNE’11) 1.develop standards of performance

2.plan each project

3.establish a monitoring and reporting system

19

REC SEM VIII Sy & QB 4.measure and analyze results 5.initiate corrective action for projects that are off

track 6.reward and discipline

7.document the monitoring and controlling mechanism

8.utilize a configuration management system 212. What are mile stones?

Mile stones are tangible events that are expected to occur at a certain time in the project life time.

The managers use them to determine project status. 213. Write down the key elements used for monitoring. i. Testing status ii. Tester productivity iii. Testing cost iv. Errors, faults and failures 214. What are the elements used for black box measures? •Number of requirements or features to be tested •Number of equivalence classes identified •Number of equivalence classes actually covered •Number or degree of requirements or features actually covered 215. Write down the measures used for test execution. •Number of available test cases executed •Number of available test cases executed and passed •Number of unplanned test cases executed •Number of unplanned test cases executed and passed 216. Write down the measures used for test regression. •Number of planned regression test executed •Number of planned regression test executed and passed 217. Write down the measures for test harness.

The size is a measure that is usually applied by managers to help estimate the amount of effort

needed to develop a software system. Size is measured in many different ways for example, lines of

code, function points and feature points. 218. List the measures for test monitoring. •Time spent in test planning Time spent in test case design •Time spent in test execution Time spent in test reporting •Number of test cases developed Number of test cases executed 219. List the measures for test productivity. Productivity for a tester could be estimated by a combination of: •Number of test cases developed / unit time •Number of tests executed / unit time •Number of LOC test harness developed / unit time •Number of defects detected in testing / unit time 220. How does the fault, error monitoring helps?

Monitoring errors, faults and failures is very useful for:

20

REC SEM VIII Sy & QB •Evaluating product quality; Evaluating testing effectiveness; •Making stop-test decisions; Defect casual analysis; •Defect prevention; Test process improvement; •Development process improvement; 221. What is test effectiveness? Test effectiveness measurements will allow managers to determine if test resources have been used

wisely and productively to remove defects and evaluate product quality. Test effectiveness

evaluations allow managers to learn which testing activities are or are not productive. 222. What is milestone meeting event? A milestone meeting is an important event; it is a mechanism for the project team to communicate

with upper management and in some cases user / client groups. 223. What does a test report contain? •Activities and accomplishments during the reporting period •Problems encountered since the last meeting period •Problems solved •Outstanding problems •Current project state versus plan •Expenses versus budget •Plans for the next time period 224. List down the major activities of CM. •Identification of the configuration items •Change control •Configuration status reporting •Configuration audits 225. What is baseline? Base lines are formally reviewed and agreed upon versions of software artifacts, from which all

changes are measured. They serve as the basis for further development and can be changed only

through formal change procedures. Base lines plus approved changes from those base lines constitute

the correct configuration identification for the item. 226. List down the items for audit. •Compliance with software engineering standards •The configuration change procedure, Related configuration items, Reviews 227. What are the tester’s role in controlling and monitoring? i) Collecting and analyzing test measurements, Participation in test status meetings ii) Training in tools and methods for test process monitoring and controlling, including configuration

management, Serving as members of the change control board

iii) Completing follow-up activities for corrective actions iv) Preparing test-related documents such as test logs and test incident

reports v) Contributing to test summary report 228. What are users and client’s role in controlling and monitoring?

21

REC SEM VIII Sy & QB i) Attendance at special test milestone meetings. If the software is being developed for a specific

client, the development organization may invite a user / client group to attend a test milestone

meeting to show progress. ii) Stop-test criteria for acceptance test. In the case of software custom built for a specific client, the

client should be asked to give input on stop-test criteria that indicate the completeness of acceptance

test.

iii) Test effectiveness. If an organization is measuring test-effectiveness using post release problem

reports, the users / client will play an important role in reporting problems and insuring they are

returned to the proper personnel in the development organization. 229. Define testing. •Testing is generally described as a group of procedures carried out to evaluate some aspect of a

piece of software. •Testing can be described as a process used for revealing defects in software and for establishing that

the software has attained a specified degree of quality with respect to selected attributes.

230. Define review. (AU-NOV/DEC 2009) (AU-MAY/JUNE’11) A review is a group meeting whose purpose is to evaluate a software artifact or a set of software

artifacts. 231. Expand and define SCM. (AU-NOV/DEC 2009) SCM means Software Configuration Management (SCM). Software systems are constantly

undergoing change during development and maintenance. By software systems we include all

software artifacts such as requirements and design documents, test plans, user manuals, code, and test

cases. Different versions, variations, builds, and release exist for these artifacts. 232. List down the goals of reviewer. •Identify problem components or components in the software artifact that need improvement •Identify components of the software artifact that do not need improvement •Identify specific errors or defects in the software artifact •Ensure that the artifact conforms to organizational standards 233. Write down the benefits of review program. (AU-APR/MAY 2008) •Higher-quality software Increased productivity •Closer adherence to project schedules Increased awareness of quality issues •Teaching tool for junior staff Opportunity to identify reusable software artifacts •Reduced maintenance costs Higher customer satisfaction •More effective test planning •A more professional attitude on the part of the development staff. 234. What are the types of reviews?

Reviews can be formal or informal. They can be technical or managerial. Managerial reviews usually focus on project management and project status. These are used to: •Verify that a software artifact meets its specification •To detect defects •Check for compliance to standards. 235. List the components of review plan.

22


i.Review goals ii.Item being reviewed iii.Preconditions for the review

iv.Roles, team size, participants v.Training requirements vi.Review step

vii.Check lists and other related documents to be disturbed to participants

viii.Time requirements ix.The nature of the review log and summary report

x.Rework and follow-up 236. List the preconditions to be reviewed. •The review of items is a required activity in the project plan •A statement of objectives for the review has been developed •The individuals responsible for developing the reviewed item indicate readiness for the review •The review leader believes that the item to be reviewed is sufficiently complete for the review to be useful.

PART –C (16 MARKS) 237. Explain the measurement and milestones for monitoring and controlling. 238. Explain the status meetings, reports and control issues. 239. Explain the four major activities associated with configuration management. (NOV 2009) 240. Explain the criteria for test completion. (AU-NOV/DEC 2009) 241. Write a summary about the following types of reviews:

i) Requirement reviews ii) Design reviews (AU-APR/MAY 2008) 242. Explain the three critical views of controlling and monitoring. 243. Write a note on five stop test criteria based on quantitative approach. (AU-APR/MAY

2008) 244. If you are developing a patient record system for health care center, why of the stop

test will be most appropriate for this system? (AU-MAY/JUN 2009) 245. What is the role of the tester in supporting, monitoring and controlling of testing?( AU-

MAY/JUN 09)

246. Explain the following: i.Types of reviews ii.Developing a review program (AU-NOV/DEC09)

247. Explain the components of review plans in detail. (AU-NOV/DEC 2009)

248. Discuss the Criteria for Test Completion. (AU-MAY/JUNE’11)

249. Explain the various types of Reviews. (AU-MAY/JUNE’11)

23

roever engineering college - perambalur, … - software... · roever engineering college elambalur,...

Documents