Bot-Powered Continuous QA

Distribute QA tests to our professional software testers using bot commands inside your repo.
Get started How it works
Frequently asked questions
Do testers need access to our code?
No. Testers don’t access your code and you can pick and choose which issues from your issue library that you want to share with testers. You share the starting web URL, and login credentials to access your app (if required).
What type of access do testers require?
Testers only need the web address of your application including the steps to test and login credentials (if required). They perform functional and regression testing using the front end interface of your web application.
Do testers agree to non-disclosure?
Yes. Testers must undertake a rigorous vetting process before accessing clients web applications and tests and must agree to non-disclosure before they start this process. We make a point of not crowdsourcing.
What type of testing is performed?
Our testers perform functional and regression testing and you use bot commands in an issue ticket within your issue library to communicate with testers when you need a test performed, re-tested, or when rejecting a report.
Does Bugdojo access our code?
No. We connect to your repo to give you professional QA resources on-demand as you’re building code, and give you full control over which issues from your library you share for testing. We are only testing your web interface.
Does Bugdojo guarantee quality?
Yes. We provide a quality guarantee every time you run a test and receive a report. If you’re not 100% happy with the report submitted by the tester you can reject it by using a bot command, distribute to another tester.
How long does it take to write a test?
Roughly 60 seconds. You can write tests in plain english and they only have to include some basic tests and expected result. In fact to make it easy, we provide you a template which you can follow each time you distribute a test.
Do you provide videos with the reports?
Yes. When a tester reports a pass or fail they include the steps to reproduce, the actual result, which is also accompanied by a video of the test. This makes it easy to check the result and remediate a bug fix if required.
How do testers access our environment?
Testers only need access to the web address of the test asset which you supply when writing the test case. You can also provide test credentials or VPN credentials. Tester are asked to sign NDA and you choose what to share.
How long does it take to run a test?
It takes 60 minutes to receive the video report back from a tester in the comment stream. Once you receive the result, it will automatically accept after 3 days. If you’re not happy you can reject the report no charge and retest.

Get started

Receive your first 5 tests free
$6.50 per test
Receive detailed test results & videos
Access to experienced & skilled testers
Integration with Github & Bitbucket
Scale testing as needed & cancel anytime
Github
Bitbucket
Gitlab
Over 100 tests a month? Contact us for special pricing offer.

Bot-Powered Continuous QA

Distribute QA tests to our professional software testers using bot commands inside your repo.
Get started How it works