Hi HN! It’s Mustafa. I’m the founder of Preflight (https://preflight.com). Preflight lets anyone test their product by simply recording actions on your browser with a chrome extension to save everyone's time in the company.
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.
So, that'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.
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.
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's easy to communicate with developers what's wrong and you would not release bugs to your users.
When something is wrong, we detect console log errors and network errors on the page.
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's why most of these frameworks feel awkward and cannot mimic the actual user's behavior. We now are working on how your users use your product with programmatically controlled actual keyboard and mouse interaction.
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.
Thank you for reading. I'd love to hear your thoughts and help all of you with any of your QA needs.
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.
So, that'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.
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.
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's easy to communicate with developers what's wrong and you would not release bugs to your users.
When something is wrong, we detect console log errors and network errors on the page.
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's why most of these frameworks feel awkward and cannot mimic the actual user's behavior. We now are working on how your users use your product with programmatically controlled actual keyboard and mouse interaction.
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.
Thank you for reading. I'd love to hear your thoughts and help all of you with any of your QA needs.