Lecture 7

Question 1

Unit Testing (UT)

Answer 1

Tests that verify the functionality of individual/specific units of code, usually written by devs as they work on code, to ensure that specific functions are working as expected.

Question 2

[UT] Benefits

Answer 2

• Find problems early on
• Simplifies Integration and integration testing later
• Provides living documentation of a new system

Question 3

[UT] Case Structure (and the acronym!)

Answer 3

S.E.V.C

• Setup (put UUT in state needed to run the test)
• Execute (trigger UUT target behavior, capture all output)
• Validation (ensure test results are correct)
• Cleanup (restore UUT to pre-test state to allow for immediate test execution)

Question 4

[UT] Characteristics

Answer 4

F.R.O.M SLC. FC. C.A.M

• FAST
• READABLE
• ORDER doesn’t matter
• MEMORY-ran
• SINGLE LOGICAL CONCEPT tested
• FULL CONTROL over all running processes
• CONSISTENTLY returns same result
• ABLE to be fully automated
• MAINTAINABLE

Question 5

[UT] Outcomes

Answer 5

• 1+ assert statements to validate specific outcomes

- Verify that no/a particular exception was (not) thrown

Question 6

[UT] Substitutes

Answer 6

Unit Test substitutes are used to assist in testing a module in isolation.

• Method Stub: a stand-in piece of code for some programming functionality
• Mock Object: a simulated object that mimics the behavior of real objects in controlled ways
• Test Harness

Question 7

Integration Testing (IT)

Answer 7

any type of software testing that seeks to verify the interfaces between units or components against a software design.

works to expose defects in the interfaces and interaction between integrated components (aka modules)

Question 8

IT vs UT

Answer 8

Integration:

• coarse-grained
• complex
• test intricate web of calls
• slow
• can’t run in an IDE

Unit:

• fine-grained
• simple
• test single API call
• fast
• easy to run in an IDE

Question 9

Test Driven Development (TDD)

Answer 9

Software development process that relies in the repetition of a very short dev cycle

Question 10

[TDD] Cycle

Answer 10

1) Dev writes an initially failing automated test case, defining a desired improvement or new functionality
2) Dev produces minimum amount of code to pass that test
3) Def refactors the new code to acceptable standards

Question 11

[TDD] Benefits

Answer 11

• Dev is concerned with the interface before implementation
• Dev focuses on making the test pass ONLY, not exceptional cases, error handling, etc
• Early and frequent testing, obviously
• Code produced is more modularized, flexible

Question 12

Code/Test Coverage (C/T C)

Answer 12

A measure that describes the degree to which source code of a program is tested by a particular test suite. High code coverage means it’s been thoroughly tested and a lower chance of software bugs.

Tests include: U.A.I.R (unit, automated, integrated, regression)

Question 13

[C/T C] Types

Answer 13

• Functional
• Statement
• Branch
• Path

Question 14

[C/T C] Functional Coverage

Answer 14

has each function (subroutine) in the program been called?

Question 15

[C/T C] Statement Coverage

Answer 15

Minimum number of paths in which all nodes are covered

Question 16

[C/T C] Branch Coverage

Answer 16

Minimum number of paths in which all edges are covered

Question 17

[C/T C] Path Coverage

Answer 17

Number of all paths, from start to end

Question 18

Cyclomatic Complexity (CC)

Answer 18

Software measurement that indicates program complexity. The number of linearly independent paths through a program’s source code.

Question 19

[CC] Formula

Answer 19

CC = E-N + 2