A versioned binary that’s as close to regular Chrome as possible without negatively affecting the testing use case. # The solution: Chrome for Testingĭesigned to solve these problems, Chrome for Testing is a dedicated flavor of Chrome targeting the testing use case, without auto-update, integrated into the Chrome release process, made available for every Chrome release. Third, Chromium is different from Chrome. Second, they are built and published separately from the Chrome release process, making it impossible to map their versions back to real user-facing Chrome releases. First, these Chromium binaries are not reliably available across all platforms. Not only do you have to download a Chrome binary somehow, you also need a correspondingly-versioned ChromeDriver binary to ensure the two binaries are compatible.ĭue to there being no good way to solve these issues, we know that many developers download Chromium (not Chrome) binaries instead, although this approach has some flaws. This is great for users, but painful for developers needing to reproduce a bug report in an older Chrome version.Ī more specific example of this problem is when you want to use ChromeDriver for browser automation. Google intentionally doesn’t make versioned Chrome downloads available, since users shouldn’t have to care about version numbers-they should always get updated to the latest version as soon as possible. # Versioned browser binariesĪuto-update aside, you might also have found it hard to find a Chrome binary with a specific version. This is the fundamental mismatch between what’s good for regular browser users versus what’s good for developers doing automated testing. As a result, you may not want to use your regular Chrome installation for automated testing. None of this is possible with an auto-updating browser binary.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |