3 ms·

Cypress.io SDK to auto-heal broken UI selectors by Dev Tools (YC S22)

etienne_devtool 4y ago
Hi HackerNews, I am Etienne co-founder of Dev Tools (YC S22) and today we are releasing our SDK for Cypress. We are looking for feedback and suggestions. Do you maintain UI tests? Do they often break because of changes in the underlying HTML? As long as the UI looks the same, you should not have to maintain those tests. We offer a free SDK that will make broken selectors in UI tests a thing of the past. In a few words, the first time you run your tests with our tool we visually identify the UI elements and learn how to recognize them. Next time you run the test, if the selectors are not broken it runs as usual, but if the selectors are broken, we silently kick in and use our backend to try and visually identify the element that has a broken selector. If we find it, then the test will run as usual and you don’t need to do any maintenance. The setup process for our SDK is a few lines of code. The test code itself does not have to change beyond those lines. If that sounds interesting to you, check out our tool at dev-tools.ai, we support Selenium for Python and Java and Cypress for Javascript. A little insight into our tech: We use EfficientDet as our main object detector + some custom code and heuristics We distribute the work using Celery + RabbitMQ and GPU workers We currently are a small team of two, so the frontend is mostly server side rendering with Flask and Jinja. We are also a small startup, and constantly looking for the right features to implement to help testers. If you have feature ideas, suggestions or feedback, please leave us a message here or on Discord Thx
- trinovantes 4y ago
  Will you support Playwright in the future?
  - etienne_devtool 4y ago
    Hi, which language do you use with Playwright? We have plans to support it and we are thinking of starting with Python of JS.
    - trinovantes 4y ago
      I use JS (typescript) with Playwright. I look forward to see it supported!

Hi HackerNews, I am Etienne co-founder of Dev Tools (YC S22) and today we are releasing our SDK for Cypress. We are looking for feedback and suggestions. Do you maintain UI tests? Do they often break because of changes in the underlying HTML? As long as the UI looks the same, you should not have to maintain those tests. We offer a free SDK that will make broken selectors in UI tests a thing of the past. In a few words, the first time you run your tests with our tool we visually identify the UI elements and learn how to recognize them. Next time you run the test, if the selectors are not broken it runs as usual, but if the selectors are broken, we silently kick in and use our backend to try and visually identify the element that has a broken selector. If we find it, then the test will run as usual and you don’t need to do any maintenance. The setup process for our SDK is a few lines of code. The test code itself does not have to change beyond those lines. If that sounds interesting to you, check out our tool at dev-tools.ai, we support Selenium for Python and Java and Cypress for Javascript. A little insight into our tech: We use EfficientDet as our main object detector + some custom code and heuristics We distribute the work using Celery + RabbitMQ and GPU workers We currently are a small team of two, so the frontend is mostly server side rendering with Flask and Jinja. We are also a small startup, and constantly looking for the right features to implement to help testers. If you have feature ideas, suggestions or feedback, please leave us a message here or on Discord Thx

trinovantes 4y ago
Will you support Playwright in the future?
- etienne_devtool 4y ago
  Hi, which language do you use with Playwright? We have plans to support it and we are thinking of starting with Python of JS.
  - trinovantes 4y ago
    I use JS (typescript) with Playwright. I look forward to see it supported!