Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

[Feature]: Provide users a hook to define the tests to each shard.

クローズ
  • 何か問題がありますか？
#43,564 コメント 1 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
35/100
issue の種類
機能追加
明瞭さ
説明が足りない
活発さ
活発
技術スタック
playwright, typescript
領域
testing

調査の方向性

Start by reading Playwright's test sharding implementation and how it assigns tests to shards; the issue does not name files, tests, or entry points. Clarify whether the goal is custom ordering based on duration, shard selection by tags or permissions, or both, then define how users register that behavior. Done would mean the chosen hook is documented and covered by tests for its shard assignments.

索引モデルが issue の本文から書いたものです。

説明

🚀 Feature Request

I normally answer question on Discord, this issue or desire has come up a few times in one way or another. The question was a way to influence the tests that will be provided to each shard.

Example

I see two different but related use cases.

First would be if users have historical data of how long a test may take, if they were allowed a way to register some method that would sequence tests that are provided to each shard, thus allowing a way to help minimize the time for a test run. So when some test may take a long time, those could be distributed across each shard equally and spread out the load.

The other use case might be to allow shards to be defined in a way to help isolate or direct tests to a given shard. So a little more might need to be added, and could be a different DCR to keep things more atomic, but thought i'd spew it all out at once and make a second issue of deemed a separate issue. But it would be great from other support issues i've answered, at times people may wish to run or direct test to only run on one machine. Example might be for low-end/restricted user or a higher level user based on permissions and finally say an admin. So it might require the ability for a shard to be defined based on permissions or operations. Tie this in with the ability of tests could have a tag attribute to then allow users the ability to help define the "working set" list of tests. How this is clear. Could see two separate DCR requests but thought i'd get it all out at once...

Motivation

Would allow users the ability and flexibility to help customize test when they want to shard, but they may have multiple constraints and desire how tests are grouped on a given shard.

主要言語
TypeScript
スター
98k
フォーク
6.6k
平均マージ
15時間 59分
マージ済み PR（30日）
296

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

microsoft/playwright のほかの issue

microsoft/playwright の issue をすべて見る

似ている issue

TypeScript の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。