L2

Question 1

software dev team members

Answer 1

developer (writes implementation)
tester (writes specification)
and manager

Question 2

4 observations

Answer 2

• specifications must be explicit
• independent dev and testing
• resources are finite
• specifications evolve over time

Question 3

testing checks

Answer 3

consistency between specification and implementation

Question 4

classification of testing approaches

Answer 4

manual/automated vs black box/ white box

Question 5

advantages of automated testing

Answer 5

• find bugs more quickly
• no need to write tests
• no need to maintain tests if software changes

Question 6

advantages of manual testing

Answer 6

• efficient test suite

- potential better coverage (not guarantee)

Question 7

advantages of black box testing

Answer 7

• can work with codes that cannot be modified
• does not need to analyze or study codes
• code can be any format

Question 8

advantages of white box testing

Answer 8

• efficient test suite

- potential better coverage

Question 9

disadvantages of automated testing

Answer 9

• hard to do
• impossible for entire systems
• impossible without specification

Question 10

pre/post conditions

Answer 10

• predicates assumed to hold before/after a function executes
• most useful when they are executable
• need not be precise (may become more complex than the code, but is useful even if they don’t cover every situations)

Question 11

common problems of a test suite

Answer 11

• too few test: may miss bugs

- too many tests: costly to run, bloat, and redundancy, harder to maintain.

Question 12

2 approaches to test suite validation

Answer 12

• code coverage

- mutation analysis (or mutation testing)

Question 13

code coverage

Answer 13

• metric to quantify the extent to which a program code is tested
• measured in % (100% is rare in practice)

Question 14

type of code coverage

Answer 14

• function coverage
• statement coverage
• branch coverage
• and many others

Question 15

mutation analysis

Answer 15

• test variation (mutants) of the program

- the mutant can be equivalent to the original

Question 16

frame conditions

Answer 16

the assumption about everything else outside of the pre/post condition

Question 17

mutation analysis adequates if

Answer 17

mutant fails but the original code passes

Question 18

problem with mutation analysis

Answer 18

if mutant is equivalent to the original