Funkcionalnosć tutoho sydła so přez wothladowanske dźěła wobmjezuje, kotrež maja waše dožiwjenje polěpšić. Jeli nastawk waš problem njerozrisuje a chceće prašenje stajić, wobroćće so na naše zhromodźenstwo pomocy, kotrež na to čaka, wam na @FirefoxSupport na Twitter a /r/firefox na Reddit pomhać.

Pomoc přepytać

Hladajće so wobšudstwa pomocy. Njenamołwimy was ženje, telefonowe čisło zawołać, SMS pósłać abo wosobinske informacije přeradźić. Prošu zdźělće podhladnu aktiwitu z pomocu nastajenja „Znjewužiwanje zdźělić“.

Dalše informacije

Understanding the working principle behind the recorder in Selenium IDE

  • 1 wotmołwa
  • 2 matej tutón problem
  • 3 napohlady
  • Poslednja wotmołwa wot the-edmeister

more options

We are working on development of a framework on top of Selenium. We want to expose a tool so that users can record actions on the browser. For this, we want to understand how Selenium IDE is able to get information from the controls being recorded.

We feel Selenium IDE is able to record by getting information about the controls by subscribing to the events raised by the firefox browser. Is our understand correct? If not, then we would like to the approach being used to the information from the control.

Any help is highly appreciated.

We are working on development of a framework on top of Selenium. We want to expose a tool so that users can record actions on the browser. For this, we want to understand how Selenium IDE is able to get information from the controls being recorded. We feel Selenium IDE is able to record by getting information about the controls by subscribing to the events raised by the firefox browser. Is our understand correct? If not, then we would like to the approach being used to the information from the control. Any help is highly appreciated.

Wšě wotmołwy (1)