@@ -121,14 +121,7 @@ public function test_counts_reflect_seeded_data(): void
121121 $ maintenanceAsset = Asset::factory ()->create (['next_audit_date ' => $ farFuture ]);
122122 $ maintenanceAsset ->forceFill (['asset_eol_date ' => $ farFuture ])->save ();
123123
124- // Pin asset_id to the already-isolated $maintenanceAsset. Without
125- // this override MaintenanceFactory's default definition resolves
126- // asset_id via Asset::factory()->laptopZenbook(), spawning an
127- // extra asset whose asset_eol_date lands in the past on the ~5%
128- // chance leaked by AssetFactory's afterMaking hook. That was
129- // the source of a flaky assetsPastEol == 5 in CI.
130124 Maintenance::factory ()->create ([
131- 'asset_id ' => $ maintenanceAsset ->id ,
132125 'item_id ' => $ maintenanceAsset ->id ,
133126 'item_type ' => Asset::class,
134127 'start_date ' => now ()->subDays (20 ),
@@ -153,20 +146,14 @@ public function test_counts_ignore_completed_maintenances(): void
153146 // should register.
154147 $ asset = Asset::factory ()->create ();
155148
156- // Pin asset_id on both maintenance rows for the same reason as
157- // test_counts_reflect_seeded_data: MaintenanceFactory's default
158- // asset_id resolver spawns an extra asset per call, which can
159- // leak into cross-cutting counts on adjacent tests.
160149 Maintenance::factory ()->create ([
161- 'asset_id ' => $ asset ->id ,
162150 'item_id ' => $ asset ->id ,
163151 'item_type ' => Asset::class,
164152 'start_date ' => now ()->subDays (20 ),
165153 'expected_completion_date ' => now ()->subDays (5 ),
166154 'completed_at ' => now ()->subDays (1 ),
167155 ]);
168156 Maintenance::factory ()->create ([
169- 'asset_id ' => $ asset ->id ,
170157 'item_id ' => $ asset ->id ,
171158 'item_type ' => Asset::class,
172159 'start_date ' => now ()->subDays (20 ),
0 commit comments