Changes for page Tips and Tricks

Last modified by chrisby on 2024/04/01 13:11

From version 1.27

edited by chrisby
on 2023/10/25 20:15

Change comment: There is no comment for this version

To version 1.28

edited by chrisby
on 2023/11/28 23:29

Change comment: There is no comment for this version

Summary

Page properties

Content

@@ -6,7 +6,7 @@
  * Don't reinvent the wheel and **use existing test libraries**. There are proven solutions that minimize the effort of creating tests.
  * Use a common **test structure convention** by dividing the test logic into three parts
  *1. **given** (a context → setting up data, fields, and objects)
--*1. **when** (something happens → execute production code)
++*1. **when** (something happens → define behavior of mocks and execute production code)
  *1. **then** (a certain outcome is expected → check the result via assertions)
  ** Alternative common names for the three steps: **arrange, act, assert**
  * Use additional **simple high-level checks**. For example, when working with a collection, checking the number of items before examining an item from the collection in detail is a good indicator of unexpected or missing items.