Frequently asked questions

Quick answers grounded in how QualityKeeper works today. For step-by-step guides, use the sidebar or Welcome.

Getting started

What do I need installed before I can record or run tests?

Use Google Chrome and install the QualityKeeper Recorder extension from the Chrome Web Store. Without the extension, recording from the browser won’t work.

I’m new—where should I start?

  1. Prerequisites
  2. Login or Signup
  3. Projects and Create project

Projects & environments

What is the “QA base URL” when I create a project?

It’s the default URL where tests for that project usually run. You can still use other environments (QA, staging, production) with their own base URLs and variables.

Environment variables vs State Data—what’s the difference?

  • Environment variables are per environment (shared across many test cases in a project). Good for API URLs, secrets, and values that change by deployment. See Environment variables.
  • State Data is per test case—reusable keys for that case only, often referenced in steps with {{state("key")}}. See Test Case Tab - State Data.

Test cases & steps

What are prerequisites and post-requisites?

On the Overview tab, prerequisites run before the main case (for example login). Post-requisites run after—for example logout or clearing cart. Mark a case as usable as a prerequisite with Is Prerequisite.

Why use additional selectors?

If the main selector breaks, QualityKeeper tries fallback selectors in priority order (lower number = higher priority). See Steps.

Do HOVER, FOCUS, and BLUR need a selector?

Yes—like CLICK and TYPE, those actions target an element and need a selector (plus optional fallbacks). See Steps.

Reports & execution

What’s the difference between “positive only” and “all active” when I run?

  • Positive only scopes the picker to positive test cases; you can include or exclude specific ones.
  • All active includes every active test case; leave all selected for a full regression or deselect some for a partial run. See Reports.

Does the default resolution in Settings always apply?

Execution defaults pre-fill run dialogs—you can change resolution on each Run without changing Settings.

Credits & storage

What uses credits?

Runs and other billable actions consume credits (for example 1 credit per execution on runs, as documented on Reports). Exact rules can depend on your plan.

Where do I see my balance and history?

Click Available credits in the header for the summary and Credit history audit. See Credits.

How much storage do I get?

By default plans include 2 GB. You can inspect usage and manage files under Settings → Storage.

Manage & integrations

Who can invite new users?

Organization admins (for example Super admin) can invite users and assign project roles. QA and View only users cannot invite others. See Users & Roles.

Is Slack integration ready for everyone?

Slack linking is beta. Currently only one user per organization/context can enable the connection; see Settings → Profile.

Troubleshooting

Recording or runs fail for no obvious reason—what should I check?

Confirm Chrome and the recorder extension are installed (Prerequisites), your environment URL and variables are correct, and selectors still match the app under test. Use Runs View Details to see which step failed.