Tests Generator

[alainvd]

This pull request includes foundational components for testing your application by generating model factories, HTTP tests, unit tests, and test case stubs for common code paths.

Before merging, you need to:

• Checkout the shift-117163 branch
• Review all pull request comments for additional changes
• Run composer update
• Run vendor/bin/phpunit
• Review the incomplete tests

[alainvd]

⚠️ Shift could not verify the following core testing files since they differed from the default Laravel version. You should compare these files against the Laravel 10 versions to review any differences:

• phpunit.xml
• tests/CreatesApplication.php
• tests/TestCase.php

[alainvd]

❌ Shift could not generate factories for your application models. This is often due to a failure when running the php artisan migrate:fresh from the Shift build server.

Shift added a factory generator package as a development dependency so you may generate your model factories locally.

To do so, run php artisan generate:factory. You may use the --force option to regenerate any partial factories added by Shift or pass the model name to regenerate a specific factory.

[alainvd]

ℹ️ Using your routes, Shift generated HTTP tests for 42 Controllers. While test cases were stubbed using the route definitions and inspecting the return statements within the controller action, they are marked as incomplete for you to review and add any remaining setup and assertions. You may review the documentation on HTTP Tests for additional reference.

[alainvd]

ℹ️ Shift generated unit tests for 4 Form Requests. While test cases were stubbed for each of the existing methods, they are marked as incomplete for you to review and add any remaining setup and assertions. You may review this alternative Form Request testing strategy as a guide to how these unit tests are written.

[alainvd]

ℹ️ Shift generated tests for 89 Commands. While test cases were stubbed to call the command, they are marked as incomplete for you to review and add any setup and assertions. You may review the documentation on Console Tests for additional reference.

[alainvd]

ℹ️ Shift set some basic testing configuration values in your phpunit.xml file. Depending on your application, you may need to adjust these.

For example, the database was configured to use SQLite. However, your application may depend on a specific database. As such, you will want to set up and configure an equivalent database for testing.

Shift also changed any <server> configuration elements to <env> elements to address configuration precedence.

[alainvd]

⚗️ This Shift pairs with the Confident Laravel video course. If you are getting started with testing Laravel applications, it will guide you step-by-step from writing your first test to a confidently tested Laravel application.