ab21c7f805
* feat: Cal.diy — community-driven MIT-licensed fork of Cal.com This squashed commit contains all Cal.diy changes applied on top of calcom/cal.com main: - Rebrand Cal.com to Cal.diy across the entire codebase - Remove Enterprise Edition (EE) features, license checks, and AGPL restrictions - Switch license from AGPL-3.0 to MIT - Remove docs/ directory (migrated to Nextra at cal.diy) - Remove dead code: org tests, EE tips, platform nav, premium username, SAML/SSO, etc. - Clean up .env.example for self-hosted Cal.diy - Update Docker image references to calcom/cal.diy - Update README, CONTRIBUTING.md, and issue templates for Cal.diy community fork - Add PR welcome bot for Cal.diy contributors - Fix API v2 breaking changes oasdiff ignore entries - Replace Blacksmith CI runners with default GitHub Actions 3893 files changed, 20789 insertions(+), 411020 deletions(-) Co-Authored-By: benny@cal.com <sldisek783@gmail.com> * refactor: remove org-specific /organizations/:orgId endpoints from API v2 atoms controllers (#1701) Co-authored-by: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com> * fix: revert Cal.diy Inc to Cal.com, Inc. in license files, copyright notices, and package metadata (#1702) Co-authored-by: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com> * rip out org related comments in api v2 --------- Co-authored-by: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
28 lines
1.1 KiB
Markdown
28 lines
1.1 KiB
Markdown
---
|
|
title: Incremental Test Fixing
|
|
impact: MEDIUM
|
|
impactDescription: Methodical approach prevents getting overwhelmed by test failures
|
|
tags: testing, debugging, workflow
|
|
---
|
|
|
|
# Incremental Test Fixing
|
|
|
|
## One File at a Time
|
|
|
|
When fixing failing tests in the Cal.diy repository, take an incremental approach by addressing one file at a time rather than attempting to fix all issues simultaneously.
|
|
|
|
This methodical approach makes it easier to identify and resolve specific issues without getting overwhelmed by the complexity of multiple failing tests across different files.
|
|
|
|
## Recommended Order
|
|
|
|
1. Run `yarn type-check:ci --force` to identify TypeScript type errors
|
|
2. Run `yarn test` to identify failing unit tests
|
|
3. Address both type errors and failing tests before considering the task complete
|
|
4. Type errors often need to be fixed first as they may be causing the test failures
|
|
|
|
## Focus Strategy
|
|
|
|
- Focus on getting each file's tests passing completely before moving on to the next file
|
|
- Fix type errors before test failures - they're often the root cause
|
|
- Run `yarn prisma generate` if you see missing enum/type errors
|