Skip to main content

FAQ — Early Verify

Which languages and test frameworks are supported?​

JavaScript and TypeScript with Jest. Other frameworks will be added over time.

I don’t see any coverage — why?​

Verify relies on Jest to produce coverage. If Jest isn’t fully configured (or tests can’t run), Verify can’t display coverage. Make sure:

  • Jest is installed and configured (e.g., jest, ts-jest/babel-jest as needed)
  • Tests run successfully in the repo

Why don’t I see functions or coverage when I open a repo?​

That’s expected on the first view. You’ll see a basic tree with testable files only.
Click Refresh Coverage; when processing completes, the tree adds function nodes and coverage numbers for each folder, file, and public function.

What does Verify provide beyond a basic coverage tool?​

It centralizes repository coverage with branch/commit context and lets you drill down to function level—so you can find gaps quickly and prioritize fixes.

How do I start?​

Install the GitHub App, grant access to the repositories you want to track, and open the dashboard to view coverage.

Do I need a secret token?​

Some setups may require credentials. If you need access, Contact Us here

Do I need to configure my CI to use Verify?​

No. Verify uses the Early AI GitHub App to gain access and perform data processing. Install the app, select repositories, and you’re set.

Which CI systems are supported?​

Verify works independently of your CI. You can keep your existing CI as-is; Verify does not require CI changes to provide coverage views and drill-downs.

Can I limit which repos are visible?​

Yes. During app installation you can choose Only select repositories and pick the repos to monitor.