Your test runs can finally go all the way on their own
At night, at the weekend, on every commit or release.
2FA Automation for QA Teams
Automate 2FA.
Without disabling it. Without faking it.
Q-Bot drives two-factor authentication on a real smartphone, on demand from your test pipeline. The last manual step of your test runs disappears, without a human in the loop.
When 2FA blocks your tests
Your tests are automated. Until 2FA.
A test suite can automate everything except the validation on a smartphone. A human then has to step in, and until they do, the test stays blocked.
Without Q-Bot
- Automated test
- 2FA step
- Human action required
- Test blocked
With Q-Bot
- Automated test
- 2FA step
- Q-Bot
- Test resumes on its own
How it works
Q-Bot takes over at the two-factor authentication step
When your test reaches the mobile validation, Q-Bot drives the smartphone automatically, runs the 2FA scenario and lets the test carry on with no human intervention.
1
The 2FA step comes up
The test reaches mobile validation.
2
Q-Bot is triggered
One HTTP call starts the scenario.
3
Q-Bot drives the smartphone
It acts inside the genuine 2FA app.
4
The approval goes through
A code, a push or a mobile interaction.
5
The test resumes
The run carries on automatically.
No-code setup
Show it the journey. Q-Bot replays it.
Take a screenshot of the app, place the areas to tap and the wait times. Q-Bot remembers the scenario and then replays it automatically on the real smartphone.
- Capture the screen
- Place the interactions
- Q-Bot replays the journey
The demo
Watch Q-Bot clear a 2FA in 60 seconds
A test reaches the 2FA step. Q-Bot takes over on a real smartphone. The test carries on automatically.
Q-Bot, step by step
Step 1 of 4
The product
A device that sits on the desk
Q-Bot is set up next to the tester's workstation and connects to the company network. No software installation required.
The gesture
A real phone, not a simulator
Q-Bot is connected over USB to a genuine smartphone. It drives the real 2FA app directly and reproduces the interactions a user performs. Not a simulator, not a stub.
Fast validation in seconds
Your data
100 % local
Scenarios stay in the device, on your own network.
Zero data sent to an outside service
The footprint
20 cm on your desk
The format is meant to sit beside the tester's screen and be forgotten, not to take up half the desk.
Benefits
What Q-Bot changes for a test team
It removes the one step test tools cannot get past, without bypassing it: the approval happens in the genuine 2FA app, on a genuine smartphone.
Test on the genuine 2FA app
No mock, no simulator.
Fit Q-Bot into your existing pipeline
One HTTP call is all it takes.
Keep control inside your own environment
Q-Bot runs locally, on your network.
Real-world uses
Q-Bot steps in where you need it
Three situations where two-factor authentication stops a test run, and where Q-Bot takes over. Whether your tests target a web, mobile or business application.
E2E tests with 2FA
The whole journey runs, login and approval included, without skipping the 2FA step.
Regression runs and CI/CD
Nightly suites and merge-request runs go all the way through.
Business flows needing mobile approval
Confirming a transaction, signing a document, elevating a session: Q-Bot approves it on the phone.
Compatibility
Works with your tools and your 2FA apps
Q-Bot drives the 2FA apps on an Android smartphone, and is triggered from the test pipeline you already use.
2FA apps
- LuxTrust Mobile
- Microsoft Authenticator
- Google Authenticator
- itsme
- Any Android 2FA app
Testing tools
- Selenium
- Cypress
- Appium
- Playwright
- Robot Framework
- Katalon
- TestComplete
- Jenkins CI
- GitLab CI
- REST API
Your tool is not on the list? If it can send an HTTP call, it can trigger Q-Bot.
What makes Q-Bot dependable
-
Made in LuxembourgDesigned and built by Q-Leap.
- 100 % local supportThe team that built it is the team that answers.
- By testers, for testersSoftware testing has been our trade since 2012.