The translation is temporarily closed for contributions due to maintenance, please come back later.

Translation status

17 Strings
35%
Browse Translate
462 Words
37%
2,883 Characters
36%

Strings status

Strings Words Characters
17 462 2,883
All strings Browse Translate Zen
6 175 1,041
Translated strings Browse Translate Zen
11 287 1,842
Unfinished strings Browse Translate Zen
11 287 1,842
Strings marked for edit Browse Translate Zen

Summary

Project website tuist.dev
Translation process
  • Translations can be made directly.
  • Translation suggestions can be made.
  • Any authenticated user can contribute.
  • The translation uses monolingual files.
  • The translation base language can not be edited.
Source code repository https://github.com/tuist/tuist
Repository branch main
Last remote commit [Release] Tuist CLI 4.191.5 47d72d91c9
github-actions authored 05/01/2026
Last commit in Weblate Translated using Weblate (Portuguese) 443deef24d
DeepL authored 04/29/2026
Weblate repository https://translate.tuist.dev/git/tuist/documentation-pages/
File mask docs/docs/*/guides/features/selective-testing.md
Monolingual base language file docs/docs/en/guides/features/selective-testing.md
Translation file Download docs/docs/zh_Hans/guides/features/selective-testing.md
Last change April 20, 2026, 4:04 p.m.
Last change made by Background commit
Language Chinese (Simplified Han script)
Language code zh_Hans
Text direction Left to right
Case sensitivity Case-insensitive
Number of speakers 1,286,444,445
Number of plurals 1
Plural type None
Plurals
Plural formula 0
04/28/2026

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 17 462 2,883
Translated 35% 6 37% 175 36% 1,041
Needs editing 64% 11 62% 287 63% 1,842
Read-only 0% 0 0% 0 0% 0
Failing checks 0% 0 0% 0 0% 0
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 0% 0 0% 0 0% 0
Last 12 months Previous

Activity in last 12 months

0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 39 changes 0 changes 11 changes 0 changes 51 changes 0 changes 37 changes 0 changes 0 changes 0 changes 6 changes 0 changes 2 changes
MayJunJulAugSepOctNovDecJanFebMarApr

Quick numbers

462
Hosted words
17
Hosted strings
35%
Translated
1
Contributors
and previous 30 days

Trends of last 30 days

—
Hosted words
+100%
—
Hosted strings
+100%
—
Translated
+35%
—
Contributors
—
User avatar weblate:commit

Changes committed
Changes committed 04/20/2026
User avatar mt:deepl

Automatically translated
To get automatic pull/merge request comments, integrate your {1}Tuist project{2} with a {3}Git platform{4}.
要获取自动生成的拉取/合并请求评论，请将您的 {1}Tuist 项目{2}与 与 {3}Git 平台{4} 集成。
04/20/2026
User avatar weblate:commit

Changes committed
Changes committed 03/20/2026
User avatar mt:deepl

Automatically translated
Test coverage tools assume that the whole test suite runs at once, which makes them incompatible with selective test runs—this means the coverage data might not reflect reality when using test selection. That’s a known limitation, and it doesn’t mean you’re doing anything wrong. We encourage teams to reflect on whether coverage is still bringing meaningful insights in this context, and if it is, rest assured that we’re already thinking about how to make coverage work properly with selective runs in the future.
测试覆盖率工具默认整个测试套件会一次性运行，这使其得它们与选择性测试运行不兼容——这意味着在使用测试选择功能时，覆盖率数据可能无法真实反映实际情况。这是已知的限制，并不代表操作有误。 我们建议团队审视覆盖率在此场景下是否仍能提供有效洞察。若仍具价值，请放心——我们已着手研究如何使覆盖率在未来与选择性运行模式协同工作局限性，并不意味着您做错了什么。 我们建议团队思考在此情境下覆盖率是否仍能提供有意义的洞察；若确实如此，请放心，我们正在研究如何在未来让覆盖率与选择性运行正常配合。
03/20/2026
User avatar mt:deepl

Automatically translated
---
{
"title": "Selective testing",
"titleTemplate": ":title · Features · Guides · Tuist",
"description": "Use selective testing to run only the tests that have changed since the last successful test run."
}
---
---
{
"title": "选择性测试",
"titleTemplate": ":title · 功能 · 指南 · Tuist",
"description": "使用选择性测试，仅运行自上次成功测试运行后发生变更以来发生更改的测试。"
}
---
03/20/2026
User avatar mt:deepl

Automatically translated
On every test run on the CI, you most likely re-run all the tests, regardless of the changes. Tuist's selective testing helps you to drastically speed up running the tests themselves by running only the tests that have changed since the last successful test run based on our {1}hashing algorithm{2}.
在持续集成环境 CI 上的每次测试运行中，您很可能无论变更与否无论更改内容如何，您通常都会重新运行所有测试。Tuist的自适应测试机制通过基于 的选择性测试功能基于我们的 {1}哈希算法{2}，仅运行自上次成功测试后发生变更的测试项，可大幅提升测试执行效率运行以来发生更改的测试，从而帮助您大幅加快测试运行速度。
03/20/2026
User avatar mt:deepl

Automatically translated
As your project grows, so does the amount of your tests. For a long time, running all tests on every PR or push to `main` takes tens of seconds. But this solution does not scale to thousands of tests your team might have.
随着项目规模扩大的扩展，测试用例数量也会增长。长期以来，在每个PR或推送至`主分支` 时运行全部测试需耗费随之增加。很长一段时间以来，在每次提交拉取请求（PR）或向`main` 推送代码时，运行所有测试都需要数十秒。但该这种方案无法适应团队可能拥有的数千个测试用例。
03/20/2026
User avatar mt:deepl

Automatically translated
Due to the impossibility of detecting the in-code dependencies between tests and sources, the maximum granularity of selective testing is at the target level. Therefore, we recommend keeping your targets small and focused to maximize the benefits of selective testing.
由于无法检测测试与源代码之间的代码内部依赖关系，选择性测试的最大粒度仅能达到为目标级别。因此建议保持目标小而聚焦，以充分，我们建议将目标保持得小而专注，以最大限度地发挥选择性测试的优势。
03/20/2026
User avatar webhook:github

Resource updated
The “docs/docs/zh_Hans/guides/features/selective-testing.md” file was changed. 01/22/2026
User avatar webhook:github

String updated in the repository
Once your Tuist project is connected with your Git platform such as [GitHub]{1}, and you start using `tuist test` as part of your CI workflow, Tuist will post a comment directly in your pull/merge requests, including which tests were run and which skipped: ![GitHub app comment with a Tuist Preview link]{2}
当您的Tuist项目与Git平台（如[GitHub]{1}）连接后，若在持续集成流程中使用`tuist test` 命令，Tuist将直接在拉取请求/合并请求中添加评论，包含已运行测试与跳过测试的详情：![GitHub应用评论含Tuist预览链接]{2}
01/22/2026
Browse all translation changes