Skip to content

Testing

No tests exist.

  • package.json has no test script
  • No test framework declared
  • No __tests__/, test/, spec/, e2e/

What "verification" looks like today

Manual: spin up yarn dev, log in, exercise the feature, eyeball the result. The Polotno editor in particular needs visual / interactive verification — automated tests for visual editors are notoriously expensive.

Test priorities (if added)

For a 73-page internal staff tool:

  1. Auth + redirect flow — login → dashboard → logout → re-login. The single highest-value test because it's the platform entry point.
  2. Role-typed UI gating — render Navbar with each role_type (1, 2, 6, 13), assert correct items visible. This catches the lurking bug from inline-literal role IDs.
  3. Store actions — mock $axios, assert action behaviour. ~100 actions; sample the 20 most-used.
  4. Smoke per page — render with mocked auth + mocked API, assert no crash.
  5. Polotno boundary — assert the editor mounts and exposes window.store. Don't test internal editor behaviour (Polotno's responsibility).

Tooling

  • Vitest or Jest + @vue/test-utils@1 (Vue 2 era)
  • axios-mock-adapter for API mocks
  • Playwright for E2E (one happy-path spec; not 100 specs — designer staff have other ways to detect breakage)

Effort

~1 engineer-week for an initial Vitest harness + the high-priority tests above. Worthwhile if the team plans the Vue 2 → Vue 3 migration — having tests beforehand makes the migration much safer.

Cross-component status

Same as the rest of the platform. No backend has tests; no frontend has tests. admin_console_R (smallest, newest) is the lowest-cost pilot target if test infrastructure is to be introduced.