What is Naite?

Learn about Naite, Sonamu’s test logging and debugging system.

Naite Overview

Test Logging

Record logs during executionSystematic tracking

Query System

Wildcard patternsChaining queries

Callstack Tracking

Call path tracingDebugging support

VSCode Integration

Real-time visualizationExtension support

Naite is Sonamu’s test logging system. It systematically records data generated during test execution and allows you to query this data to help with test debugging. Just as tree rings record the growth process, Naite records the entire process of test execution. You can trace what data flowed at each step and which functions were called, in chronological order.

Why Do You Need Naite?

Limitations of Conventional Debugging

When writing tests, you often encounter situations like these:

Confusion with console.log

When multiple tests run simultaneously, console.log outputs get mixed up. It’s difficult to determine which log came from which test.

test("create user", async () => {
  console.log("Creating user..."); // Mixed with other test logs
  const user = await createUser();
  console.log("User created:", user);
});

test("create post", async () => {
  console.log("Creating post..."); // Mixed with the above test output
  const post = await createPost();
  console.log("Post created:", post);
});

Console output:

Creating user...
Creating post...
User created: { id: 1 }
Post created: { id: 1 }

It’s hard to tell which completed first as the order is mixed up.

Difficulty with Filtering

When you want to see only logs from a specific module or function, filtering is impossible with console.log. You have to look at all logs.

// Want to see only Syncer's behavior but...
test("generate all entities", async () => {
  await syncer.generateAll(); // Dozens of console.logs internally
  // No way to see only Syncer-related logs
});

Unknown Call Path

It’s difficult to trace where a specific log was output from and which functions it went through.

// Don't know where this log came from
console.log("Processing data...");

// Called in order A → B → C → D but
// Can't trace without callstack information

Mixed with Test Output

Vitest’s test result output and console.log get mixed, reducing readability.

✓ test 1 (123ms)
Debug: something...
✓ test 2 (98ms)
Debug: another thing...
✗ test 3 (45ms)

Naite’s Solution

Naite systematically solves these problems:

Key-based Management

Assigns unique keys to each log for systematic management. You can clearly distinguish modules and functions like user:create, syncer:render.

Wildcard Filtering

You can query only user-related logs with user:* or all create logs with *:create. Find the information you want quickly.

Automatic Callstack Tracking

Automatically collects the callstack for each log recording. You can clearly understand the function call path.

Test Isolation

Each test has an independent log store. Logs never get mixed with other tests.

VSCode Integration

Visualize logs in real-time with VSCode Extension. View them cleanly, separated from test output.

Query System

Easily find logs with complex conditions using chaining queries. Combine fromFile(), fromFunction(), where() and more.

Basic Concepts

1. Naite.t() - Recording Logs

Naite.t() is a function that records data during test execution. The first argument is the key, and the second argument is the value to record.

import { Naite } from "sonamu";

// User creation start
Naite.t("user:create:start", { username: "john" });

const user = await createUser({ username: "john" });

// User creation complete
Naite.t("user:create:done", { userId: user.id });

Key Naming Rules:

Use colons (:) to separate hierarchies
Recommended format: module:function:action
Examples: user:create:start, syncer:render:template, payment:charge:done

Benefits:

Queryable with wildcard patterns (user:*, *:create)
Group and manage by module
Improved readability with intuitive structure

2. Naite.get() - Querying Logs

Naite.get() is a function that queries recorded logs. You can search by key or wildcard pattern.

// Query by exact key
const logs = Naite.get("user:create:start").result();
// [{ username: "john" }]

// Query with wildcard pattern
const allUserLogs = Naite.get("user:*").result();
// Queries both user:create:start and user:create:done

// Only the first log
const firstLog = Naite.get("user:create:start").first();
// { username: "john" }

Query Chaining: You can chain multiple conditions for complex searches:

Naite.get("user:*")
  .fromFile("user.model.test.ts")     // Only from specific file
  .fromFunction("createUser")         // Only from specific function
  .where("data.username", "=", "john") // Only specific value
  .result();

3. NaiteStore - Log Storage

Each test has an independent NaiteStore. This is of type Map<string, NaiteTrace[]>, storing logs as arrays based on keys.

NaiteStore Structure

type NaiteStore = Map<string, NaiteTrace[]>;

interface NaiteTrace {
  key: string;        // "user:create:start"
  data: any;          // { username: "john" }
  stack: StackFrame[]; // Callstack information
  at: Date;           // Recording time
}

