respect-validation/tests/feature/Rules/CallTest.php
Henrique Moody 94daa8d669
Use Pest instead of PHPT files
Although I love PHPT files, and I've done my fair share of making it
easier to write them in this library, they're very slow, and running
them has become a hindrance.

I've been fidgeting with the idea of using Pest for a while, and I think
it's the right tool for the job. I had to create a couple of functions
to make it easier to run those tests, and now they're working really
alright.

I migrated all the PHPT files into Pest files -- I automated most of the
work with a little script using "nikic/php-parser"; this commit should
contain all the previous PHPT tests as Pest tests.

The previous integration tests would take sixteen seconds, and the Pest
tests take less than a second.
2024-12-16 17:07:47 +01:00

38 lines
1.1 KiB
PHP

<?php
/*
* Copyright (c) Alexandre Gomes Gaigalas <alganet@gmail.com>
* SPDX-License-Identifier: MIT
*/
declare(strict_types=1);
test('Scenario #1', expectMessage(
fn() => v::call('trim', v::noWhitespace())->assert(' two words '),
'"two words" must not contain whitespaces',
));
test('Scenario #2', expectMessage(
fn() => v::not(v::call('stripslashes', v::stringType()))->assert(' some\thing '),
'" something " must not be a string',
));
test('Scenario #3', expectMessage(
fn() => v::call('stripslashes', v::alwaysValid())->assert([]),
'`[]` must be a suitable argument for `stripslashes(string $string): string`',
));
test('Scenario #4', expectFullMessage(
fn() => v::call('strval', v::intType())->assert(1234),
'- "1234" must be an integer',
));
test('Scenario #5', expectFullMessage(
fn() => v::not(v::call('is_float', v::boolType()))->assert(1.2),
'- `true` must not be a boolean',
));
test('Scenario #6', expectFullMessage(
fn() => v::call('array_shift', v::alwaysValid())->assert(INF),
'- `INF` must be a suitable argument for `array_shift(array &$array): ?mixed`',
));