You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+178-7Lines changed: 178 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,24 +22,33 @@ At the same time, **the Kotest _libraries_, like its assertions, the way it mode
22
22
unrivaled** and don't suffer from the framework's shortcomings. Paired with TestBalloon's flexibility and its small API
23
23
surface, we can get the best of both worlds.
24
24
25
+
26
+
27
+
> [!IMPORTANT]
28
+
> Always explicitly add `de.infix.testBalloon:testBalloon-framework-core`**≥ 0.7.0** to your test dependencies!
29
+
> You will run into an unresolved dependency error otherwise!
30
+
25
31
## Modules
26
32
27
-
This project consists of three modules:
33
+
This project consists of the following modules:
28
34
29
35
*`freespec` emulating Kotest's `FreeSpec` test style for TestBalloon
30
36
*`datatest` replicates Kotest's data-driven testing features for TestBalloon
31
37
*`property` bringing Kotest's property testing to TestBalloon
38
+
*`fixturegen` introducing per-test fixture generation for TestBalloon without boilerplate
39
+
40
+
> [!TIP]
41
+
> `freespec` and `fixturegen` are [modulated](https://github.com/a-sit-plus/modulator) into the `fixturegen-freespec` module, meaning that if you add the
42
+
> `at.asitplus.modulator` gradle plugin to any project that uses both, you can automagically combine FreeSpec syntax
43
+
> and per-test fixture generation! If you don't want to use modulator, you can just add the `at.asitplus.testballoon:fixturegen-freespec:$version`
44
+
> dependency manually to your project.
32
45
33
-
> [!IMPORTANT]
34
-
> Always explicitly add `de.infix.testBalloon:testBalloon-framework-core`**≥ 0.7.0** to your test dependencies!
35
-
> You will run into an unresolved dependency error otherwise!
0 commit comments