We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hi
For assertStatus it would be more clean if the consts of Illuminate\Http\Response were used instead of integers.
assertStatus
Illuminate\Http\Response
$response->assertStatus(200); -> $response->assertStatus(Response::HTTP_OK); $response->assertStatus(400); -> $response->assertStatus(Response::HTTP_NOT_FOUND); $response->assertStatus(422); -> $response->assertStatus(Response::HTTP_UNPROCESSABLE_ENTITY);
$response->assertStatus(200);
$response->assertStatus(Response::HTTP_OK);
$response->assertStatus(400);
$response->assertStatus(Response::HTTP_NOT_FOUND);
$response->assertStatus(422);
$response->assertStatus(Response::HTTP_UNPROCESSABLE_ENTITY);
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Hi
For
assertStatusit would be more clean if the consts ofIlluminate\Http\Responsewere used instead of integers.Example
$response->assertStatus(200);->$response->assertStatus(Response::HTTP_OK);$response->assertStatus(400);->$response->assertStatus(Response::HTTP_NOT_FOUND);$response->assertStatus(422);->$response->assertStatus(Response::HTTP_UNPROCESSABLE_ENTITY);The text was updated successfully, but these errors were encountered: