QAssist Session Capture

Send a signed-in browser session for one site you name to your own QAssist instance, for tests that can't drive the login.

QAssist Session Capture hands one signed-in browser session to QAssist, the goal-based AI browser testing tool, so a test can start already logged in. It exists for the logins a test can never drive itself: social login, where the site refuses to serve its form to an automation-controlled browser, and anything else behind a step a script cannot repeat. How it works: 1. In QAssist, open a project's Sessions tab and click "Capture with browser extension". You get a one-time setup code, good for 15 minutes. 2. Sign in to the site you want to capture, in a normal tab, the normal way. 3. Open this extension, paste the code, and name the site. The extension says exactly what it is about to read and where it will go, before Chrome's own permission prompt for that one site. 4. Confirm the account. It captures, posts once to your QAssist instance, and is done. What it does not do: - It never asks for, sees, or stores a password. - It reads one site — the one you name and approve. Never everything you browse. - It sends to one place: the QAssist instance address you typed. There is no server belonging to this extension, no analytics, and no third party. - It never keeps the captured session in the browser. The data is assembled, posted, and dropped. Before every capture it shows you which Chrome profile you are signed in as and makes you confirm, and it refuses to capture at all until you have marked the profile as a test/disposable one in Settings. Capturing your daily personal account should take a deliberate act, not an absent-minded click. QAssist is open source and self-hostable, and this extension talks to whichever instance you point it at — your own or the hosted one. Source: https://github.com/rszhd/qassist