interface StackFrame {
  functionName: string | null;  // "createUser"
  filePath: string;              // "/Users/.../user.model.ts"
  lineNumber: number;            // 123
}

Example:

// New Store created when test() runs
const store = new Map();

// Added on each Naite.t() call
Naite.t("user:create:start", { username: "john" });
// store.set("user:create:start", [{ key: "user:create:start", data: { username: "john" }, ... }])

Naite.t("user:create:start", { username: "jane" });
// Added to the same key
// store.set("user:create:start", [
//   { key: "user:create:start", data: { username: "john" }, ... },
//   { key: "user:create:start", data: { username: "jane" }, ... }
// ])

Test Isolation:

test("test 1", async () => {
  Naite.t("key", "value1");
  const data = Naite.get("key").first();
  expect(data).toBe("value1");
});

test("test 2", async () => {
  // Previous test's logs are not present
  const data = Naite.get("key").first();
  expect(data).toBeUndefined();
});

Each test has an independent Store so they don’t affect each other.

4. Automatic Callstack Tracking

Naite automatically collects the callstack at the time of Naite.t() call. This allows you to understand where the log was recorded and which function call path was taken.

Single Call
Function Chain
Deep Call

test("create user", async () => {
  Naite.t("test:log", "value");
  // Callstack: [test → runWithMockContext]
});

async function createUser() {
  Naite.t("user:create", { ... });
  // Callstack: [createUser → test → runWithMockContext]
}

test("create user", async () => {
  await createUser();
});

async function save() {
  Naite.t("db:save", { ... });
  // Callstack: [save → validate → create → test → runWithMockContext]
}

async function validate() {
  await save();
}

async function create() {
  await validate();
}

test("create", async () => {
  await create();
});

Usage:

Filter logs recorded in a specific function with fromFunction("createUser")
Click on callstack in VSCode Extension → navigate directly to code location
Debug complex call chains

Practical Examples

Basic Usage - Flow Tracking

The most basic usage is recording each step of the test flow.

test("post creation flow", async () => {
  const postModel = new PostModel();

  // 1. Record input data
  Naite.t("post:create:input", {
    title: "Hello World",
    content: "This is content",
    author_id: 1,
  });

  // 2. Create post
  const { post } = await postModel.create({
    title: "Hello World",
    content: "This is content",
    author_id: 1,
  });

  // 3. Record result
  Naite.t("post:create:output", {
    postId: post.id,
    createdAt: post.created_at,
  });

  // 4. Verify entire flow
  const logs = Naite.get("post:create:*").result();
  expect(logs).toHaveLength(2);
  expect(logs[0].title).toBe("Hello World");
  expect(logs[1].postId).toBeGreaterThan(0);
});

Input/Output Pattern: Using :input and :output suffixes helps clearly distinguish function inputs and outputs. This is useful for tracking data transformation processes.

Intermediate Usage - Conditional Tracking

Track business logic branches.

test("order payment processing", async () => {
  const order = await getOrder(123);

  Naite.t("payment:process:start", {
    orderId: order.id,
    amount: order.amount,
    paymentMethod: order.payment_method,
  });

  if (order.payment_method === "card") {
    Naite.t("payment:card:charge", { cardNumber: "****1234" });
    await chargeCard(order);
    Naite.t("payment:card:success", { transactionId: "tx_123" });
  } else if (order.payment_method === "bank") {
    Naite.t("payment:bank:transfer", { bankCode: "001" });
    await transferBank(order);
    Naite.t("payment:bank:success", { transferId: "tf_456" });
  }

  Naite.t("payment:process:done", { orderId: order.id });

  // Verify card payment was executed
  const cardLogs = Naite.get("payment:card:*").result();
  expect(cardLogs.length).toBeGreaterThan(0);
});

Advanced Usage - Error Tracking

Record detailed information when errors occur.

test("invalid input handling", async () => {
  try {
    Naite.t("user:create:input", { username: "" }); // Empty value

    await userModel.create({
      username: "",
      email: "test@test.com",
    });

    throw new Error("Should have failed");
  } catch (error) {
    Naite.t("user:create:error", {
      errorType: error.constructor.name,
      errorMessage: error.message,
      validationErrors: error.details,
    });

    // Check error log
    const errorLog = Naite.get("user:create:error").first();
    expect(errorLog.errorType).toBe("ValidationError");
    expect(errorLog.errorMessage).toContain("username");
  }
});

Value of Error Tracking: When an error occurs, you can clearly see what input values caused it and at which step it failed. Combined with VSCode Extension’s callstack feature, you can pinpoint the exact error location.

