When attempting to test connection to Microsoft Edge, older versions of Rapise may fail to automatically download and update the required Edge WebDriver. In this case Rapise shows "Failed to connect to: Edge" error message and the rapise_ide.log file contains "edgedriver_win32.zip download request failed with status code: Conflict, reason phrase: Public access is not permitted on this storage account.". This article explains the underlying cause of this error and provides a manual workaround using Microsoft's updated download URLs.
If you are running Web tests on MS Edge version 133 or 134 (latest version at 2025-03-20) you may receive an error on MS Edge start: "session not created: probably user data directory is already in use, please specify a unique value for --user-data-dir argument, or don't use --user-data-dir (SessionNotCreated)". Learn how to fix it from this article.
When you are recording/running a test via Selenium browser profiles in Rapise - by default a new user profile is created when new instance of a browser is launched. It means that new browser instance starts with empty cache, no cookies, etc. Sometimes it complicates testing. If you are testing a Web application that requires SMS/Email code to authorize a browser then you will have to do it every time. Automation of input of SMS/Email codes may be really hard. It is much easier to authorize a browser manually once and then run tests for long period of time. To make it work you will need to configure a permanent user profile for the browser used for testing. Learn how to do it for Chrome/Edge from this article.