Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

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

Jump to bottom

Extending from Laravel\BrowserKitTesting\TestCase lose assertions that I already know/have #133

Closed
brainlet-ali opened this issue Apr 22, 2020 · 1 comment
Closed

Extending from Laravel\BrowserKitTesting\TestCase lose assertions that I already know/have #133

brainlet-ali opened this issue Apr 22, 2020 · 1 comment

Comments

@brainlet-ali
Copy link

When I install and use this package, I no longer have access to assertions like:

  • assertStatus
  • assertOK

And rather I'm forced to use assertResponseStatus which doesn't feel natural and asking me the leave the testing API that I already know.
@brainlet-ali brainlet-ali changed the title Extending from Laravel\BrowserKitTesting\TestCase loses assertions that I already have.1 Extending from Laravel\BrowserKitTesting\TestCase lose assertions that I already have.1 Apr 22, 2020
@brainlet-ali brainlet-ali changed the title Extending from Laravel\BrowserKitTesting\TestCase lose assertions that I already have.1 Extending from Laravel\BrowserKitTesting\TestCase lose assertions that I already know/have Apr 22, 2020
@driesvints
Copy link
Member

Think you're confusing Browser Kit Testing with the regular TestCase class of Laravel. They're two different things.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@driesvints @brainlet-ali