How It Works

1. Log Recording Process

Environment Check

Checks if NODE_ENV === "test". Immediately terminates if not in test environment.

Context Check

Gets the currently running Context with Sonamu.getContext(). Ignores if no Context exists.

Callstack Collection

Collects the current callstack with new Error().stack and parses it.

Trace Creation

Creates a NaiteTrace object containing key, value, callstack, and time.

Store Save

Adds to the array with naiteStore.set(key, [...existing, trace]).

2. Log Query Process

3. VSCode Extension Transmission

Importance of Serialization: All values are serialized to JSON for transmission to VSCode Extension. If you pass functions or circular reference objects to Naite.t(), a warning is displayed, but it accepts any type for ease of use.

Key Features

1. Test-Only Design

Naite is designed to only work in test environments. Even if Naite.t() exists in production code, there’s no performance impact.

if (process.env.NODE_ENV !== "test") {
  return; // Immediate return, no cost
}

2. Complete Test Isolation

Each test has an independent NaiteStore. A new Store is created each time in getMockContext() in bootstrap.ts.

function getMockContext(): Context {
  return {
    naiteStore: Naite.createStore(), // Create new Map
    // ...
  };
}

3. Any Type Allowed

Naite.t(value: any) accepts any type. Ease of use was prioritized over TypeScript type safety.

// All types allowed
Naite.t("key", "string");
Naite.t("key", 123);
Naite.t("key", { nested: { object: true } });
Naite.t("key", [1, 2, 3]);

However, values that cannot be serialized will show a warning when transmitted to the Extension.

4. Automatic Serialization

getAllTraces() returns all values serialized to JSON. This is for inter-process communication through Vitest’s task.meta.

return traces.map((trace) => ({
  key: trace.key,
  value: JSON.parse(JSON.stringify(trace.data)), // Force serialization
  filePath: trace.stack[0]?.filePath ?? "",
  lineNumber: trace.stack[0]?.lineNumber ?? 0,
  at: trace.at.toISOString(),
}));

5. Wildcard Pattern Matching

Supports simple but powerful pattern matching:

user:*: prefix matching (any length)
*:create: suffix matching (same length)
user:*:done: middle wildcard (same length)

Uses intuitive patterns instead of complex regular expressions.

Cautions

Cautions when using Naite:

Test environment only: Only works when NODE_ENV === "test". Automatically disabled in production.
Context required: Sonamu.getContext() must exist. Only use within bootstrap’s runWithMockContext().
Avoid excessive logging: Calling Naite.t() inside loops can create thousands of traces, degrading performance.
Key naming convention: The module:function:action format is recommended. Consistent rules make finding things easier later.
Serializable values recommended: Values must be JSON serializable to transmit to VSCode Extension. Avoid functions and circular references.

Next Steps

Recording Logs

Learn detailed usage and best practices for Naite.t().

Querying Logs

Learn about Naite.get() and the chaining query system.

Naite Viewer

Learn how to visualize logs in real-time with VSCode Extension.

Debugging Tests

Learn how to track complex bugs with callstack tracing.

​Naite Overview

Test Logging

Query System

Callstack Tracking

VSCode Integration

​What is Naite?

​Why Do You Need Naite?

​Limitations of Conventional Debugging

​Naite’s Solution

Key-based Management

Wildcard Filtering

Automatic Callstack Tracking

Test Isolation

VSCode Integration

Query System

​Basic Concepts

​1. Naite.t() - Recording Logs

​2. Naite.get() - Querying Logs

​3. NaiteStore - Log Storage

​4. Automatic Callstack Tracking

​Practical Examples

​Basic Usage - Flow Tracking

​Intermediate Usage - Conditional Tracking

​Advanced Usage - Error Tracking

​How It Works

​1. Log Recording Process

​2. Log Query Process

​3. VSCode Extension Transmission

​Key Features

​Cautions

​Next Steps

Recording Logs

Querying Logs

Naite Viewer

Debugging Tests

Naite Overview

What is Naite?

Why Do You Need Naite?

Limitations of Conventional Debugging

Naite’s Solution

Basic Concepts

1. Naite.t() - Recording Logs

2. Naite.get() - Querying Logs

3. NaiteStore - Log Storage

4. Automatic Callstack Tracking

Practical Examples

Basic Usage - Flow Tracking

Intermediate Usage - Conditional Tracking

Advanced Usage - Error Tracking

How It Works

1. Log Recording Process

2. Log Query Process

3. VSCode Extension Transmission

Key Features

Cautions

Next Steps