Testing and automation
What is here, and what is next
Web testing ships today. The rest of the testing story is the direction, not a feature you can click yet.
Software is not only websites. Teams ship desktop apps, APIs, and mobile apps, and they need those to hold up under load and under someone poking at them. Today that usually means a different tool for each kind of test. Many of those tools also guess at the screen with computer vision, instead of sitting in the editor where the code was written.
Gyaanmitra's aim is simpler to say than to finish: if you can build it here, you should be able to prove it here. The integrated browser is the first version of that idea.
Where things stand
Web apps, shipped
The browser and the agent's ability to drive it are in the product. See web automation.
Desktop apps, planned
The same click-and-check idea for native windows on Mac, Linux, and Windows. Not available yet.
APIs, planned
Request, response, and a check that the contract still holds, next to the code that serves it. Not available yet.
Mobile, planned
Android and iOS, in the same workflow as the web. Not available yet.
Penetration testing, planned
Common holes and bad configuration, looked at while you are still building. Not available yet.
Performance, planned
A slowdown noticed in the change that caused it, not after it ships. Not available yet.
The rule for all of it
Verification sits next to the code. The agent still waits for approval. You should not have to learn a second product just to find out whether something works.
This page is a direction, not a release note
There is no public date for the planned items. Follow the repository, or open an issue if a testing workflow should move up the list.