前端应用
a11y-frontend-testing
更新于 2026-10-06
Accessibility · 测试规则
Testing rules for Accessibility: behaviour-named cases, explicit fixtures and order-independent suites.
- 技术栈
- Accessibility
- 主题
- 测试
- 条目
- 9 条
- 版本
- v0.2.0
✓ 应当这么做
- ✓ Test the smallest unit that carries the behaviour, then one end-to-end happy path
- ✓ Name tests after the behaviour, not after the function under test
- ✓ Keep fixtures explicit and local to the test that needs them
✕ 常见反模式
- ✕ Asserting on private internals that will change with any refactor
- ✕ Fixed sleeps instead of condition waits
- ✕ Tests that depend on execution order or a shared mutable world
◎ 交付前验证
- ◎ Production build completes and the bundle budget is respected
- ◎ No critical CSS purged by the optimizer (spot-check key pages)
- ◎ Lighthouse/axe pass on the main route after the change
同分类条目
40 篇前端应用
React 工程规则
React 19 delivery rules: pure render, server actions and stable list identity
前端应用
Next.js 工程规则
Next.js 15 App Router rules: async cookies/headers and server/client boundary discipline
前端应用
Nuxt 工程规则
Nuxt 3 rules: data fetching composables and SSR-safe state
前端应用
Vue 工程规则
Vue 3 Composition API rules: pure computed state and typed props
前端应用
Svelte 工程规则
Svelte 5 rules: runes-based reactivity and effect discipline
前端应用
Solid 工程规则
Solid.js rules: fine-grained reactivity without dependency-array leakage