How to Test the Code in awesome-gpt-image-2: Complete Testing Guide

Run npm test to execute the Node.js built-in test runner against all *.test.js files in api/_lib/, or use node --test --watch api/_lib/*.test.js for continuous feedback during development.

The awesome-gpt-image-2 repository is a Vite-powered React application backed by serverless API endpoints. All server-side logic lives under api/ and is thoroughly tested using Node's native test framework—no external test libraries required. This guide walks you through setting up, running, and extending the test suite.

Test Framework Overview

The project uses Node's built-in test runner (node:test) and the standard assert module. This eliminates dependencies on Jest, Vitest, or Mocha and ensures compatibility with the Node.js LTS version specified in the project.

According to the source code in package.json, the test command is:

{
  "scripts": {
    "test": "node --test api/_lib/*.test.js"
  }
}

This pattern automatically discovers and executes every *.test.js file in api/_lib/, including community.test.js and alipay.test.js.

Setting Up the Test Environment

1. Install Dependencies

Start with a clean install using the project's lockfile:

npm ci

The lockfile at package-lock.json ensures deterministic dependency resolution.

2. Configure Environment Variables

Most tests are pure unit tests without external service dependencies. However, the code references process.env.APP_URL for same-origin validation checks. Create a minimal .env.local file:

APP_URL=https://gpt-image2.canghe.ai

For local testing, any valid URL format suffices—the tests primarily validate string matching logic rather than live endpoints.

3. Verify Installation

Confirm the setup by running the full suite:

npm test

Successful output lists each test case name followed by a final "passed" summary.

What Gets Tested

The test suite covers critical business logic across multiple modules:

Community Module Tests (api/_lib/community.test.js)

This is the most comprehensive test file, validating:

• Order payload construction — Verifies correct object assembly for community orders
• Migration constraints — Checks unique index enforcement and idempotent notification handling
• QR-code processing — Tests media-type detection and size limit enforcement
• Permission logic — Validates admin role checks and same-origin request validation
• Rate limiting — Ensures community action throttling works as designed

Alipay Module Tests (api/_lib/alipay.test.js)

Located in api/_lib/alipay.test.js, this suite covers:

• Amount parsing — Correct handling of fractional CNY values
• Notification sanitization — Input cleaning for webhook payloads
• Signature verification — Cryptographic validation of Alipay callbacks

Running Tests: Methods and Options

Standard Execution

Run the complete suite as defined in package.json:

npm test

Single File Testing

Isolate specific modules during debugging:

node --test api/_lib/community.test.js

Watch Mode for Development

Enable continuous feedback while editing code:

node --test --watch api/_lib/*.test.js

The --watch flag re-runs affected tests on file changes without manual invocation.

Adding New Tests

Extend coverage by creating additional *.test.js files in api/_lib/. The glob pattern in package.json picks them up automatically.

Example: Testing a New Helper Function

Create api/_lib/my-helper.test.js:

import test from 'node:test';
import assert from 'node:assert/strict';
import { formatAmount } from './my-helper.js';

test('formatAmount converts cents to display yuan', () => {
  assert.equal(formatAmount(1000), '10.00');
  assert.equal(formatAmount(50), '0.50');
  assert.equal(formatAmount(0), '0.00');
});

test('formatAmount handles negative values', () => {
  assert.equal(formatAmount(-500), '-5.00');
});

Execute immediately:

npm test

Key Source Files Reference

File	Purpose
package.json	Test script definition and runtime dependencies
api/_lib/community.test.js	Core community logic validation
api/_lib/alipay.test.js	Payment processing verification
api/_lib/community.js	Implementation under test (community features)
api/_lib/alipay.js	Implementation under test (Alipay integration)
supabase/migrations/20260722090000_paid_community.sql	Schema constraints referenced by tests

Summary

• Test command — npm test runs all api/_lib/*.test.js files via Node's built-in runner
• No external test framework — Pure Node.js node:test and assert modules
• Environment requirement — Minimal APP_URL in .env.local for same-origin checks
• Watch mode available — Use node --test --watch for development workflows
• Automatic discovery — New *.test.js files in api/_lib/ are included automatically

Frequently Asked Questions

What testing framework does awesome-gpt-image-2 use?

The repository uses Node.js's native test runner (node:test) introduced in Node.js 18 and stabilized in Node.js 20. This eliminates Jest, Mocha, or Vitest dependencies. Tests import from node:test and node:assert/strict for assertions, as seen in api/_lib/community.test.js and api/_lib/alipay.test.js.

Do I need to set up a database to run the tests?

No. The tests are pure unit tests that mock or avoid database interactions. They validate logic like payload construction, signature verification, and permission checks without requiring a live Supabase instance. Only a placeholder APP_URL environment variable is needed.

How do I run a single test file instead of the full suite?

Use Node's test runner directly with the specific file path:

node --test api/_lib/alipay.test.js

This bypasses the package.json glob pattern and executes only the specified file, useful for rapid iteration on specific modules.

Can I use watch mode for automatic test re-runs?

Yes. Node's test runner supports native watch mode:

node --test --watch api/_lib/*.test.js

This monitors all test files and re-executes when changes are detected, providing continuous feedback without manual test invocation.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}