-
Notifications
You must be signed in to change notification settings - Fork 210
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.
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
junit: allow user to reset Browser after each test #1692
Closed
Closed
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -50,13 +50,21 @@ public class Options { | |
public Path outputDir; | ||
// When to record traces. Default is OFF. | ||
public Trace trace = Trace.OFF; | ||
// This should only be used if a new Browser object is needed for each test. | ||
// Usually only necessary when using a cloud testing service | ||
public Boolean closeBrowserAfterEachTest; | ||
|
||
public enum Trace { | ||
OFF, | ||
ON, | ||
RETAIN_ON_FAILURE; | ||
} | ||
|
||
public Options setCloseBrowserAfterEachTest(Boolean closeBrowser) { | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. If we proceed with this option, let's have a test for it. |
||
this.closeBrowserAfterEachTest = closeBrowser; | ||
return this; | ||
} | ||
|
||
public Options setTrace(Trace trace) { | ||
this.trace = trace; | ||
return this; | ||
|
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The behavior of closing the browser (rather than just the context) after each test is very specific to BrowserStack implementation and they could solve it better by providing an API for explicitly marking test start/end instead of binding it to the lifetime of the browser connection.
I'd rather the clients, that need to close browsers after each test, implemented their own fixture and just called
browser.close()
after each test from the fixture. We can addonDisconnect
handler to all browser instances that are created viaPlaywright
fixture and clean-up thread local cache when the event is fired. It would also cover the case when the user callsbrowser.close()
in the middle of a test too, so it's something that would make sense to do in any case.Do you think such approach would make more sense or you'd still prefer to have the option?