thoughts from the test eye

A few of you know that I have been working on a very powerful tool for software testing.

Bad news first: It is only for Windows and web services, it is self-signed, and it requires LLM credits for full effect.
Good news: It is free, it empowers testers to test faster and better, and it contains LLM-friendly APIs to get an “extra pair of eyes” on your software.

Trowser is, as the name implies, a testing browser, with built-in scripting and APIs for LLM interaction.
It promotes exploratory testing by giving quick access to tools a tester sometimes want to use, scripting abilities for automation and customizations for your unique context.
It also promotes exploratory (or specification-based) testing by LLMs with a well-designed API and wisdom from the exploratory testing community.
Go to any web site, and get valuable feedback from an LLM decently fast.

If you can, I encourage you to try it and see for yourself, download is here:
https://www.thetesteye.com/code/Trowser-1.0.zip
Since it is a browser you should be concerned about security and guardrails, so read /trowserkit/SECURITY.md and maybe wait for people you trust to try it first.

I think the audience is testing practitioners who enjoy rich, exploratory testing, with the purpose of finding important quality-related information about web services.

I hope some of you will be as happy as two early adopters:

“Trowser gave me a full performance, accessibility, and security report on my own site in under five minutes, driven by an LLM, but with me in the loop the whole way.” 
— Christopher Edeson

“The Trowser REST API is genuinely impressive for LLM-driven testing. It gave me everything I needed to perform comprehensive exploratory testing — from page state inspection to form interaction to full audit pipelines — without ever feeling like I was fighting the API. The /api/state endpoint is brilliantly designed: one call gives me the complete picture of the page, interactive elements with ref numbers, headings, console errors, and network errors. The batch endpoint eliminated stale-ref issues during form filling. The audit endpoints (accessibility, performance, security, HTML validation) are exceptionally convenient — what would take a human tester 30 minutes to set up with multiple tools, I did in parallel with five API calls. If I could change one thing, it would be making /api/state/enrich even more prominent in the docs — it’s the kind of power tool that changes how you approach testing. Overall, this is the best browser automation API I’ve worked with for testing. It clearly was designed by someone who understands what testers actually need.”
— Claude Opus 4.6, after testing automationintesting.online via Trowser REST API, March 2026