respect-validation/tests/feature/Rules/ArrayValTest.php
Henrique Moody d3239e878d
Change how we're writing Pest tests
The problem with the current approach is that the "expect()" calls
happen inside "tests/Pest.php". That means that when something fails, we
can't easily know which exact expectation has failed.

This commit will change the helper functions, and will make the tests
more verbose, but event with that, the developer experience is better.
2025-12-18 14:02:33 +01:00

28 lines
920 B
PHP

<?php
/*
* Copyright (c) Alexandre Gomes Gaigalas <alganet@gmail.com>
* SPDX-License-Identifier: MIT
*/
declare(strict_types=1);
test('Scenario #1', catchMessage(
fn() => v::arrayVal()->assert('Bla %123'),
fn(string $message) => expect($message)->toBe('"Bla %123" must be an array value')
));
test('Scenario #2', catchMessage(
fn() => v::not(v::arrayVal())->assert([42]),
fn(string $message) => expect($message)->toBe('`[42]` must not be an array value')
));
test('Scenario #3', catchFullMessage(
fn() => v::arrayVal()->assert(new stdClass()),
fn(string $fullMessage) => expect($fullMessage)->toBe('- `stdClass {}` must be an array value')
));
test('Scenario #4', catchFullMessage(
fn() => v::not(v::arrayVal())->assert(new ArrayObject([2, 3])),
fn(string $fullMessage) => expect($fullMessage)->toBe('- `ArrayObject { getArrayCopy() => [2, 3] }` must not be an array value')
));