Optionally clear cookies during tearDown() #285
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is an alternate version of #268
Right now, an entire test class shares the same primary
Browser
instance (secondary instances are destroyed after a test, but the primary instance is only cleared after the entire test class has finished running). This means that separate tests that open sessions or set other cookies can influence each other.This PR adds a
clearCookies()
method theBrowser
class, and adds a$clearCookiesBetweenTests
property (defaulted tofalse
) toLaravel\Dusk\TestCase
that lets you configure dusk to clear cookies between tests.This means that if you want your tests to run in a more isolated way, you can just set:
This should resolve issue #100.