Path Testing

Question 1

Primary applicable to

Answer 1

Component testing

Question 2

When a program is executed

Answer 2

It follows various paths

Question 3

What are we concerned with in path testing

Answer 3

Identifying possible paths through code and identifying test cases with knowledge of possible paths in advance

Question 4

Bug assumption path testing

Answer 4

Assume program either makes right decision at wrong time or makes wrong decision at right time , the wrong path

Question 5

Statement coverage

Answer 5

Most basic
Every statement executed at least once

Question 6

Branch coverage

Answer 6

More refined
Every outcome of every decision executed at least once

Question 7

Coverage measured as percentage

Answer 7

Statement coverage (statements executed / total statements) x 100 easiest to achieve
Branch coverage = (branch outcomes executed / total branch outcomes) * 100
Path coverage = (paths executed / total number of paths) x 100 hardest to achieve

Question 8

Procedure for statement testing

Answer 8

Identify all executable statements
Trace execution from first statement
For each decision encountered choose the true outcome first
Make sure all statements covered, if not keep covering
Repeat above until all statements covered by at least one test case
Record. Variable values required to force execution path you take

Question 9

From paths to test cases

Answer 9

Process of choosing input values is called sensitising the path
Choose easiest pasty’s

Question 10

Statement testing

Answer 10

Executable statements do something
Statement coverage requires you to exercise each statement at least once
Every statement of code executed at least once

Question 11

Decision testing

Answer 11

Excercise all outcomes of decision in code
Reuse test cases for statement and add new ones
Trace on path through code then pick off remaining decisions with new tests

Question 12

Path coverage

Answer 12

Ensures covering all paths from start to end