Selenium JavaScript Python C#, Cypress, TestCafe, Playwright, Squish selector generation has been added to Selenideium
Tags: testautomation, selenide, selenium, cypress
Published: 2022-03-03 08:55:50

---
title: Selenium JavaScript Python C#, Cypress, TestCafe, Playwright, Squish selector generation has been added to Selenideium
published: true
date: 2022-03-03 08:00:07 UTC
tags: testautomation, selenide, selenium, cypress
canonical_url: https://mszeles.com/selenium-javascript-python-c-cypress-testcafe-playwright-squish-selector-generation-has-been-added-to-selenideium-element-inspector-v20
---
![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/2zdc3mirfs2uq0emuicq.PNG)
Awesome news!

The new version of Selenideium Element Inspector can be downloaded from the [Chrome web store](https://chrome.google.com/webstore/detail/selenideium-element-inspe/mgfhljklijclnfeglclagdeoiknnmnda).

So let's have a look, what are the **new features**

- **Automatically generating complete copy-pastable line of code for the following frameworks** :

- **Selenium JavaScript**

- **Selenium Python**
- **Selenium C#**
- **Cypress**
- **TestCafe**
- **Playwright**
- **Squish**

and of course also for

- **Selenide**
- **Selenium Java**

- **Provide an option to select the testing frameworks for which selectors will be generated**

[Download Selenideium Element Inspector v2.0](https://chrome.google.com/webstore/detail/selenideium-element-inspe/mgfhljklijclnfeglclagdeoiknnmnda), and have fun.

[Please leave a review](https://chrome.google.com/webstore/detail/selenideium-element-inspe/mgfhljklijclnfeglclagdeoiknnmnda) in case you find the plugin useful!

[Buy me a coffee in case you save time by using Selenideium Element Inspector!](https://buymeacoffee.com/mikiszeles)😊

As usual, we will continue with the implementation details.

## Refactor again

In case you had a look at the code, you could see we still have some duplication, so it is time to get rid of that.

As my plan is to add support for many testing frameworks, it makes sense in case I create a common class for them. Before we do that, I have replaced variable declaration vars with lets inspired by [this](https://maximilianocontieri.com/code-smell-116-variables-declared-with-var#ckzyznrsc01akjznv24wc56m8) article.

So let's create SelectorGenerator class:

![Selector Generator Class JavaScript Source Code](https://cdn.hashnode.com/res/hashnode/image/upload/v1645591798869/52PY2KmVt.png?auto=compress,format&format=webp)

Let's create the Selenide specific subclass: ![Selenide Selector Generator Class JavaScript Source Code](https://cdn.hashnode.com/res/hashnode/image/upload/v1645592008542/9yQ7bo1cL.png?auto=compress,format&format=webp)

Create the Selenium Java-specific class: ![Selenium Java Selector Generator Class JavaScript Source Code](https://cdn.hashnode.com/res/hashnode/image/upload/v1645592114082/fjFz6qSOP.png?auto=compress,format&format=webp)

And as a final step, let's refactor _content.js_ to use the new classes: ![Content.js After Being Refactored To Use The Selector Classes JavaScript](https://cdn.hashnode.com/res/hashnode/image/upload/v1645592311490/KU8lIrs1C.png?auto=compress,format&format=webp)

And that's it. It is very important to keep your codebase clean with frequent refactoring.

I wanted to separate the classes into their own JavaScript files, but as I am new to JavaScript I miserably failed with that. After a few hours, I gave up. I constantly got the following error: _> SyntaxError: Cannot use import statement outside a module I tried to specify "type": "module", exporting, importing classes in different ways_, but I could not solve it. If you could help me, that would be awesome.

Let's start feature development

## Adding Selenium Python support

It is so easy to add support for any testing framework:

![Selenium Python Selector Generator Class JavaScript Source Code](https://cdn.hashnode.com/res/hashnode/image/upload/v1645592695616/CdMTM9zIj.png?auto=compress,format&format=webp)

## Adding Selenium C# support

![Selenium CSharp Selector Generator Class JavaScript Source Code](https://cdn.hashnode.com/res/hashnode/image/upload/v1645595678902/w39eTzSDR.png?auto=compress,format&format=webp)

## Adding Selenium JavaScript support

![Selenium JavaScript Selector Generator Class JavaScript Source Code](https://cdn.hashnode.com/res/hashnode/image/upload/v1645647627112/KSIn2V3PX.png?auto=compress,format&format=webp)

Adding Cypress support So let's see how we can add Cypress support:Cypress Selector Generator Class ![Cypress Selector Generator Class JavaScript Source Code](https://cdn.hashnode.com/res/hashnode/image/upload/v1645595588692/EqsTypek1.png?auto=compress,format&format=webp)

Adding Playwright support Adding Playwright is as easy as adding any other framework support: ![Playwright Selector Generator Class JavaScript Source Code](https://cdn.hashnode.com/res/hashnode/image/upload/v1645653753658/pAS7i9IPn.png?auto=compress,format&format=webp)

Adding Squish and TestCafe support I was talking with my colleagues from the company and I found out they are using Squish and TestCafe, so it was no question whether I will implement them or not.

![Squish Selector Generator Class JavaScript Source Code](https://cdn.hashnode.com/res/hashnode/image/upload/v1645896579625/wNpS130rsN.png?auto=compress,format&format=webp)

Adding TestCafe: ![TestCafe Selector Generator Class JavaScript Source Code](https://cdn.hashnode.com/res/hashnode/image/upload/v1645896674780/XL-gT2rw8.png?auto=compress,format&format=webp)

And that's it. We have added support for all testing frameworks planned for Selenideum Element Inspector v2.0. In case I missed your favourite framework, just create a ticket on [GitHub](https://github.com/mszeles/selenideium-element-inspector/issues), and I will implement it as soon as I can. 😊

After this, a few hours of debugging came. For some unknown reason, one selector for each framework appeared as "undefined". I filled the code with logs and also debugged the code without any success.

In the end, I refactored storing the selector into its own method, so I can log the stack trace in case I get an undefined value: ![Store Selector Method Source Code](https://cdn.hashnode.com/res/hashnode/image/upload/v1645896898201/qfY7uy_n1.png?auto=compress,format&format=webp)

In the end, I found out I accidentally stored the return value of one of the generator functions which stores the selectors and it has no return value.

Let's do something more interesting to close this article

## Configuring for which framework to generate selectors

As we have added Selenide, Selenium Java, Selenium Python, Selenium C#, Selenium JavaScript, Cypress, TestCafe and Playwright support we are logging too many selectors unnecessarily. In order to avoid that, let's make the frameworks selectable.

There are 3 steps we have to do:

- Create an options page and add checkboxes for the frameworks to the UI
- Store and load settings in chrome storage
- Log selectors only for the selected frameworksCreate an options page and add checkboxes for the frameworks to the UI

## Create an options page and add checkboxes for the frameworks to the UI

This is easy, here is the _options.html_: ![Adding Configuration Options To Log Selectors Only For The Selected Frameworks HTML Code](https://cdn.hashnode.com/res/hashnode/image/upload/v1646174951834/5u01lamQY.png?auto=compress,format&format=webp)

We also need a small CSS file _options.css_: ![CSS File For Options HTML Page](https://cdn.hashnode.com/res/hashnode/image/upload/v1646175063996/_yJRtGt3C.png?auto=compress,format&format=webp)

## Store and load settings in chrome storage

Well, this is tricky part number 1. It took me hours of trial and error and googling and also some help from my colleague [Zsolt Ilonca](https://www.linkedin.com/in/zsolt-ilonczai-801a44122/) to solve this. We did not really became friends with the assynchronity of JavaScript. To be honest, I am pretty sure the code could be much simpler, so please do not hesitate to share your improvement suggestions with me. 🙏

Basically what we are doing is restoring the settings from Chrome local storage on the DOMContentLoaded event and we are adding click event listeners for the inputs, based on which we update the local settings.

This is the _options.js_ file: ![Options JavaScript file](https://cdn.hashnode.com/res/hashnode/image/upload/v1646175503290/FSuI0GiaH.png?auto=compress,format&format=webp)

Let's continue with the last step.

## Log selectors only for the selected frameworks

Here again, Javascript async/await tricked me so it again took me a few hours to implement this. Here is the relevant part of the _content.js_ code: ![Content.js Log Selectors Only For The Selected Frameworks JavaScript](https://cdn.hashnode.com/res/hashnode/image/upload/v1646249727542/g9VgNccsB.png?auto=compress,format&format=webp)

Aaaand we are done. It is time to submit the plugin into the Chrome Web Store and to wait a few days to be accepted, then I will immediately post this article. 😊

Download the plugin: [Selenideium Element Inspector](https://chrome.google.com/webstore/detail/selenideium-element-inspe/mgfhljklijclnfeglclagdeoiknnmnda/).

P.S.: **Thanks for sharing the article**. 👍

📚 **Join the Selenide community on** [LinkedIn](https://www.linkedin.com/groups/9154550/)! ✌

[Buy me a coffee!](https://buymeacoffee.com/mikiszeles)