Edit

Prerelease testing using preview channels

  • Article

Prerelease testing means testing your WebView2 app by using the preview channels of Microsoft Edge to find issues that will affect your particular WebView2 app, before any changes ship in the Stable Evergreen WebView2 Runtime. This helps catch any bugs before they degrade the app experience for end users.

Conduct both automated and manual testing:

  • For automated testing, do prerelease testing, which means testing with a preview version of the WebView2 Runtime. Covered by the present article.
  • For manual testing, use self-hosting, which means deploying a preview version of the WebView2 Runtime with your app, to use daily by your team. See Self-host by deploying preview channels.

Importance of prerelease testing

Evergreen WebView2 is based on the evergreen Chromium platform, which receives monthly major updates. Regressions in WebView2 apps tend to be application-specific, rather than affecting all WebView2 apps. WebView2 is tested in a variety of general scenarios, but it's possible that some of the specific scenarios of your app are not covered.

To catch app-specific regressions before WebView2 changes ship in Edge Stable, test your WebView2 app against the preview WebView2 Runtime that's shipped with the preview channels of Microsoft Edge (Canary, Dev, and Beta). To manually install the preview channels, go to Become a Microsoft Edge Insider. The preview channels are also called Insider channels.

Start by doing automated testing against Edge Canary

Start with automated testing against the Microsoft Edge Canary channel, which ships daily. This enables you to catch issues as early as possible. The Microsoft Edge Dev channel ships weekly, and is also a good option.

Start with automated testing against the preview WebView2 Runtime in the Microsoft Edge Canary channel, which ships daily. This enables you to catch issues as early as possible. The Microsoft Edge Dev channel ships weekly, and is also a good option.

To do automated testing:

  1. Set the preview channel for your app.

    You can set the preview channel by using ChannelSearchKind, so that your WebView2 app uses the least-stable channel (Canary, then Dev). To do this, see Switching the channel search order (recommended) in Test upcoming APIs and features.

  2. Install or deploy the preview channel.

  3. Conduct automated testing on your app running against the preview channels.

    You can use WebDriver to conduct automated testing of your WebView2 app. See Automate and test WebView2 apps with Microsoft Edge WebDriver.

  4. Compare the results with the baseline.

    The baseline for testing should be the latest stable release of WebView2, which can be either the Evergreen WebView2 runtime, or the latest fixed-version Runtime. You can download the Runtime from the Microsoft Edge WebView2 page.

Upon finding issues, you can report them via the Microsoft Edge / WebView2Feedback repo. Under the Runtime Channel section, be sure to indicate that you found the issue on a preview channel, so that the fix can be prioritized before the bug ships in the Stable release.

See also