TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

Show HN: PreFlight (YC W19) – Web apps testing for everyone to save time

1 pointsby mesadbalmost 4 years ago

1 comment

mesadbalmost 4 years ago
Hi HN! It’s Mustafa. I’m the founder of Preflight (<a href="https:&#x2F;&#x2F;preflight.com" rel="nofollow">https:&#x2F;&#x2F;preflight.com</a>). Preflight lets anyone test their product by simply recording actions on your browser with a chrome extension to save everyone&#x27;s time in the company.<p>At ShipBob, we had a lot of UI issues when we scaled from 5 engineers to 30+ engineers. With the new engineers, we released bugs. Because even though we tested our parts the other parts of the software were breaking.<p>So, that&#x27;s why we were so close with customer support. It was a little frustrating to develop and fix at the same time. Because we had to fix the issues right away.<p>And then I thought of building a tool where everyone can create tests by simply recording actions once. So people who are experiencing the same issues that I had would have peace of mind by testing the existing functionalities.<p>So, I built Preflight to save time who are suffering from UI that breaks or the server that stops responding. It can be a Product Manager or Manual QA who wants to create the tests to save time for themselves and developers. And with Preflight it&#x27;s easy to communicate with developers what&#x27;s wrong and you would not release bugs to your users.<p>When something is wrong, we detect console log errors and network errors on the page.<p>The problem with Selenium, Puppeteer, etc is they all push UIEvents on browsers to hack it to work as actual mouse and keyboard interactions. That&#x27;s why most of these frameworks feel awkward and cannot mimic the actual user&#x27;s behavior. We now are working on how your users use your product with programmatically controlled actual keyboard and mouse interaction.<p>We are also working on understanding the context of a test and we are going to be able to run the tests based on context not only based on selectors. For example: add a product to the cart, then go to the checkout page.<p>Thank you for reading. I&#x27;d love to hear your thoughts and help all of you with any of your QA needs.