Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/Octopodo/kt-testing-suite-core/llms.txt

Use this file to discover all available pages before exploring further.

KT Testing Suite Core brings familiar testing patterns to the world of Adobe ExtendScript. Write describe/it/expect tests in TypeScript, build them with the KT toolchain, and run them directly inside any Adobe host application via the ExtendScript Debugger.

Introduction

Learn what KT Testing Suite Core is, how it fits into the Adobe ExtendScript ecosystem, and when to use it.

Quickstart

Install the package, write your first test, and run it inside an Adobe app in under five minutes.

Matchers

Browse 30+ built-in matchers for equality, type checks, numeric comparisons, collections, and Adobe IO types.

API Reference

Full TypeScript signatures for every exported function, class, and interface.

What’s inside

Lifecycle Hooks

beforeEach, afterEach, beforeAll, and afterAll with correct nested suite execution order.

Custom Matchers

Extend expect with your own domain-specific matchers using extendMatchers().

Reporters

Built-in ConsoleReporter and JSONReporter for human-readable output and VS Code extension integration.

Adobe Type Helpers

asAdobeType<T>() and isAdobeType() for type-safe assertions on After Effects, Premiere, and Illustrator objects.

Get started in three steps

1

Install

Add the package to your Adobe extension project.
npm install kt-testing-suite-core
2

Write a test

Create a test file using the familiar describe/it/expect API.
src/tests/my-suite.test.ts
import { describe, it, expect } from "kt-testing-suite-core";

describe("My Suite", () => {
  it("adds numbers correctly", () => {
    expect(1 + 1).toBe(2);
  });
});
3

Build and run

Build the test bundle and run it in Adobe via the ExtendScript Debugger.
npm run build-tests
Then open the ExtendScript Debugger in VS Code and point it at dist.test/index.test.js.
KT Testing Suite Core targets the ExtendScript engine used inside Adobe Creative Cloud apps. It does not run in a standard Node.js environment — tests must be executed inside an Adobe host application.

Build docs developers (and LLMs) love