docs: write test framework migration document

[json-choi]

Summary by CodeRabbit

• Documentation
  • Added a comprehensive migration guide explaining how to convert Mocha/Jest end-to-end tests to the Itdoc format, with rationale, step-by-step workflow, and before/after examples in JavaScript and TypeScript.
  • Documented common patterns (optional/nullable fields, path/query params, auth headers), API metadata and request/response guidance, troubleshooting, and a migration checklist.
  • Published a full Korean translation of the guide.

[coderabbitai]

Walkthrough

Adds two new documentation files: an English guide at itdoc-doc/docs/guides/test-framework-migration.mdx and a Korean translation at itdoc-doc/i18n/ko/docusaurus-plugin-content-docs/current/guides/test-framework-migration.mdx. Both files provide a migration guide for converting Mocha/Jest end-to-end tests to Itdoc format, covering rationale, key differences, step-by-step migration workflow, before/after JavaScript and TypeScript examples, Itdoc DSL usage (describeAPI, itDoc, HttpMethod, HttpStatus, field, header helpers), patterns for params and auth, a migration checklist, troubleshooting, and links/resources.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Files are homogeneous documentation additions; review should focus on accuracy and consistency of examples and localization. Areas to check:

• Example code blocks for correctness (JS/TS before/after).
• Consistency between English and Korean versions.
• Accurate references to Itdoc API names and helpers.

Possibly related issues

• [Docs]: Creating a Test Framework Migration document #238 — Adds the requested Test Framework Migration document converting Mocha/Jest to Itdoc; this PR appears to implement that feature request.

Suggested reviewers

• wnghdcjfe
• cjs1301

Pre-merge checks and finishing touches

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The pull request title 'docs: write test framework migration document' accurately and concisely describes the main change: adding a comprehensive migration guide document for converting existing Mocha/Jest tests to Itdoc format. The title is specific, clear, and directly reflects the primary purpose of the changeset, which includes new documentation files in both English and Korean with step-by-step migration instructions and examples.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch 238-docs-creating-a-test-framework-migration-document

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 120cbd8 and c9fcfcb.

📒 Files selected for processing (2)

• itdoc-doc/docs/guides/test-framework-migration.mdx (1 hunks)
• itdoc-doc/i18n/ko/docusaurus-plugin-content-docs/current/guides/test-framework-migration.mdx (1 hunks)

🧰 Additional context used

🪛 Gitleaks (8.28.0)

itdoc-doc/docs/guides/test-framework-migration.mdx

[high] 527-527: Detected a Generic API Key, potentially exposing access to various services and sensitive operations.

(generic-api-key)

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 2

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between a5f197b and a1071d9.

📒 Files selected for processing (2)

• itdoc-doc/docs/guides/test-framework-migration.mdx (1 hunks)
• itdoc-doc/i18n/ko/docusaurus-plugin-content-docs/current/guides/test-framework-migration.mdx (1 hunks)

[coderabbitai]

Actionable comments posted: 2

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between a1071d9 and 120cbd8.

📒 Files selected for processing (2)

• itdoc-doc/docs/guides/test-framework-migration.mdx (1 hunks)
• itdoc-doc/i18n/ko/docusaurus-plugin-content-docs/current/guides/test-framework-migration.mdx (1 hunks)

🧰 Additional context used

🪛 Gitleaks (8.28.0)

itdoc-doc/docs/guides/test-framework-migration.mdx

[high] 527-527: Detected a Generic API Key, potentially exposing access to various services and sensitive operations.

(generic-api-key)

[PENEKhun]

ko

고생하셨습니다!
사용자들이 이미 작성해둔 supertest를 itdoc으로 마이그레이션하기 한층 쉬워질 것 같네요 👍

제안 1

Test Framework Migration Guide라는 제목 보단,

• Migration guide from your e2e tests

이런식의 제목이 어떨까요?

필수는 아니니 직접 잘 판단해 주시면 됩니다.

en

Great work!

This will definitely make it much easier for users to migrate their existing supertest code to itdoc 👍

Suggestion 1

Instead of the title Test Framework Migration Guide, how about something like:

migration guide from your e2e tests
What do you think?