@octanejs/testing-library 0.1.3 → 0.1.7

package/README.md

@@ -67,6 +67,17 @@ React-specific remappings:
   commit and after discrete events, exactly like React — only the synthetic
   `onChange` normalization is absent, so a controlled text input updates its
   state from `onInput`.
+- **Text commit behavior is separate and intentional.** `user.type(input, text)`
+  emits native `input` events; a text `onChange` does not run until the edit is
+  committed, such as when `await user.tab()` blurs the field. A commit-only host
+  should use `defaultValue`, native `onChange`, and
+  `suppressNativeChangeWarning`. The hint only acknowledges intent; it does not
+  remap or dispatch an event.
+- **Checkables need click activation when activation is under test.**
+  `await user.click(checkbox)` produces the native `click` → `input` → `change`
+  sequence and automatic checked-state transition. `fireEvent.change(checkbox)`
+  is only an explicit change dispatch; it does not model the click, activation,
+  cancellation/rollback, or full event ordering.
 - **No enter/leave/focus double-dispatch.** RTL's `fireEvent.mouseEnter` also
   fires `mouseover` (and `focus` fires `focusin`, `select` fires `keyup`, …)
   purely to feed React's plugin system, which listens to different native
@@ -125,7 +136,7 @@ dispatches **real native events**, which is exactly octane's event model (a
 better fit than React, where it relies on the synthetic layer picking natives
 up). Install it alongside this package and use it unchanged; the pairing is
 pinned by `tests/user-event.test.ts` (click, `type()` per-keystroke `onInput`,
-`keyboard()`).
+text commit on `tab()`, checkbox click ordering, `keyboard()`).
 
 ## Status
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@octanejs/testing-library",
-  "version": "0.1.3",
+  "version": "0.1.7",
   "license": "MIT",
   "type": "module",
   "engines": {
@@ -41,12 +41,12 @@
     "@testing-library/dom": "^10.4.1"
   },
   "peerDependencies": {
-    "octane": "0.1.6"
+    "octane": "0.1.10"
   },
   "devDependencies": {
     "@testing-library/user-event": "^14.6.1",
     "vitest": "^4.1.9",
-    "octane": "0.1.6"
+    "octane": "0.1.10"
   },
   "scripts": {
     "test": "vitest run"

package/src/fire-event.ts

@@ -14,4 +14,9 @@
 // input-as-change); no remapping is wanted. The commit wiring (flushSync +
 // effect drain around every dispatch) rides on dom-testing-library's
 // `eventWrapper` config hook — see pure.ts.
+//
+// In particular, `fireEvent.change(textbox)` means “dispatch an explicit native
+// commit event”; it does not simulate typing or blur. Likewise, change on a
+// checkbox does not reproduce click activation/toggling or click → input →
+// change ordering. Use user-event's type/tab/click flows for those sequences.
 export { fireEvent } from '@testing-library/dom';