Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
36 changes: 18 additions & 18 deletions apps/cookbook/docs/angular/02-glossary.md
Original file line number Diff line number Diff line change
Expand Up @@ -75,9 +75,13 @@ The System Under Test is the code or system that is being tested. It is the part

Originally defined by Kent Beck, [Test Desiderata](https://testdesiderata.com/) is a set of properties we wish for our tests to have. The challenge is that some of these properties are incompatible with each other by nature, which means that we have to make trade-offs when designing our tests.

#### Isolated
#### Automated

Tests should return the same results regardless of the order in which they are run.
Tests should run without human intervention.

#### Behavioral

Tests should be sensitive to changes in the behavior of the code under test. If the behavior changes, the test result should change.

#### Composable

Expand All @@ -91,37 +95,33 @@ If nothing changes, the test result shouldn’t change.

Tests should run quickly.

#### Writeable

Tests should be cheap to write relative to the cost of the code being tested.

#### Readable
#### Inspiring

Tests should be comprehensible for the reader, invoking the motivation for writing this particular test.
Passing the tests should inspire confidence.

#### Behavioral
#### Isolated

Tests should be sensitive to changes in the behavior of the code under test. If the behavior changes, the test result should change.
Tests should return the same results regardless of the order in which they are run.

#### Structure-Insensitive
#### Predictive

Tests should not change their result if the structure of the code changes.
If the tests all pass, then the code under test should be suitable for production.

#### Automated
#### Readable

Tests should run without human intervention.
Tests should be comprehensible for the reader, invoking the motivation for writing this particular test.

#### Specific

If a test fails, the cause of the failure should be obvious.

#### Predictive
#### Structure-Insensitive

If the tests all pass, then the code under test should be suitable for production.
Tests should not change their result if the structure of the code changes.

#### Inspiring
#### Writeable

Passing the tests should inspire confidence.
Tests should be cheap to write relative to the cost of the code being tested.

## Test-Driven Development _(TDD)_

Expand Down
Loading