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: docs/src/content/docs/book/debug.mdx
+3-31Lines changed: 3 additions & 31 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -131,48 +131,20 @@ Whenever you create a new [Blueprint][bp] project or use the `blueprint create`
131
131
132
132
### Using generated test stubs {#tests-using-stubs}
133
133
134
-
<Badgetext="Available since Tact 1.6"variant="tip"size="medium"/><p/>
134
+
<Badgetext="Available since Tact 1.6.14"variant="tip"size="medium"/><p/>
135
135
136
136
Tact automatically generates test stubs for each compiled contract during the [compilation process](/book/compile#test-stubs). These generated test files serve as excellent starting points for writing comprehensive tests.
137
137
138
138
To use the generated test stubs:
139
139
140
140
1.**Copy the generated tests** from the `output/tests/` directory to your project's `tests/` directory:
141
-
```shell
142
-
cp -r ./build/tests/ ./tests/
143
-
```
144
141
145
-
2.**Rename the files** to remove the `.stub` suffix:
0 commit comments