extend(TestCase::class) // ->use(RefreshDatabase::class) ->in('Feature'); pest()->extend(TestCase::class)->in('Browser'); /* |-------------------------------------------------------------------------- | Expectations |-------------------------------------------------------------------------- | | When you're writing tests, you often need to check that values meet certain conditions. The | "expect()" function gives you access to a set of "expectations" methods that you can use | to assert different things. Of course, you may extend the Expectation API at any time. | */ expect()->extend('toBeOne', function () { return $this->toBe(1); }); /* |-------------------------------------------------------------------------- | Functions |-------------------------------------------------------------------------- | | While Pest is very powerful out-of-the-box, you may have some testing code specific to your | project that you don't want to repeat in every file. Here you can also expose helpers as | global functions to help you to reduce the number of lines of code in your test files. | */ function something() { // .. } /** * Link a Лидерра-project to a supplier_project via the M:N pivot * (Plan 1 model). Post-Plan-2 LeadRouter eligibility queries the pivot * only; legacy supplier_b{1,2,3}_project_id FK is ignored for routing. * * Single source — replaces previous duplicated declarations in * LeadRouterTest.php / RouteSupplierLeadJobTest.php (Plan 2 cleanup). * pivot created_at has DEFAULT NOW(); supplier->subject_code may be null. */ function linkProjectToSupplier(Project $project, SupplierProject $supplier): void { DB::table('project_supplier_links')->insert([ 'project_id' => $project->id, 'supplier_project_id' => $supplier->id, 'platform' => $supplier->platform, // @phpstan-ignore-next-line property.notFound — subject_code is in $fillable/casts, IDE stubs lag 'subject_code' => $supplier->subject_code, ]); }