Firefox extension/Add-on , Job: Functional changes and code refactor (Important: Requires high-skills in Javascript, jQuery and Selenium IDE)

Hello freelancers, Note: This project required a highly skilled professional in Javascript, jQuery and Selenium IDE recorder functionality to better understand the existing project code. Please do not consider this project if you are not 100% comfortable with the above requirements. If you are confident, please read the below details. I have the source code for a Firefox recorder extension project (basically a Selenium IDE or Katalon recorder) written in Javascript which I took from an open source project to implement for my requirements to work on. Please find the attached Recorder User manual to understand the project layout . For source code: [login to view URL] Current execution scenario : (If not familiar with Selenium IDE refer: [login to view URL]) 1. Recorder records a test case by clicking "Record" button. 2. Play back the test case by clicking on "Play or Play Suite or Play All" button. (Test case executes with the selected/shown target value in label "3" refer user manual Figure: 1) ============================================================= I have web application with webix, which means the elements ID's of the web page will dynamically changes every time I login to the application. So, that is making my test case execution which is recorder prior, to fail because by default the recorder is selecting find element by ID as the Selenium IDE element target values preferred order is ID, Name, Link, CSS and xPath. Now, I could like to make a functional change to the recorder code to execute the test case successfully without getting 'Element not found' exception just by taking only ID as target. Proposed execution scenario: 1. No change. (same as step-1 of current execution scenario) 2. Play back the test case by clicking on "Play or Play Suite or Play All" button. (Execute test case by looping through all the available Target Values of an element in label "5" refer user manual Figure: 1 ). If in case the element target selector 'ID' changed while test case play back, loop and look for next alternative element target selector 'Link' (Figure:1 ; label: 5) . Before sending 'Element not found' error and Test case fail. If all the alternative element targets are not really not found then throw 'Element not found' error and Test case fail. =================================================================== Current source is written in javascript with some asynchronous functions and use of promise. As of my knowledge it could be easier to use jQuery to find element in DOM using the jQuery selectors and use promise to make asynchronous code to synchronous execution flow. And also required code flow documentation prepared and comments in the code as you work. For me to understand the code flow for future purpose. ============================================= Fixed project price, preferred best offer. Please don't bid low and change the price after contact.