diff options
| author | Théophane Hufschmitt <theophane.hufschmitt@tweag.io> | 2022-05-12 12:02:31 +0200 |
|---|---|---|
| committer | Théophane Hufschmitt <theophane.hufschmitt@tweag.io> | 2022-05-12 12:02:31 +0200 |
| commit | 65a913d29be7305b2c743fb92c93f0e6bb12d610 (patch) | |
| tree | dda43262bcfc3513bef32bbbabdf08180cb46a86 | |
| parent | 7c75f1d52b3078608be29cbe0b009875829cc03f (diff) | |
Don’t recommend writing unit tests
As asked in <https://github.com/NixOS/nix/pull/6517#discussion_r869416905>
| -rw-r--r-- | doc/manual/src/contributing/hacking.md | 3 |
1 files changed, 0 insertions, 3 deletions
diff --git a/doc/manual/src/contributing/hacking.md b/doc/manual/src/contributing/hacking.md index 7ce8d8de6..59ce5cac7 100644 --- a/doc/manual/src/contributing/hacking.md +++ b/doc/manual/src/contributing/hacking.md @@ -87,9 +87,6 @@ $ nix develop Nix comes with three different flavors of tests: unit, functional and integration. -Most tests are currently written as functional tests. -**However**, it is preferable (as much as it makes sense) to primarily test new code with unit tests. - ### Unit-tests The unit-tests for each Nix library (`libexpr`, `libstore`, etc..) are defined |