Differences

This shows you the differences between two versions of the page.

--- unit_test [2025/09/03 13:27] – plida
+++ unit_test [2025/09/10 07:04] (current) – plida
@@ Line 1: / Line 1: @@
+Source: Software Testing course at ITMO university by Kochubeev Nikolay Sergeevich
 ====== Unit tests ======
-Unit tests check individual units of software (be it functions, methods or classes) in isolation from the rest of the system. The goal is to ensure that every module works as intended.
+Unit tests check individual units of software (be it functions, methods or classes) in isolation from the rest of the system. The goal is to ensure that every module works as intended. They're usually placed in a separate from the source code directory.
+==== Concepts ====
+[[test_doubles|Test doubles]] are used to ensure Unit tests are truly isolated.
+[[testing_factory|Factories]], [[testing_builders|builders]] and [[random-based_tests|random-based tests]] are used to generate test data.
+[[property-based_testing|Property-based testing]] is an approach to testing in which we test the properties of a function rather than individual examples.
+[[data-driven_testing|Data-driven testing]] is an approach in which one test function is executed multiple times with different sets of input data.
+[[fixture|Fixture]] is a defined and reliable context for the tests.
 ==== Benefits ======
@@ Line 13: / Line 26: @@
 ==== Principles of good unit tests ====
-  * **FIRST:** Fast, Isolated, Repeatable, Self-validating, Timely;
+  * **[[first|FIRST]]:** Fast, Isolated, Repeatable, Self-validating, Timely;
-  * **AAA:** Arrange, Act, Assert;
+  * **[[arrange_act_assert|AAA]]:** Arrange, Act, Assert;
-  * **GWT:** Given-When-Then.
+  * **[[given_when_then|GWT]]:** Given-When-Then.
 ==== Pros and Cons ====
@@ Line 31: / Line 44: @@
 ==== Popular testing frameworks ====
-  - **JUnit** (Java) -- standard in the ecosystem, annotations, parametrization.
+  - **JUnit** (Java) -- standard in the ecosystem, annotations, parametrization, Maven/Gradle and IDE integration.
-  - **NUnit** (C#) -- flexible attributes, rich assert set.
+  - **NUnit** (C#) -- flexible attributes ([TEST], [TestCase]), rich assert set.
-  - **xUnit** (.NET Core) -- fact/Theory, modern style, .NET CLI integration.
+  - **xUnit** (.NET Core) -- [Fact]/[Theory], modern style, .NET CLI integration.
   - **Go Testing** (Go) -- built-in, minimalistic, table-driven tests.
   - **pytest** (Python) -- fixtures, marking, parametrization, simplicity.