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.

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

Use different browser instances for before/after methods #231

Open
wurzelkuchen opened this issue Oct 27, 2023 · 0 comments · May be fixed by #232
Open

Use different browser instances for before/after methods #231

wurzelkuchen opened this issue Oct 27, 2023 · 0 comments · May be fixed by #232
Assignees
Labels
codeReadyForMerge The issue was implemented and the branch is ready to be reviewed and merged into develop docsNeeded The documenttion needs to be checked if there are changes needed and if so, adaptions should be made
Milestone

Comments

@wurzelkuchen
Copy link
Contributor

If during a test case the browser is crashing, the after method will not be able to do it's cleanup, which might leave the target system in an unstable state, affecting all other tests. (Had this case recently)

Since the cleanup before/after a test case is crucial to keep the general test suite running, it would be good to have them run in separate browser instances by default.

Since it also might be important to do the cleanup on the same browser instance (session, local storage etc.), this should be configurable, maybe via an annotation on the test case.

A unit test which actively kills the browser would be nice.

@wurzelkuchen wurzelkuchen added this to the v5.1.0 milestone Jul 1, 2024
@wurzelkuchen wurzelkuchen added codeReadyForMerge The issue was implemented and the branch is ready to be reviewed and merged into develop docsNeeded The documenttion needs to be checked if there are changes needed and if so, adaptions should be made labels Jul 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
codeReadyForMerge The issue was implemented and the branch is ready to be reviewed and merged into develop docsNeeded The documenttion needs to be checked if there are changes needed and if so, adaptions should be made
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants