About plans

The project is meant to group test runs related to your online application or website. As part of the project, any number of tests can be developed.

Local test runs are tests carried out in your own Google Chrome browser. The number of test runs launched this way is unlimited in all the sales plans.

Cloud test runs are tests launched as part of the IT infrastructure available in BugBug. Launching these test runs is limited, in line with the sales plan.

Parallel tests are test runs launched concurrently; as a result, the total time of taking the test runs is shorter. The number of parallel test runs depends on the sales plan.

A trial makes it possible to fully test BugBug’s capabilities without any costs involved. After 14 days, the account will not be closed; rather, certain functionalities will remain available.

When you try to launch another project, add another user or launch a test run, an error message will pop up with a request to extend your sales plan.

Payments

We accept payment by credit cards through the Stripe.com system.

Any time when the service is provided, you can change your sales plan. When you buy a higher plan, it is activated instantly while the outstanding limit of launches of cloud test runs will be transferred from your current to the new plan.

Any time when the service is provided you can cancel the existing plan (switch to the FREE package). The transfer will take place when the paid plan expires.

If you have more questions, please contact us at info[@]bugbug.io

Technical aspects

At the moment, the service is available exclusively as Software as a Service (SaaS); therefore, it is not possible to install it in the LAN. However, in the future we are planning to launch this service. If you are interested, contact us at info@bugbug.io.

Yes, this is the major BugBug’s benefit. All the test runs created there can be launched in a local Google Chrome browser and verified if the test ran correctly.

Not at the moment. We are planning exports of recorded test runs for late 2021.

Yes, within the organisation, you can invite new users and work on the test runs together.

Yes. We will also provide you with the CLI tool that will help you to easily integrate BugBug with your Continuous Integration system (https://www.npmjs.com/package/@testrevolution/bugbug-cli).

Not at the moment. Right now we support launching test runs in Google Chrome while support in the other browsers has been included into our roadmap.

Yes, the application supports the debugging mode of test runs.

Yes, it is possible to create various types of assertions and to add your own JavaScript code in more extended scenarios.

Yes, it is possible to add a step with any JavaScript code as part of a test run.

Yes, this is possible when you use your own JavaScript code and, for example, a fetch() function.

The data used in the test runs are recorded in our database and stored in the DigitalOcean cloud. Access to the database is provided exclusively as part of the BugBug application infrastructure. We make all the effort to prevent data leaks.

Yes, it is possible to launch many test runs parallel but only in the cloud launch mode. The tests launched in a local browser are always run one after another (in a sequence) due to the isolation of the data between the test runs (excluded shared cookies or local storage).

The mechanism of identifying the elements on the site checks the latest status of site loading, the actual visibility of the expected element and, if a specific element does not animate itself (does not move on the site), if it is not concealed by another element and, first and foremost, if it is available in the DOM structure of the site. As a result, the test runs are highly stable.

Yes, it is. The function of launching cyclical test runs is available in every paid plan.

No. Right now BugBug handles web applications and websites.

Try today!

Power up your workflow with BugBug

Reliable, modern end-to-end software that improves testers and developers' work.

Sign up to our newsletter