[9.x] Add closure based exceptions testing

[shaffe-fr]

Hi all,

This adds new ways to test exception handling using closures.

// Ensure that an exception is thrown
$this->assertThrows(fn () => throw Exception(''));

// Ensure that a specific type of exception is thrown
$this->assertThrows(
    fn () => (new SomeActionThatThrowsExceptions)->execute(), 
    CustomException::class
);

// Ensure that an exception is thrown with a specific message
$this->assertThrows(fn () => throw Exception('My message'), Exception::class, 'My message');

// Ensure that no exceptions are thrown
$this->assertDoesntThrow(
    fn () => (new SomeActionThatWorksFine)->execute()
);

// Ensure that a specific type of exception is thrown with the given message
$this->assertThrowsWithMessage(
    fn () => (new SomeActionThatThrowsExceptionsWithCustomMessage)->execute(), 
    'My custom exception message'
);

[taylorotwell]

Can you elaborate a bit on why you would need assertDoesntThrow? Wouldn't PHPUnit fail anyways if there was an unexpected exception?

[taylorotwell]

Please mark as ready for review once you have responded.

[shaffe-fr]

Hi @taylorotwell,
assertDoesntThrow will only bubble exceptions of the given type. Other exceptions will be ignored.
After some thoughts, I don't think it's a behaviour we want or expect for an assertion with this name.
I removed the method.

[DarkGhostHunter]

You can also use a try-catch block if you need to assert something during the exception handling.

[shaffe-fr]

@DarkGhostHunter I think this is a quality of life improvement among many others in Laravel.
One might argue the tap helper is overkill because we can use separated statements.