Scribd
Upload
52 views

A. As Soon As The Code Is Written

The document discusses various topics related to software testing: 1. Testing activities should start as early as possible in the development lifecycle to find faults early when they are cheapest to fix. 2. Faults found by users are due to poor quality software and insufficient testing. 3. The main reason for testing before release is to find as many bugs as possible and ensure the software is of sufficient quality.

Uploaded by

Mohd Waseem
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
52 views

A. As Soon As The Code Is Written

The document discusses various topics related to software testing: 1. Testing activities should start as early as possible in the development lifecycle to find faults early when they are cheapest to fix. 2. Faults found by users are due to poor quality software and insufficient testing. 3. The main reason for testing before release is to find as many bugs as possible and ensure the software is of sufficient quality.

Uploaded by

Mohd Waseem
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 4

Software testing

1.Software testing activities should start

a. as soon as the code is written


b. during the design stage
c. when the requirements have been formally documented
d. as soon as possible in the development life cycle

2.Faults found by users are due to:

a. Poor quality software


b. Poor software and poor testing
c. bad luck
d. insufficient time for testing

3.What is the main reason for testing software before releasing it?

a. to show that system will work after release


b. to decide when the software is of sufficient quality to release
c. to find as many bugs as possible before release
d. to give information for a risk based decision about release

4. When reporting faults found to developers, testers should be:

a. as polite, constructive and helpful as possible


b. 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
d. All of the above

5.In which order should tests be run?

a. the most important tests first


b. the most difficult tests first(to allow maximum time for fixing)
c. the easiest tests first(to give initial confidence)
d. the order they are thought of

6. The later in the development life cycle a fault is discovered, the more expensive it is to fix.
why?

a. the documentation is poor, so it takes longer to find out what the software is doing.
b. wages are rising
c. the fault has been built into more documentation, code, tests, etc
d. none of the above
7. Which is not true-The black box tester

a. should be able to understand a functional specification or requirements document


b. should be able to understand the source code.
c. is highly motivated to find faults
d. is creative to find the system's weaknesses

8. Increasing the quality of the software, by better development methods, will affect the time
needed for testing (the test phases) by:

a. reducing test time


b. no change
c. increasing test time
d. can't say

9. Coverage measurement

a. is nothing to do with testing


b. is a partial measure of test thoroughness
c. branch coverage should be mandatory for all software
d. can only be applied at unit or module testing, not at system testing

10. When should you stop testing?

a. when time for testing has run out.


b. when all planned tests have been run
c. when the test completion criteria have been met
d. when no faults have been found by the tests run

11. Which of the following is true?

a. Component testing should be black box, system testing should be white box.
b. 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
d. the more tests you run, the more bugs you will find.

12. What is the important criterion in deciding what testing technique to use?

a. how well you know a particular technique


b. the objective of the test
c. how appropriate the technique is for testing the application
d. whether there is a tool to support the technique

13. If the pseudo code below were a programming language ,how many tests are required 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;

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

14. Using the same code example as question 17,how many tests are required to achieve
100% branch/decision coverage?
a. 1
b. 2
c. 3
d. 4

15 Which of the following is NOT a type of non-functional test?

a. State-Transition
b. Usability
c. Performance
d. Security

16. which of the following statements are true?

a. Faults in program specifications are the most expensive to fix.


b. Faults in code are the most expensive to fix.
c. Faults in requirements are the most expensive to fix
d. Faults in designs are the most expensive to fix.

17. Which of the following is not the integration strategy?

a. Design based
b. Big-bang
c. Bottom-up
d. Top-down

18. Which of the following is a black box design technique?

a. statement testing
b. equivalence partitioning
c. error- guessing
d. usability testing

19. Which of the following is a static test?

a. code inspection
b. coverage analysis
c. usability assessment
d. installation test

20. Which of the following is the odd one out?

a. white box
b. glass box
c. structural
d. functional

21. 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?

a. 10,11,21
b. 3,20,21
c. 3,10,22
d. 10,21,22

22. Using the same specifications as question 29, which of the following covers the MOST
boundary values?

a. 9,10,11,22
b. 9,10,21,22
c. 10,11,21,22
d. 10,11,20,21

You might also like