HELP NEEDED: Find out suitable testing strategy (unit tests, e2e tests)

[trobonox]

I am currently debating how the application should be tested, open for ideas (frameworks to use, what approach makes most sense for this app). Since the app uses TypeScript, mostly saving logic to JSON and drag-n-drop would have to be tested, so unit tests might be the most appropriate.

Tracking issue, open for suggestions/ideas.

[gitoak]

let me look into it

[gitoak]

TL;DR: Use Vitest for unit tests on logic like JSON saving, utils and dnd mechanics. Use Playwright for E2E testing of full user flows, dnd UI and platform specific features (e.g., file system). This covers both isolated logic and critical user interactions across platforms.

Testing Strategy

Unit Testing with Vitest:

• Why Vitest
  • Fast: Vitest is optimized for Vite-based apps like Nuxt, faster than Jest.
  • Great Typescript support
• What to Unit Test
  • Saving Logic: Ensure application state is correctly converted to and from json
  • dnd logic: Validate dnd mechanics and ensure proper state updates
  • Utilities: Test helper functions
  • State Management: test store modules and other state
  • + more

E2E Testing with Playwright

• Why Playwright:
  • Cross-platform & Tauri Integration: supports file system and window interactions on different os's and screen sizes
  • Simulates Real User Actions: Ideal for testing full user workflows and UI integration
• What to E2E Test:
  • Critical User Flows: Test saving/loading data, dnd behavior, creating boards, etc.
  • File System Access: Ensure file-related operations on different operating systems
  • Cross-platform Behavior: Validate consistent app behavior across platforms
  • + more

This Testing Strategy is optimized for the Nuxt + Tauri stack and is also compatible with GH actions for automatic tests

Love to hear your feedback @trobonox