Selenium automation with Celers
Selenium automation that writes itself
Selenium scripts break when a page changes and take time to write. Celers records the browser, keeps several locators for every element, waits properly, and repairs a step when a page moves things around.
Several locators per element
Text, attributes and position are kept together, so one changed id does not break the run.
Real waits
Waits for an element, a page or a download instead of fixed sleeps.
Debugger
Breakpoints, step over, step into, and replay of a failed step with the variables shown.
Your Chrome
Runs in Google Chrome with its own profile per automation, so sign-ins persist.
How selenium automation works in Celers
- 1Record the test or task in Chrome.
- 2Add assertions or data steps on the canvas.
- 3Debug with breakpoints.
- 4Schedule it or export it to Python.
Questions
- Is it a Selenium IDE replacement?
- It covers recording and replay like Selenium IDE, and adds loops over data, schedules, queues, desktop apps and a debugger.