07 Unit Testing Part 2

Question 1

Test-Driven Development (TDD)

Answer 1

A software development process where a unit’s test are written before the unit’s implmentation and guide the unit’s development as the tests are executed repeatedly until they are all succeed.

Question 2

Refactoring

Answer 2

Process of restructuing existing computer code without changing its external behavior.

Improve nonfunctional attributes of the software.

Question 3

TDD Process Steps

Answer 3

Red:
- Write new tests
- Verify failure of new tests and success of existing tests.

Green:
- Write Code to implement, modify, or develop the unit.
- Repeat until the tests pass.

Refactor:
- Refactor the code
- Confirm tests pass.

Repeat

Question 4

Unit Testing

Answer 4

A test that invokes a small, testable unit of work in a software system and then checks a single assumption about the resulting output or behavior.

Form of white box testing, focusing on implementation details.

Uses Coverage criteria as the exit criteria.

Question 5

Unit Testing Tools

Answer 5

Test Framework
Test Runner
Mocks
Coverage Reporter

Question 6

Test Framework

Answer 6

Defines the test writing syntax.

Question 7

Test Runner

Answer 7

• Executes all (or subset) of the system’s unit tests and present,s displays or otherwise output the results.
• Might also spin up mocks, a virtual environment, or any other resources the test require.
• Often a basic tesyt runner is built into the test framework.

Question 8

Mocks

Answer 8

Provides a “mock” or simulated implementation of each external dependency or resources required by the methods being tested.

May return random, dummy, or cached data.

Question 9

Coverage Reporter

Answer 9

Determines and provides a report on the test coverage metrics.

Might run independently or during each test executed by a test runner.