Do I need to know Selenium or Playwright?
No. QAptain abstracts the underlying tooling behind
natural-language job descriptions.
You focus on what should happen — QAptain handles the implementation.
Can I reuse job descriptions?
Yes. Restarting a job reuses the
same description and configuration,
making it easy to iterate or retry after small adjustments.
Are SaaS and Licensed features different?
No. Both deployment modes provide the
same features, UI, and workflows.
Only the hosting model and initial setup differ.
Can I edit a job while it’s running?
No. Once a job starts, its configuration and description are locked.
You can modify the job after it completes and then restart it.
What happens if a browser step times out?
The job is marked as failed, and the timeout reason is
shown in the execution details. You can adjust the description and restart the job.
Can QAptain open pull requests automatically?
Yes. When enabled during repository setup, QAptain can push changes to a
feature branch and open a pull request automatically.
How are credentials and tokens handled?
QAptain does not store any passwords.
Provider access tokens (GitHub, GitLab, Gitea) are used
only at runtime and are never stored.
All user passwords are stored only as secure hashes and
cannot be retrieved or viewed in plain text.
What happens if license limits are reached?
New jobs may wait or fail to start, and a
limit-related message is shown in the UI.
Contact your administrator if higher limits are required.