---
url: /reference/typescript/wow-view-engine/symbols-testing.md
description: >-
  Every name @ahoo-wang/wow-view-engine/testing exports, generated from its
  TSDoc.
---

# @ahoo-wang/wow-view-engine/testing symbol index

Every name `@ahoo-wang/wow-view-engine/testing` exports — 15 — with its kind and the first sentence of its TSDoc, generated from the built declarations. 15 of them are described by hand in the curated pages, linked in the last column; the rest are read from their source through the signature in the [API report](https://github.com/Ahoo-Wang/Wow/blob/main/typescript/wow-view-engine/test/api/testing.api.md). This index is English only.

::: v-pre

| Symbol | Kind | Summary | Covered in |
|---|---|---|---|
| `ActionHarness` | interface | A host's declared actions over some records, without a screen (host-integration.md 6): the engine's own reading of them — which place offers which, whether a record takes one now and why not, how a selection splits, what the confirmation and the form ask, when the rules change on their own — so a host's unit test pins its business rules in a line each. | [Testing Helpers](./testing#api-actionHarness) |
| `ActionHarnessOptions` | interface | — | [Testing Helpers](./testing#api-actionHarness) |
| `ActionRefusedError` | class | A record the engine did not send the command to, because the action refused it when it came to its turn. | [Testing Helpers](./testing#api-actionHarness) |
| `Admissible` | type | What `admit` takes one of: a definition, or a resource holding one — the shape a host registers (host-integration.md 4), so a host's list of resources is passed as it is, sources and all. | [Testing Helpers](./testing#api-admit) |
| `AdmitFinding` | type | One finding, with the definition it is about. | [Testing Helpers](./testing#api-admit) |
| `AdmitOptions` | interface | — | [Testing Helpers](./testing#api-admit) |
| `HarnessBulk` | interface | One action over a selection, as the selection's bar and its dialog read it. | [Testing Helpers](./testing#api-actionHarness) |
| `HarnessField` | interface | One field of an action's form, as the dialog draws it. | [Testing Helpers](./testing#api-actionHarness) |
| `HarnessState` | interface | One action on one record, as the row, the menu and the detail draw it. | [Testing Helpers](./testing#api-actionHarness) |
| `MemorySourceOptions` | interface | How `memorySource` keeps and reads its documents. | [Testing Helpers](./testing#api-memorySource) |
| `actionHarness` | function | — | [Testing Helpers](./testing#api-actionHarness) |
| `admit` | function | Every finding the engine would have about `definitions` over`descriptors` (the snapshots, by `DataViewDefinition.source`), each with the definition it is about; `[]` for a host's declarations that hold. | [Testing Helpers](./testing#api-admit) |
| `matches` | function | Whether one document matches a filter, as `memorySource` reads it — the question a test asks of a condition of its own, such as the one an old screen used, to compare with what a view matched. | [Testing Helpers](./testing#api-memorySource) |
| `memorySource` | function | A `ViewSource` over documents held in memory that answers each query the way a Wow service over MongoDB does — filter, sort, page, projection and aggregation — so a host's test sees the engine's real queries answered by the semantics the engine is built on, not a canned answer. | [Testing Helpers](./testing#api-memorySource) |
| `resolveNavigation` | function | `to` through the route of the definition it leads to, where it has one (`bind`'s `route`, looked up by `bindingOf`): what the host's `navigate` is handed. | [Testing Helpers](./testing#api-resolveNavigation) |

:::