phpunit test assertNotRegExp() not working as expected?

Question

Test failed asserting that '{"error":{"message":"Book not found"}}' does not match PCRE pattern "/Book not found/".

Why is this pattern not matching the content string?

<?php

namespace Tests\App\Http\Controllers;

use TestCase;

class BooksControllerTest extends TestCase
{
    /** @test **/
    public function show_route_should_not_match_an_invalid_route()
    {
        $this->get('/books/this-is-invalid');

        $this->assertNotRegExp(
            '/Book not found/',
            $this->response->getContent(),
            'BooksController@show route matching when it should not.'
        );
    }
}

Andrey Tserkus · Accepted Answer · 2016-05-02 16:33:52Z

4

The pattern /Book not found/ does match the content string {"error":{"message":"Book not found"}}. That works correctly.

Note that you're using assertNotRegExp() - i.e. you're literally saying - "Make sure that the pattern does not match the string". So the assertion succeeds when the pattern does not match, and fails when the pattern matches.

Seems like you actually wanted to use assertRegExp() for your test.

answered May 2, 2016 at 16:33

Andrey Tserkus

3,63421 silver badges24 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

Ryderpro Over a year ago

Hmmm. Working through "Writing API's with Lumen." I found I misread a section about updating the route. Fixed the duplicate route with $app->get('/books/{id:[\d]+}', 'BooksController@show'); and now test works. Route does not match that expression it will not be routed to the controller.

Collectives™ on Stack Overflow

phpunit test assertNotRegExp() not working as expected?

1 Answer 1

1 Comment

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

1 Comment

Your Answer

Sign up or log in

Post as a guest

Related