fastify/fastify

Migrate away from tap in all repositories

Open

#5,555 建立於 2024年7月8日

在 GitHub 查看
 (37 留言) (10 反應) (0 負責人)JavaScript (36,241 star) (2,683 fork)batch import
good first issue

描述

I think we must move away from tap in favor of node:test, as Isaacs has stated that he will drop unsupported Node.js version in patch releases. Given our infrequent major release cadence, it's not a good bet for us.

https://x.com/izs/status/1810339751456825767?s=46&t=22eoAstJVk5l46KQXYEk5Q

貢獻者指南

技術棧
javascriptnodejs
領域
testingbackendtooling
議題類型
refactor
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
3-5 days
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
active
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
mostly clear
前置要求
Node.js testingfastify test setup
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
60
研究方向
The issue requires replacing the 'tap' test framework with Node.js's built in 'node:test' across all fastify repositories. Review the conversation in the issue for the agreed upon approach and any migration steps. Look at current test files (e.g., test/*.js) and the package.json test scripts to understand the scope. Identify common patterns and plan the migration per repository.
Migrate away from tap in all repositories · fastify/fastify#5555 | Good First Issue