Flaky Test Retries in Pest v4.5.0

Pest v4.5.0 adds first-class support for retrying flaky tests with a new flaky() modifier and --flaky CLI flag. The release also includes a new architecture assertion for detecting namespace/file path casing mismatches, a --only-covered coverage filter, and more.

• flaky() test modifier with configurable retry count
• --flaky CLI option to run only flaky-marked tests
• toBeCasedCorrectly architecture assertion
• --only-covered option for code coverage output
• Multiple bug fixes for datasets, traits, and parallel testing

# 什么是新的

# flaky() Test Modifier and --flaky CLI Option

Tests that fail intermittently due to timing, external dependencies, or other non-deterministic conditions can now be marked with ->flaky() . When a flaky test fails, Pest automatically retries it up to the configured number of times before reporting it as a failure. The default retry count is 3.

它
（
'sends an email notification'
,
功能
（）{

// ...
}）
->
flaky
（）；
它
（
'resolves within the timeout'
,
功能
（）{

// ...
}）
->
flaky
（
尝试
:
5
（英文）：

新的 --flaky CLI flag filters the test run to execute only tests marked as flaky, making it easier to verify or debug unstable tests in isolation:

vendor/bin/pest

--flaky

Lifecycle hooks such as beforeEach 和 afterEach run between each retry, so test state is properly reset on every attempt.

# toBeCasedCorrectly Architecture Assertion

新的 ->toBeCasedCorrectly() assertion has been added to Pest's architecture testing suite. It compares each class's namespace against its file path and flags any casing discrepancies. Because macOS and Windows use case-insensitive file systems by default, mismatched casing is often invisible in local development but causes class-not-found errors when deployed to Linux servers.

拱
（）

->
预计
（
'应用程序'
）

->
toBeCasedCorrectly
（）；

A class at app/Providers/AppServiceProvider.php with the namespace App\providers\AppServiceProvider would be caught by this assertion.

公关稿： #1455 , contributed by @SimonBroekaert

# --only-covered Coverage Option

这 --coverage flag now accepts an --only-covered companion option that hides all files with 0% coverage from the output. This is useful when working on large applications where you want to focus on which files your new tests actually cover, without scrolling past a long list of uncovered files.

vendor/bin/pest

--覆盖率

--only-covered

The option does not affect --min 或者 --exact thresholds; those calculations still include all files.

公关稿： #1626 , contributed by @SimonBroekaert

# 问题修复

• 固定的 toUseTrait to detect traits inherited through parent classes and nested trait usage ( #1515 ), contributed by @yondifon
• Fixed missing classes before toExtend in the Laravel preset ( #1569 ), contributed by @treyssatvincent
• Added "Rules" classes to the Laravel preset ( #1580 ), contributed by @bibrokhim
• 固定的 --parallel 和 --teamcity argument handling for ParaTest ( #1615 ), contributed by @smirok
• Fixed nested dataset discovery and invalid-dataset reporting in parallel mode ( #1655 ), contributed by @stsepelin
• Fixed Unicode character preservation in filenames when using --filter （ #1624 ), contributed by @Vmadmax
• Fixed dataset named parameters ( #1634 ), contributed by @dbpolito
• 固定的 this type annotations for parameter closures in functions ( #1628 ), contributed by @DevDavido
• Fixed dataset inheritance when using method chaining with beforeEach()->with() 和 describe()->with() （ #1565 ), contributed by @louisbels

# 参考

• 完整更新日志
• GitHub 发布