Reading your previous question, I think you are using the Selenium IDE.
Update 2: Check out the Katalon Recorder . This is currently the only extension for the latest Chrome and Firefox compatible with the original Selenium environment.
- Play, record, debug (pause, resume, set breakpoints).
- Report (magazines and screenshots).
- Optionally integrates with Katalon Analytics for historical reporting and advanced analysis.
- Exporting Selenium WebDriver scripts to C # (NUnit and MSTest), Java (TestNG and JUnit), Ruby (RSpec), Python (unittest), Groovy (compatible with Katalon Studio) and Robot Framework

Update 1: Check out Brian Anderson's great post on the status of the Selenium IDE project, as well as its replacement.
Selenium IDE is an old project dating back to Selenium RC. The last time it was updated in 2015 . I don’t think anyone will take the project and transfer it to Chrome.
If you really want to use the Selenium IDE with Chrome, check out Katalon Studio . Katalon Studio is a free alternative to the Selenium IDE. Our team has used it before, and it has some advantages over the Selenium IDE:
- He is still in active development. I get new versions every six weeks or so, with many improvements in each.
- It brings everything together, including WebDrivers for popular browsers and the Android SDK. This means that you only need to download and unzip the package.
- It can record tests both on a web application (Chrome / Firefox / IE, Windows / macOS), and on a mobile application (Android / iOS).
- It runs tests through Selenium 3 (latest version). For advanced use cases, you can run your test on cloud browsers or devices (Sauce Labs, BrowserStack, Kobiton, just to name a few).
- Commands (they call them Keywords) are comparable to Selenese commands, and you can write scripts in Groovy if you know programming. Keyword mode (recording and playback) and Script mode are always interchangeable. This simplifies collaboration between developers and testers, especially with or without limited programming skills.
- It supports Page Object, Data-Driven Testing, etc., and you can add other libraries or extend its functions, because the basic Script is Groovy. I know that some people have successfully used the framework of Siculi or Gallen inside the Catalon. This is an important moment of the transition to Selenium, by the way, - taking advantage of a free and open ecosystem based on the W3C standard instead of locking yourself in with expensive and outdated commercial tools.
- It integrates well with JIRA, and tests can be run through the CLI.
Whatever tool you choose, there are some criteria that you should pay attention to:
- Is the tool an active development? If this is an open source project, you can check their GitHub activity. Otherwise, review the latest release notes. Switching to a new tool is expensive, especially if existing test cases need to be rewritten, so make sure they work for several years.
- Is technology supported by popular browsers and platforms supported? Grant, some browsers suck, but as long as your clients use them, your tests must be executable in these browsers. One of the good news is that the JSON Wire protocol that controls Selenium is hosted and supported by W3C, including Google, Microsoft, Apple and Mozilla.
- How good is its ability to integrate with other QA tools, and is it possible to expand the functionality suitable for your organization?
source share