Automated Testing for Lovable Projects
Just enter your URL or connect to Github. Squidler scans the project to ensure everything works and gives you the solutions to solve the problems.
Get started
How it works
The Interface
ur time is valuable, and it should not be spent fiddling with tools more than needed. Squidler does its utmost to get out of your way.
You'll get emails for the problems you're interested in, either when they're found or in weekly digests. Links to found problems are sharable, so you can send them to developers or other technical staff.
You can also integrate Squidler by email or directly with Slack.
Testing with a Browser
Many tools for scanning and testing websites automatically only consider HTTP responses — status codes, headers, and server-side rendered HTML.
However, with many modern websites and apps using JavaScript, such tools have a problem assessing content rendered after the page is loaded.
Not only that, anything requiring user interaction to be rendered, like opening a modal window, is out of reach.
Generative & Continuous Testing
Generative testing means that Squidler generates test cases on its own. In practice, it's an iterative process of finding the possible actions at any step, and using a combination of randomness and heuristics to select the next action.
There are two core aspects to the effectiveness of Squidler: generative and continuous testing. The combination is the heart of the service.
FAQ
Unlike most tools that only analyze HTTP responses (status codes, headers, server-side HTML), Squidler uses a real browser to render and interact with websites and apps. This allows it to assess content rendered after the page loads, including elements that require user interaction, like modals and dynamic content.
Squidler can test all types of websites and apps, including static websites, server-side rendered sites, progressive web apps (PWAs), and single-page apps (SPAs). As long as the content renders to the DOM, Squidler can assess it.
Generative testing is an iterative process where Squidler autonomously generates test cases. It explores possible actions step-by-step, using randomness and heuristics to decide the next actions to test, ensuring a comprehensive evaluation of the website.
Continuous testing means that Squidler runs tests consistently as the website evolves. By combining generative and continuous testing, Squidler ensures ongoing, real-time validation of your website’s performance and user experience.
Squidler uses a user-centric evaluation approach. It evaluates the behavior of a virtual user interacting with the website, just as a human would. This black-box method identifies issues that may arise from multi-step interactions, like a bug that only appears after a modal window is opened and closed.
Still have questions?
We value your input and are here to help! For support, bug reports, or feature suggestions, please contact our support team via email or through our Slack integration. Your feedback is essential for making Squidler even better.
Contact us