![]() ![]() 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. You want to pin a specific browser version and check that version number into your source code repository, so that you can check out old commits and branches and re-run the tests against the browser binary from that point in time.You want consistent, reproducible results across repeated test runs-but this may not happen if the browser executable or binary decides to update itself in between two runs.However, as a developer running a suite of end-to-end tests you might have an entirely different perspective: Users are happy to know they’re running an up-to-date and secure browser version including modern Web Platform features, browser features, and bug fixes at all times. One of Chrome’s most notable features is its ability to auto-update. Auto-update: great for users, painful for developers Today, we’re announcing a change that hopefully eases some of this pain. At the same time, setting up an adequate browser testing environment is notoriously difficult, so much so that it’s consistently reported as a top web developer pain point. Backgroundīrowser testing is a vital component of creating a high-quality web experience, regardless of whether it is done manually or automatically. Note: Chrome for Testing has been created purely for browser automation and testing purposes, and is not suitable for daily browsing. This article explains why the Chrome team felt this was needed, and walks through concrete examples where Chrome for Testing might benefit you as a developer. The tray opens when you've finished downloading a file and automatically dismisses itself, making it easy to access quickly and allowing you to continue browsing uninterrupted.Today we’re happy to announce Chrome for Testing, a new Chrome flavor that specifically targets web app testing and automation use cases. When a download is in progress, an animated ring helps you monitor it with a quick glance. The new download tray is available to the right of the Chrome address bar and replaces the legacy downloads experience at the bottom of your screen. Was no longer modern, interactive, and consistent with the look and feel of other browser UI or the browser ecosystem at largeĪll this made it clear that there was room for improvement for us to create a more intuitive experience for downloading in Chrome. Occupied precious pixels at the bottom of the screen which squeezed the web content area, and was limited by screen width in how many files it could show at onceĭidn't go away automatically, and only offered actions such as pause/resume and open in folder from a fixed overflow menu ![]() We learned that while there was a lot about it that worked well for you, like strong support for core download journeys and built-in protection from potentially harmful files, it had its problems too. Over the years, we have listened to your feedback about the legacy Chrome downloads experience. What influenced your decision to redesign Chrome downloads?ĭownloads are a core part of day to day web browsing, from getting the perfect cat themed background for your PC to saving a copy of your tax return. Let's go behind the scenes and learn more about this redesign from Chrome Senior Product Manager Jasika Bawa. With the latest release of Chrome for desktop we are introducing a redesign of the Chrome downloads experience to make it easier for you to interact with your recent downloads. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |