test: migrate five small feature areas to Vitest - #446
Conversation
E2E — mocked backend🎭 E2E Tests✅ All green — 339 passed · 0 failed · 0 skipped, across 27 spec files in 5m 45s. By spec file
All 339 tests — click to expand
Slowest 10 — what the shard counts should be tuned against
📼 Download the HTML report, videos and traces — see the Generated by run 32691851101 from |
E2E — real Fineract🎭 E2E Tests✅ All green — 72 passed · 0 failed · 0 skipped, across 22 spec files in 6m 5s. By spec file
All 72 tests — click to expand
Slowest 10 — what the shard counts should be tuned against
📼 Download the HTML report, videos and traces — see the Generated by run 32691851101 from |
|
@zhangxinyao88 Handle merge conflicts |
Summary
spm,calendars,meetings,settings, andtellersprovideTranslateTesting()#411 progress
Migrated:
spm— 5, this PRcalendars— 3, this PRmeetings— 3, this PRsettings— 3, this PRtellers— 3, this PRerrors— 1, test: migrate errors spec from Karma to Vitest #417interop— 1, test: migrate interop spec from Karma to Vitest #413Still on Karma:
security— 2tasks— 2transfers— 2dashboard— 1profile— 1login— 2, including one object-formcreateSpyObjcenters— 2, including oneflush()reporting— 2, including oneflush()layout— 2, both using object-formcreateSpyObjTesting
npm run lintnpm run format:checknpm run check:test-runnerLatest main CI has 827 Karma + 546 Vitest tests. This PR moves 54 tests, so the expected result is 773 Karma + 600 Vitest = 1,373 unchanged. Local Karma and build hit a native Node 22 exit 134 during Angular compilation; PR CI will verify both on the latest LTS.
Part of #411