Chrome for testing integration #571
Merged
Conversation
This file contains hidden or 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
…n used version for 90 days, check for latest every 7 days
sazid
approved these changes
Jul 21, 2025
|
@mdshakib007 Please put the action usage examples in the description. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
PR Type
New Feature
Overview
With ZeuZ's new "Chrome for Testing" feature, people can now test their web applications across any specific version of Chrome, even on a pre-release build like Dev, Beta, or Canary!
✅ Seamlessly validate cross-version compatibility
✅ Pinpoint bugs in specific Chrome builds
✅ Future-proof your app by testing against upcoming Chrome features
✅ Save time with fully automated version-targeted testing
All you need to do is specify the Chrome version, and - ZeuZ handles the rest!