-
-
Notifications
You must be signed in to change notification settings - Fork 35
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
feat: Allow specifying the /forcequit argument for WAD #282
feat: Allow specifying the /forcequit argument for WAD #282
Conversation
thank you @papauorg |
Hi @mykola-mokhnach, I adressed your comments for your ultra-fast review :) Thanks for that!
i did sign it. But to be honest it is kind of irritating to sign a 3 page contract for a contribution like this. |
1c5d855
to
4270b44
Compare
Sorry for that, this CLA is common for all OSS projects under Linux Foundation. |
4270b44
to
f779ac1
Compare
## [3.1.0](v3.0.2...v3.1.0) (2024-11-15) ### Features * Allow specifying the /forcequit argument for WAD ([#282](#282)) ([a9dda08](a9dda08))
🎉 This PR is included in version 3.1.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
The WinAppDriver supports a command line argument that will close the program under test ignoring any open windows or message boxes. This is very helpful for avoiding stale open applications in case the test did not properly clean up and close the program or an error occured during testing.
I extended the available capabilities by
ms:forcequit
which can be specified by the test. It will then start the WinAppDriver with an additional argument/forcequit
if set.