repo-source-code-test-frameworks

Start with the React implementation as the canonical reference, then port identical describe/test names, schemas, and expected outputs to other frameworks. Only mechanical adapters differ, such as createForm in Solid or injectForm in Angular.

Use the custom renderHook helper at src/vitest/renderHook.ts, which mounts a wrapper component so lifecycle hooks like onBeforeMount or onMount have context. For pure Svelte rune logic without lifecycle, $effect.root in a .test.svelte.ts file is a lighter option.

No, React Native has no Form component and no submit method, so submission tests call handleSubmit directly. Tests render through react-native-web with @testing-library/react and jsdom, using fireEvent.change on rendered TextInput elements.

setTimeout(0) makes tests flaky because it does not wait for actual reactive updates. Use vi.waitFor to poll assertions until reactive state settles, flushSync for Svelte rune updates, or flushPromises for one-shot Vue microtask drains.

Tests must reach 100% coverage on every non-excluded file, matching React's vitest.config.ts exclusions for src/types, src/vitest, index files, and test files. Framework-specific branches like Solid's unwrap need dedicated tests with explanatory comments.