Development Guide

This section documents the development workflow for contributors working on the revolution/laravel-boost-copilot-cli package source code. It covers local environment setup, test infrastructure, code quality tooling, and CI/CD pipelines.

For end-user installation and usage, see Getting Started. For runtime architecture, see Core Architecture.

---

Overview

The package uses Orchestra Testbench to provide a minimal Laravel application environment for testing, Pest as the test framework, and Laravel Pint for code formatting. All development tasks are executed via Composer scripts.

Core development dependencies:

Package	Version	Purpose
orchestra/testbench	^10.6	Provides Laravel application environment for package development and testing
pestphp/pest	^4.1	Test framework
pestphp/pest-plugin-laravel	^4.0	Laravel-specific assertions and helpers
mockery/mockery	^1.6	Mocking framework for tests
laravel/pint	^1.25	Code formatting based on Laravel style preset

Sources: composer.json16-22

---

Development Dependencies and Autoloading

The package defines PSR-4 autoloading for both production code and development/test code:

Production autoloading:

• Namespace: Revolution\Laravel\Boost\
• Directory: src/

Development autoloading:

• Tests\ → tests/
• Workbench\App\ → workbench/app/
• Workbench\Database\Factories\ → workbench/database/factories/
• Workbench\Database\Seeders\ → workbench/database/seeders/

Sources: composer.json23-35 </old_str> <new_str>

Development Guide

This section documents the development workflow for contributors working on the revolution/laravel-boost-copilot-cli package source code. It covers local environment setup, test infrastructure, code quality tooling, and CI/CD pipelines.

For end-user installation and usage, see Getting Started. For runtime architecture, see Core Architecture.

---

Overview

The package uses Orchestra Testbench to provide a minimal Laravel application environment for testing, Pest as the test framework, and Laravel Pint for code formatting. All development tasks are executed via Composer scripts.

Core development dependencies:

Package	Version	Purpose
orchestra/testbench	^10.6	Provides Laravel application environment for package development and testing
pestphp/pest	^4.1	Test framework
pestphp/pest-plugin-laravel	^4.0	Laravel-specific assertions and helpers
mockery/mockery	^1.6	Mocking framework for tests
laravel/pint	^1.25	Code formatting based on Laravel style preset

Sources: composer.json16-22

---

Package Namespace and Autoloading

The package defines PSR-4 autoloading for production and development code:

Production code:

• Namespace: Revolution\Laravel\Boost\
• Directory: src/
• Classes: CopilotCli, CopilotCliServiceProvider

Development/test code:

• Tests\ → tests/
• Workbench\App\ → workbench/app/
• Workbench\Database\Factories\ → workbench/database/factories/
• Workbench\Database\Seeders\ → workbench/database/seeders/

The service provider Revolution\Laravel\Boost\CopilotCliServiceProvider is auto-discovered by Laravel via the extra.laravel.providers configuration.

Sources: composer.json23-50

---

Composer Scripts

All development tasks are executed via Composer scripts:

Script	Command	Purpose
composer test	pest --compact	Execute full test suite in compact output mode
composer test:coverage	pest --compact --coverage --coverage-clover build/logs/clover.xml	Execute tests with code coverage reporting (Clover XML)
composer lint	pint	Format code using Laravel Pint
composer test:lint	pint --test	Check code formatting without modifying files
composer boost	vendor/bin/testbench boost:install --no-interaction --ansi	Execute boost:install command in the Testbench environment
composer serve	vendor/bin/testbench serve	Start Testbench development server (includes workbench:build)

Automatic post-install scripts:

After composer install or composer update, three scripts execute automatically via the post-autoload-dump hook:

1. clear → vendor/bin/testbench package:purge-skeleton — Removes skeleton files
2. prepare → vendor/bin/testbench package:discover — Discovers packages
3. build → vendor/bin/testbench workbench:build — Builds workbench assets and database

Sources: composer.json53-76

---

Development Workflow

Composer Script Execution Flow

Sources: composer.json53-76 testbench.yaml23-27

---

Repository Structure for Contributors

The relevant directories for contributors are:

Path	Purpose
src/	Package source (CopilotCli, CopilotCliServiceProvider)
tests/	Pest tests (Feature/, ArchTest.php, TestCase.php, Pest.php)
workbench/	Orchestra Testbench workbench app (models, factories, seeders, routes)
resources/boost/guidelines/	Blade template for the AI guidelines file distributed to users
.ai/guidelines/	Blade template for the AI guidelines file used during package development
.github/workflows/	CI/CD workflows (tests, lint, copy-guideline)
pint.json	Pint code style configuration
testbench.yaml	Orchestra Testbench configuration

---

Sub-sections

The child pages of this section cover each topic in detail:

• Development Environment Setup (6.1) — Cloning the repo, composer install, testbench.yaml, composer serve.
• Testing with Orchestra Testbench (6.2) — testbench.yaml settings, the workbench/ directory, and TestCase.php bootstrap.
• Writing Feature Tests (6.3) — CopilotCliTest.php, CopilotCliServiceProviderTest.php, GuidelinesTest.php — what each covers and why.
• Architecture Tests (6.4) — ArchTest.php constraints via Pest's arch(): strict types, no debug functions, no final on Revolution\Laravel\Boost classes.
• Code Quality and Formatting (6.5) — pint.json preset, composer lint, composer test:lint, and the lint.yml workflow.
• CI/CD Pipeline (6.6) — tests.yml PHP matrix, lint.yml, copy-guideline.yml.

---

Test Infrastructure Map

Test file to system under test mapping:

Sources: composer.json28-34