Pest Testing (Krayin CRM)

Pest Testing in Krayin CRM

When to Apply

Activate this skill when:

• Creating or updating tests (unit or feature)
• Debugging test failures
• Using datasets, mocks, or custom expectations
• Writing architecture or convention tests
• The user mentions test, spec, TDD, expects, assertion, coverage, or verifying behavior

Krayin Testing Structure

Test Locations

Krayin tests are stored in the root tests/ directory:

/tests
├── Feature/
├── Unit/
├── Pest.php
├── TestCase.php
└── CreatesApplication.php

Available Test Suites

Defined in phpunit.xml:

Pest.php Configuration

tests/Pest.php binds the base test case for feature tests:

uses(\Tests\TestCase::class)->in('Feature');

It also defines helper functions you can reuse, such as:

• getDefaultAdmin()
• actingAsSanctumAuthenticatedAdmin()
• getFirstName($fullName)

Running Tests

Run All Tests

php artisan test --compact

Run a Specific Test Suite

php artisan test --testsuite="Feature"
php artisan test --testsuite="Unit"

Run a Specific Test File

php artisan test --compact tests/Feature/ExampleTest.php

Run with Filter

php artisan test --compact --filter=testName

Creating New Tests

Create Feature Test

php artisan make:test --pest ExampleFeatureTest

Create Unit Test

php artisan make:test --pest --unit ExampleUnitTest

Basic Test Structure

it('passes basic assertion', function () {
    expect(true)->toBeTrue();
});

it('returns successful response', function () {
    $response = $this->get('/');

    $response->assertSuccessful();
});

Assertions

Prefer specific response helpers:

Datasets

it('has valid emails', function (string $email) {
    expect($email)->toContain('@');
})->with([
    'james' => 'james@krayin.com',
    'john'  => 'john@krayin.com',
]);

Common Pitfalls

• Forgetting to use assertSuccessful() and other specific helpers
• Skipping --pest when creating tests
• Ignoring helper utilities already available in tests/Pest.php

Testing Best Practices

• Cover happy paths, failure paths, and edge cases
• Keep tests isolated and focused
• Use factories where available
• Follow existing test patterns in the repository