Test apps behind Windows sign-in
Runs can sign in to apps that use Windows single sign-on: set the domain account as project variables and the runner gets a Kerberos ticket before it starts.
Wopee.io · Changelog
Product updates and improvements, as they ship to production.
Running in productionAPI v5.241.0CMD v3.458.3Agent v3.146.0since
Runs can sign in to apps that use Windows single sign-on: set the domain account as project variables and the runner gets a Kerberos ticket before it starts.
Ask the chat for a test no user story covers yet and it proposes the story and the test together, in one change you can review and apply.
On very large pages the agent reads what is on screen in full and a short outline of the rest, then searches or opens the regions it needs.
A defect the agent sees more than once is reported once, with every sighting under it, and the run log ends with the agent's verdict, not just Playwright's.
An HTTP request step can keep a token from the response as a hidden value that later steps use, and it can call your API on another domain.
Asking the chat to generate tests now updates your suite; anything that would replace existing tests or steps waits until a project admin confirms it.
The Users screen shows each member's access to the project's GitHub repository, with resend, retry and connect actions, and access follows project membership.
Paste a screenshot into the chat, point it at a story or test with @, and review each change it proposes as a readable preview before you apply it.
An agent question now shows one recommended option and a two-minute countdown; with no answer the run continues with that option and the chat says so.
A failed run in a project with a linked repository offers Create GitHub issue, filled with the failing step, expected and actual result and the screenshot.