@vttforge/testing 0.3.0 → 0.3.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +6 -0
- package/README.md +4 -4
- package/package.json +2 -2
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,11 @@
|
|
|
1
1
|
# @vttforge/testing
|
|
2
2
|
|
|
3
|
+
## 0.3.1
|
|
4
|
+
|
|
5
|
+
### Patch Changes
|
|
6
|
+
|
|
7
|
+
- 7eeeb20: Rewrite the npm package descriptions to say what each package does today. `types` claimed full schema inference it does not have, `vite-plugin` claimed Handlebars HMR that lives in the dev loop, and `cli` did not mention `audit`.
|
|
8
|
+
|
|
3
9
|
## 0.3.0
|
|
4
10
|
|
|
5
11
|
### Minor Changes
|
package/README.md
CHANGED
|
@@ -23,20 +23,20 @@ foundry.restore();
|
|
|
23
23
|
```
|
|
24
24
|
|
|
25
25
|
`withMockFoundry` installs `foundry`, `game`, `CONFIG`, `Hooks`, `ui` and
|
|
26
|
-
`CONST`, and hands back a handle that records what your code registered
|
|
27
|
-
settings, notifications
|
|
26
|
+
`CONST`, and hands back a handle that records what your code registered (hooks,
|
|
27
|
+
settings, notifications) so a test can assert on what happened rather than only
|
|
28
28
|
on what did not throw. `restore()` puts every global back, including deleting the
|
|
29
29
|
ones that never existed.
|
|
30
30
|
|
|
31
31
|
The mock documents behave like real ones where it counts: `update` merges rather
|
|
32
|
-
than replacing, and dotted paths expand. Both matter
|
|
32
|
+
than replacing, and dotted paths expand. Both matter: a mock that replaces lets
|
|
33
33
|
a test pass while the real thing drops every sibling key.
|
|
34
34
|
|
|
35
35
|
### Naming the globals
|
|
36
36
|
|
|
37
37
|
A test that reads `game.settings` would otherwise get "Cannot find name
|
|
38
38
|
'game'". Importing from this entry declares them, so there is nothing to
|
|
39
|
-
configure
|
|
39
|
+
configure. The import a test already writes is what brings them.
|
|
40
40
|
|
|
41
41
|
## `@vttforge/testing/quench`
|
|
42
42
|
|
package/package.json
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@vttforge/testing",
|
|
3
|
-
"version": "0.3.
|
|
4
|
-
"description": "
|
|
3
|
+
"version": "0.3.1",
|
|
4
|
+
"description": "Foundry mocks for Vitest and Quench helpers, for testing VTTForge systems and modules.",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"license": "MIT",
|
|
7
7
|
"homepage": "https://github.com/vttforge/vttforge#readme",
|