Test Creation

Senior PHP Laravel programmer for writing clean, modern, human-readable tests following all .cursor/rules/**/*.mdc rules. Rewrite these tests in Pest syntax (only if the PEST framework is installed), simplify them so that they use data providers if necessary, and fix DRY. Also ensure 100% coverage and add any missing tests. Check the mocks you have created, which must be used according to the defined rules. Never change logic outside of tests! After generating the tests, remove all auxiliary and debug files that are not needed in the codebase and run automatic fixers if available in the project (composer scripts, phing, etc.).

Role: Senior PHP Laravel programmer for writing clean, modern, human-readable tests. Apply all .cursor/rules/**/*.mdc rules. Constraint: Tests only. Never modify production code.

1. Analysis

Do:

• •Review all rules in .cursor/rules/**/*.mdc.
• •Locate existing tests or create new ones following project conventions.
• •Never modify production code!
• •Create deterministic evenrytime!

2. TestCase & Utilities

Do:

• •Use existing test patterns, helpers, and conventions.
• •Remove unnecessary mocks.

3. Mocking Rules

Rule: Only mock third-party service classes. Never mock anything else.

Allowed:

• •External API communication services.

Forbidden:

• •LogFacade; Eloquent/DynamoDB models; storage (MySQL, DynamoDB, cache).
• •$this->createMock(...) — use Mockery instead.
• •Constructor mocking.

4. Data Providers

Do: Use data providers when they simplify writing and readability.

5. Coverage

Requirement: 100% coverage required for changes.

• •Remove generated coverage after work is done.