不想手动配置？将本页链接粘贴到 Devin 会话中，让它为你完成所有设置。 A [playbook](/zh/product-guides/creating-playbooks) 会将你团队的测试规范固化下来，让 Devin 编写测试的方式与工程师保持一致。支付相关代码有其独特考量——幂等性、货币精度、网关重试、符合 PCI 要求的 mocking 等——因此，一个专注支付场景的 playbook 能捕捉到通用 playbook 会遗漏的问题。 **选项 1：自己编写 playbook。** 前往 [**Settings > Playbooks > Create playbook**](https://app.devin.ai/settings/playbooks/create?utm_source=docs\&utm_medium=use-case-gallery) 并定义你的规范： ```txt Payments Test Playbook theme={null} ## Procedure 1. Read the target payment module and identify all exported functions 2. Study existing test files in src/services/__tests__/ for patterns 3. Create a test file named {Module}.test.ts in __tests__/ next to the source 4. Write tests using the AAA pattern (Arrange, Act, Assert) 5. Mock the Stripe SDK with jest.mock('stripe') — never call real payment APIs 6. Mock database calls with the helpers from src/test/helpers.ts 7. Use integer cents for all currency values — never floating-point dollars 8. Test idempotency: calling processCharge twice with the same idempotency key must not create duplicate charges 9. Cover success paths, error paths, and edge cases for every function 10. Run `npm test -- --coverage` and verify 90%+ line coverage for the file ## Specifications - Framework: Jest with TypeScript - Mocking: jest.mock() for Stripe SDK, jest.spyOn() for internal methods - Currency: Always use integer cents (e.g., 2999 not 29.99) - Assertions: Prefer specific matchers (toHaveBeenCalledWith, toThrow) - Naming: describe('PaymentService') > describe('processCharge') > it('charges a valid card') ## Forbidden Actions - Do not call real Stripe, PayPal, or any live payment gateway in tests - Do not use floating-point arithmetic for currency calculations - Do not modify the source module to make it easier to test - Do not skip idempotency or retry-logic edge cases ``` **选项 2：让 Devin 为你创建 playbook。** 描述你的测试规范，Devin 会为你生成一个完整的 playbook： ```txt Generate a payments test playbook theme={null} Create a playbook for writing unit tests for our payment modules in src/services/. We use Jest with TypeScript, mock the Stripe SDK with jest.mock('stripe'), and use integer cents for all currency values. Look at our existing tests in src/services/__tests__/ to learn our patterns (AAA style, specific matchers, describe/it naming). The playbook should cover mocking strategy, idempotency testing, currency precision rules, and forbidden actions like calling real payment APIs. ``` 然后将你目前最好的一个测试文件 (例如 `src/services/__tests__/UserService.test.ts`) 添加为一条 [Knowledge](/zh/product-guides/knowledge) 条目，这样 Devin 就能获得一个你团队风格的具体示例。在让 Devin 针对特定文件之前，先找出你的支付模块中存在哪些覆盖率薄弱环节。让 Devin 运行你的覆盖率工具，并找出问题最严重的部分： ```txt Analyze payment module coverage theme={null} Run npm test -- --coverage and list every file under src/services/ that handles payments, billing, or subscriptions with less than 80% line coverage. Sort by coverage ascending so I can see the biggest gaps first. ``` Devin 会在其终端中运行测试套件，解析覆盖率报告，并给出一份按优先级排序的列表： ``` File | Lines | Uncovered functions ------------------------------------|-------|------------------------------ src/services/PaymentService.ts | 34% | processCharge, issueRefund, handleWebhook src/services/SubscriptionService.ts | 41% | renewSubscription, cancelTrial, proratePlan src/services/InvoiceService.ts | 52% | generateInvoice, applyPromoCode, calculateTax src/services/PayoutService.ts | 58% | initiateTransfer, reconcileSettlement ``` 新建一个新会话，附加你的支付测试 playbook (你会看到一个蓝色胶囊提示已附加) ，然后告诉 Devin 要针对哪个模块编写测试： ```txt Write tests for PaymentService theme={null} Write unit tests for all untested functions in src/services/PaymentService.ts. Focus on processCharge, issueRefund, and handleWebhook. Each function needs tests for success, error, and edge cases. Mock the Stripe SDK — never call real APIs. Use integer cents for all currency values. Run the tests and verify 90%+ line coverage for this file. ``` Devin 会阅读该模块，学习你现有测试的模式和写法，按照你的 playbook 编写一份完整的测试文件，并运行它： ``` PASS src/services/__tests__/PaymentService.test.ts PaymentService processCharge ✓ charges a valid credit card and returns a receipt (14ms) ✓ uses integer cents to avoid floating-point errors (6ms) ✓ rejects duplicate charges with the same idempotency key (5ms) ✓ retries on Stripe gateway timeout up to 3 times (18ms) ✓ throws InsufficientFundsError for declined cards (4ms) issueRefund ✓ refunds full amount for a completed charge (8ms) ✓ refunds partial amount in cents when specified (6ms) ✓ prevents refund exceeding the original charge amount (3ms) ✓ throws AlreadyRefundedError on duplicate refund attempts (4ms) handleWebhook ✓ processes charge.succeeded events and updates order status (7ms) ✓ processes charge.refunded events and credits the customer (6ms) ✓ verifies Stripe webhook signature before processing (3ms) ✓ ignores unrecognized event types without error (2ms) Coverage: 94% lines | 91% branches | 100% functions ``` Devin 会创建一个 PR (pull request) ，并在描述中附上测试文件和覆盖率摘要。审查第一个拉取请求 (pull request，PR) 。如果 mock 策略或断言风格不太合适，在将 playbook 应用于更多模块之前先对其进行更新——这一轮反馈可以避免你在多个 PR 中反复修正同样的问题。然后按照你的覆盖缺口清单逐项推进： ```txt 覆盖 SubscriptionService theme={null} 使用相同的 playbook 为 src/services/SubscriptionService.ts 编写测试。重点覆盖 renewSubscription、cancelTrial 和 proratePlan。使用以分为单位的整数来测试按比例分摊的计算。目标是达到 90% 以上的行覆盖率。 ``` 为了更快推进，让 Devin 启动并行会话——每个支付模块一个会话——全部遵循同一套 playbook。或者 [安排](/zh/product-guides/scheduled-sessions) 每周定期会话，自动查找任何低于覆盖率阈值的支付模块并为其生成测试。

{title}