Testing & Automation
The Automation Roadmap
Gunamaya's mission doesn't stop at web apps. Here's what's shipped today, and the direction the platform is being built toward.
Software isn't only websites. Teams ship desktop applications, APIs, mobile apps, and systems that need to hold up under load and hostile input — and today, proving each of those works usually means reaching for a different tool for every category. Gunamaya's long-term goal is to bring that same "build it, then prove it, in the same window" experience introduced by the Integrated Browser to all of them.
Where things stand today
Web app automation — shipped
The Integrated Browser and Gunamaya AI's ability to drive it are fully built and working today. See Web App Automation.
Desktop application testing — planned
Extending the same click-and-verify model to native desktop UIs, so testing a desktop app doesn't require a completely separate toolchain from testing a web app.
API testing & automation — planned
First-class request/response testing and contract verification, wired into the same editor and Gunamaya AI workflow used for everything else.
Mobile automation (iOS & Android) — planned
Bringing app builds, device or simulator testing, and Gunamaya AI-assisted verification for mobile apps into the same workflow as desktop and web.
Security & penetration testing — planned
Tooling to help identify common vulnerability classes and misconfigurations as part of the normal development loop, not a separate audit phase bolted on at the end.
Performance testing — planned
Load and performance profiling that surfaces regressions while you're still writing the change that caused them, rather than after it ships.
The principle behind all of it
Every category above is being built against the same rule the Integrated Browser already follows: verification should live next to the code, use the same approval-based workflow as everything else Gunamaya AI does, and never require you to learn a completely separate tool just to find out whether something works. An IIDE that can build any kind of software should be able to test any kind of software too.
This is a living roadmap, not a changelog
Timelines for the planned categories above aren't fixed publicly yet. Follow the GitHub repository for progress, or open an issue if there's a testing workflow you'd like to see prioritized.