Clearer error reporting on seeInDatabase()

[markokeeffe]

I seem to spend a fair amount of time debugging my unit tests when I encounter an "Unable to find row in database table ..." error using the seeInDatabase() method. The output tells me the data I was looking for in the table (which is already in my unit test) and I have to add extra code such as $allRows = MyModel::all()->all() before calling $this->seeInDatabase(...) and stepping through with a debugger to see what data is in the table to find out where I'm going wrong.

I can only assume that other people are having a similar experience, I think anyone using an in-memory sqlite database for unit testing will have some frustration debugging these errors.

This change executes a second "SELECT * FROM {table}" query if the count is zero, and formats the JSON data for better reading in the console.

[sileence]

@markokeeffe please check #16679

This will be available for Laravel 5.4 (next week).

[sileence]

@markokeeffe maybe you could improve from there (adding the pretty print or anything else you might consider).

[GrahamCampbell]

Already in Laravel 5.4. If there are any other changes you'd like to see, please send a PR to 5.4. :)