Technical Test-1

Topics: WBT, BBT, Functional Testing, Integration Testing, Smoke Testing, System Testing, Defect Life
Cycle.

1. Where may functional testing be performed?

A. At system and acceptance testing levels only.

B. At all test levels.

C. At all levels above integration testing.

D. At the acceptance testing level only.

2. Who would USUALLY perform debugging activities?

A. Developers. B. Analysts. C. Testers. D. Incident Managers.

3. Which of the following would you NOT usually find on a software incident report?

A. The name and/or organizational position of the person raising the problem.

B. Version of the Software Under Test.

C. Suggestions as to how to fix the problem.

D. Actual and expected results.

4. Given the following fragment of code, how many tests are required for 100% decision coverage?

if width > length

then

biggest_dimension = width

if height > width

then

biggest_dimension = height

end_if

else

biggest_dimension = length

if height > length

then
 biggest_dimension = height

end_if

end_if

A. 3 B. 4 C. 2 D. 1

5. Which of the following combinations correctly describes a valid approach to component testing:

i) Functional testing of the component in isolation.

ii) Structure-based testing of the code without recording incidents.

iii) Automated tests that are run until the component passes.

iv) Functional testing of the interfaces between modules.

A. i and ii.

B. I, ii and iii

C. iii.

D. ii and iv

6. Complete statement and branch coverage means:

A. That you have tested every statement in the program.

B. That you have tested every statement and every branch in the program.

C. That you have tested every IF statement in the program.

D. That you have tested every combination of values of IF statements in the program

7. We can achieve complete statement coverage but still miss bugs because:

A. The failure occurs only if you reach a statement taking the TRUE branch of an IF statement, and you
got to the statement with a test that passed through the FALSE branch.

B. The failure depends on the program's inability to handle specific data values, rather than on the
program's flow of control.

C. We are not required to test code that customers are unlikely to execute.

D. All the above.

8. Bug life cycle

A. Open, Assigned, Fixed, Closed

B. Open, Fixed, Assigned, Closed

C. Assigned, Open, Closed, Fixed

D. Assigned, Open, Fixed, Closed

9. Which of the following techniques is NOT a White box technique?

A. Statement Testing and coverage

B. Decision Testing and coverage

C. Condition Coverage

D. Boundary value analysis

10. Incidents would not be raised against:

A. Requirements

B. Documentation

C. Test cases

D. Improvements suggested by users

11. What's the disadvantage of Black Box Testing

A. Chances of having repetition of tests that are already done by programmer.

B. The test inputs needs to be from large sample space.

C. It is difficult to identify all possible inputs in limited testing time. So writing test cases is slow and
difficult

D. All above

12. ________indicates how important it is to fix the bug and when it should be fixed

A. Severity

B. Priority

C. All of the above

D. None of the above

13. 173: Which of these are objectives for software testing?

A. Determine the productivity of programmers

B. Eliminate the need for future program maintenance

C. Eliminate every error prior to release

D. Uncover software errors

14. Failure is _________

A. Incorrect program behaviour due to a fault in the program

B. Bug found before product Release

C. Bug found after product Release

D. Bug found during Design phase

15. Fault Masking is

A. Error condition hiding another error condition

B. Creating a test case which does not reveal a fault

C. Masking a fault by developer

D. Masking a fault by a tester

16. To test a function, the programmer has to write a _________, which calls the function to be tested
and passes it test data.

A. Stub

B. Driver

C. Proxy

D. None of the above

17. The purpose of requirement phase is

A. To freeze requirements

B. To understand user needs

C. To define the scope of testing

D. All of the above

18. Which of the following is the main purpose of the integration strategy for integration testing in the
small?

A. To ensure that all of the small modules are tested adequately

B. To ensure that the system interfaces to other systems and networks

C. To specify which modules to combine when and how many at once

D. To ensure that the integration testing can be performed by a small team

19. Which of the following will be the best definition for Testing

A. The goal / purpose of testing is to demonstrate that the program works.

B. The purpose of testing is to demonstrate that the program is defect free.

C. The purpose of testing is to demonstrate that the program does what it is supposed to do.

D. Testing is executing Software for the purpose of finding defects.

20. Integration testing in the large involves:

A. Testing the system when combined with other systems.

B. Testing a sub-system using stubs and drivers.

C. Testing a system with a large number of users.

D. Combing software components and testing them in one go.

21. An independent path is the one

A. That is a complete path from source to destination node

B. That is a path which introduces at least one new set of processing statements
C. That is a path which introduces at most one new set of processing statements
D. None of the above

22. Which of the below is NOT a white box testing technique?

A) Statement testing
B) Path testing
C) Data flow testing
D) State transition testing
23. Which testing is concerned with behavior of whole product as per specified requirements?
a) Acceptance testing
b) Component testing
c) System testing
d) Integration testing

24. Verifying that whether software components are functioning correctly and identifying the defects in
them is objective of which level of testing?
a) Integration testing
b) Acceptance testing
c) Unit testing
d) System Testing

25. Which of the following is/are structural testing technique?

a) Statement Coverage
b) Decision Coverage
c) Condition & Path Coverage
d) All of these

26. Defect reports are useful as they contain

a) defect description
b) Priority
c) Summary
d) All of the above

27. What is not true about priority?

a) Priority is impact of defect on business
b) Priority can be urgent, high, medium, low
c) Priority once assigned cannot be changed.
d) All of the above

28. Who determines the severity of bug?

a) Developer
b) Customer
c) Tester
d) All stakeholders

29. Which testing is performed first?

a) Smoke
b) Sanity
c) Depending upon project one can select first for execution
d) simultaneously
30. Testing helps to
a) Fix defect
b) Improve quality
c) Measure quality
d) All of the above

31. In which of the following situations can we say there is a defect?

a) A requirement is not implemented
b) A requirement is wrongly implemented
c) Something extra is implemented which is not specified in URS
d) All of the above

32. If rigorous testing is done on software and no defects are detected , can we say the the software is
100% bug free?
a) Yes
b) No
c) Depends on tester's skills
d) insufficient data

33. Bug status is set to postpone due to

a. Priority of that bug may low.
b. Lack of time for the release.
c. The bug may not be the major effect in the software.
d. Data may be unavailable.

34. ________ calls the function and passes it test data.

a. Test Stub
b. Test Driver
c. Proxy
d. None of the above

35. ______ is an existing defect that has not yet caused a failure because the conditions that is
required to invoke the defect is not meet.
a. Masked defect
b. Latent defect
c. Both of these
d. None of these

36.