New tool writes and executes checks in the background while developers code, catching breaks before they ever reach a pull request
SAN FRANCISCO, CA A new tool built to remove one of software development’s most tedious chores is now live. LastApp, a testing platform designed for small engineering teams, generates and runs checks on an application the moment new code is pushed no separate QA sprint, no backlog of untested features waiting for attention.
The concept stemmed from a fairly common and obvious problem that is very easy to understand programmers love creating features but absolutely hate testing to ensure that they function properly. This process is generally skipped by most teams either due to time constraints or the fact that they simply hire a team for this task. Both paths leave gaps. Bugs slip into production. Customers find them before the team does.
The platform takes a different approach. As a developer writes and commits code, the tool watches the application’s structure — its screens, its buttons, its data flows — and builds checks that match what’s actually there. When a new button appears, a new check appears with it. When a workflow changes, the check adjusts. There’s no ticket to file, no meeting to schedule, and no test suite that quietly goes stale while the product moves on without it.
“We built this because we were tired of choosing between shipping fast and shipping safe,” said the company’s founder. “Every team we talked to had the same story testing was something they meant to get to, right after the next feature. We wanted testing to just happen, the same way a spell-checker just happens while you type. You shouldn’t have to remember to turn it on.”
Built for Teams Without a QA Department
Automation testing is highly instrumental in making sure that software applications are efficient and reliable. With the use of automation tools like LastApp AI, testing of software applications can be done easily and more efficiently. Most of the early interest in the concept has been generated by smaller firms five-person startups, single founders, agencies managing multiple client-based projects who cannot afford to hire someone for QA purposes but still require assurance that whatever they release will not cause a disruption in any existing application that their customer may use.
The bigger engineering teams have even begun to experiment with it, mostly to reduce the amount of time wasted on brittle test suites which fail as soon as there is any change in the design. One early user, a product manager at a mid-sized e-commerce company, described the switch bluntly: “Our old suite took longer to maintain than the actual app took to build. Half our sprint was fixing tests that had nothing wrong with the product — just wording that changed, or a button that moved three pixels. This just keeps up on its own.”
That maintenance burden is, in many ways, the real problem the company set out to solve. The conventional testing tools are highly accurate but at the same time very brittle. It is possible for a slight change in an interface to make many scripts fail which are not even related to the new bug created. People waste more time managing their test suites than developing new things. By generating test cases based on the construction of the application itself and not on some pre-existing script, the aim is to keep it up-to-date without updating it.
How It Works Day to Day
In practice, a developer doesn’t do anything differently to get the benefit. They write code the way they normally would. In the background, the system tracks what changed, drafts checks that reflect the new behavior, and runs them against the build before it goes any further. In case of failure, the developer knows immediately from the same window that they are using to do work, instead of learning of the failure days later via a bug report or worse yet from a client complaint.
The company says this immediacy is the whole point. Even a delay of just a day in getting the results of testing will convert the fix that would take only five minutes to a significantly lengthier task since the developer will most probably have progressed to other tasks and will need to get back into the context of his earlier work.
The pricing is done in such a way that there is a free package available for individual developers and small scale projects with paid options available for teams that require more frequent test execution. The company has said it plans to keep the core experience — tests appearing automatically as the app is built — free for solo builders indefinitely, treating it as a baseline rather than a limited trial.
Early feedback has focused less on any single feature and more on the sense of relief teams describe once testing stops requiring conscious effort. Several beta users noted that the biggest change wasn’t in bug counts but in confidence a willingness to ship a Friday afternoon change because they trusted the checks running behind it, rather than holding features back until Monday out of caution.
Availability
Automation test is now live, offering support for popular web frameworks right out of the gate and more integrations to come in the next few months according to user demand. The team can sign up for the service, link their project within a matter of minutes, and not have to change anything about their codebase or existing tests.
About the Company
Founded by engineers who were forced to manage their test suites for many years while having no time for maintenance, this firm started developing what they lacked – software that regards testing as an integral component of coding rather than a separate process competing with programming for the engineer’s time. This team of developers is located in San Francisco and remains small and product-oriented.
