E2E Test Coverage Analysis: 84% of tests are skipped

Aperta
#414 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
22/100
Tipo di issue
Refactoring
Chiarezza
Da chiarire
Stato di attività
Ferma
Stack tecnologico
typescript
Ambito
testing

Direzione di ricerca

Start with the test.describe.skip() wrappers in the 42 skipped spec files, such as 04-collections.spec.ts, and the active baseline in 01-health.spec.ts and smoke.spec.ts. Remove the skip from one small file, run it, and record which tests fail and why. Done means a re-enabled file passes reliably in the E2E run. The issue does not say which skipped areas are expected to pass, so confirm scope with maintainers first.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Summary

An analysis of the E2E test suite reveals that the vast majority of tests are currently skipped. This issue documents the current state to track progress toward enabling more tests.

Statistics

Metric Count Percentage
Active tests 60 15.6%
Skipped tests 325 84.4%
Total tests 385 100%

Test File Breakdown

Active Test Files (5 files, 63 tests - 3 individually skipped)
File Tests Notes
01-health.spec.ts 2 API health checks
02-authentication.spec.ts 6 Login/logout flows
02b-authentication-api.spec.ts 31 Auth API endpoints
03-admin-dashboard.spec.ts 10 Dashboard UI (2 skipped)
smoke.spec.ts 14 Critical path validation (1 skipped)
Skipped Test Files (42 files, 322 tests)

Tests wrapped in `test.describe.skip()`:

File Tests Feature Area
04-collections.spec.ts 9 Collections management
05-content.spec.ts 12 Content management
06-media.spec.ts 12 Media management
07-api.spec.ts 10 API endpoints
08-collections-api.spec.ts 23 Collections API
08b-admin-collections-api.spec.ts 17 Admin collections API
09-integration.spec.ts 7 Full integration workflows
09-media-bulk-actions.spec.ts 5 Media bulk actions
10-media-view-switching.spec.ts 3 Media view switching
10-workflow-transitions.spec.ts 13 Workflow transitions
11-media-create-folder.spec.ts 10 Media folder creation
11-scheduled-content.spec.ts 17 Scheduled content
12-notifications.spec.ts 12 Notification system
13-migrations.spec.ts 17 Database migrations
14-database-tools.spec.ts 18 Database tools
15-plugins.spec.ts 13 Plugin management
15-user-xss-prevention.spec.ts 2 XSS prevention
16-user-management.spec.ts 3 User management
17-media-upload-immediate.spec.ts 1 Media upload
18-media-bulk-menu-zindex.spec.ts 4 Media bulk menu z-index
19-content-media-selector.spec.ts 6 Content media selector
19-dashboard-recent-activity.spec.ts 4 Dashboard recent activity
20-content-api-collection-filter.spec.ts 4 Content API filtering
21-plugin-version-display.spec.ts 7 Plugin version display
22-collection-field-edit.spec.ts 4 Collection field editing
23-content-api-crud.spec.ts 13 Content API CRUD
24-media-thumbnail-loading.spec.ts 2 Media thumbnails
25-media-cleanup-unused.spec.ts 6 Media cleanup
26-content-duplicate.spec.ts 8 Content duplication
27-profile-picture-upload.spec.ts 3 Profile picture upload
27-settings-general.spec.ts 8 General settings
28-plugin-filters-search.spec.ts 11 Plugin filters/search
29-email-plugin-settings.spec.ts 7 Email plugin settings
30-richtext-tinymce.spec.ts 5 TinyMCE rich text
31-richtext-quill.spec.ts 5 Quill rich text
32-mdxeditor-new-content.spec.ts 3 MDXEditor new content
32-mdxeditor-richtext.spec.ts 5 MDXEditor rich text
33-field-type-editor-options.spec.ts 3 Field type editor options
34-field-type-persistence.spec.ts 2 Field type persistence
35-collection-field-type-badges.spec.ts 2 Collection field badges
36-collection-field-easymdx-edit.spec.ts 3 EasyMDX field editing
36-easymde-plugin-visible.spec.ts 3 EasyMDE plugin visibility

Recommendations

  1. Prioritize core functionality tests: Enable tests for collections, content, and media management first
  2. Fix flaky tests: Investigate why tests were skipped and fix underlying issues
  3. Track progress: Use this issue to track re-enabling tests over time
  4. CI integration: Consider running a subset of tests in CI to catch regressions
Lingua principale
TypeScript
Stelle
1.8k
Fork
219
Merge medio
2g 21h
PR unite (30g)
67

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di SonicJs-Org/sonicjs

Tutte le issue di SonicJs-Org/sonicjs

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.