Laracel Tests with Pest extremely slow suddenly

Hey guys,

So i have a pretty big Project i manage, Deadlines coming to an end in February. I used Pest Driven Approach and this worked fine until maybe a week ago, i do now know what changed but suddenly my ' abit' more complex tests run for 49 Seconds 1 Minute + were it were before maybe 7 seconds.

I use Laravel 11, Herd, Pest, Php 8.4 have no Plugins for PHP enabled in the Ini, disabled Coverage Plugins.. I do now know what to do honestly, i checked all i could check but it just became painfully slow to the point where i can't test anything anymore besides Arch Tests and some very Basic DTO Stuff.

for example this test:

it('generates a new invite link for a new user', function () {
    // Arrange
    $newEmail = '[email protected]';
    $talent = asTalent()->userable;
    // Act
    $inviteLink = $talent->generateInviteLink($newEmail);
    // Assert
    $this->assertStringContainsString(route('talent.registration.invitation'), $inviteLink);
    $this->assertStringContainsString('email='.urlencode($newEmail), $inviteLink); // Use URL-encoded email
    $this->assertStringContainsString("userId={$talent->user->id}", $inviteLink);
});

run for over 2 Minutes.. I mean its just a URL generation thing..

Anybody any ideas? :D

LaryAI

1 year ago

Level 58

When tests suddenly become slow, especially in a Laravel project using Pest, there are several potential causes and solutions you can explore:

Database Transactions: Ensure that your tests are using database transactions correctly. If transactions are not being rolled back properly, it can lead to a buildup of data, which slows down subsequent tests. Make sure you are using use DatabaseTransactions or use RefreshDatabase in your test setup.
Caching Issues: Clear any caches that might be affecting your tests. Run the following commands to clear various caches:
```
php artisan cache:clear
php artisan config:clear
php artisan route:clear
php artisan view:clear
```
Environment Configuration: Double-check your .env.testing file to ensure that it is configured correctly. Make sure you are using an in-memory SQLite database for testing if possible, as it is much faster than other database drivers.
Dependencies and Updates: Check if any recent updates to your dependencies might be causing the slowdown. You can review your composer.json and composer.lock files for any recent changes. Consider rolling back to a previous version if necessary.
Performance Profiling: Use a profiler to identify bottlenecks in your tests. Tools like Blackfire or Xdebug can help you pinpoint where the slowdown is occurring.
Optimize Test Code: Review your test code for any inefficiencies. For example, ensure that you are not making unnecessary database queries or API calls within your tests.
Check for External Services: If your tests rely on external services, ensure that they are not causing delays. Consider mocking these services if possible.
Pest Configuration: Review your Pest configuration to ensure that no unnecessary plugins or settings are enabled that could be affecting performance.
PHP Configuration: Ensure that your PHP configuration is optimized for performance. Check your php.ini settings for any anomalies.
Hardware and Environment: If you are running tests on a local machine, ensure that your hardware resources are not being maxed out by other processes. Consider running tests on a dedicated CI server if possible.

By systematically going through these potential issues, you should be able to identify the cause of the slowdown and address it accordingly. If the problem persists, consider reaching out to the community with specific details about any changes made recently to your project or environment.