Testing and automation
Build it, then prove it
An IDE should not stop at the last keystroke. It should help you see whether the software does what you meant.
Writing code and checking code usually live in different apps. You edit, then you tab away to a browser or a test tool to find out if you were right. Gyaanmitra pulls that check back into the same window, starting with a real browser beside the code.
Integrated browser
A Playwright browser in the editor. Tabs, DevTools, screenshots, and a way to pretend you are on a phone.
Web automation
Click through the app yourself, or let the agent do it and show you what it found.
When a test fails
Breakpoints, stepping, and the Problems panel are the same tools you use for the rest of the code.
What is next
API, desktop, mobile, performance, and penetration testing. Named honestly, because they are not shipped yet.
Why this is built in, not bolted on
An extension can open a URL. It usually cannot give you a real browser with DevTools and screenshots in an editor tab. The integrated browser is part of the workbench, with Playwright underneath, so the agent and you get the same kind of access a dedicated browser tool would.
Today, and later
Web testing is the part that works now. It is also the check most people need most often. The wider aim is every kind of software: desktop apps, APIs, phones, security, and speed. The roadmap says what is real and what is still being built.
If you are new here
Read the integrated browser first, then web automation for driving it by hand or with the agent.