シーズン4 · 10月16日開始 · $3,000 + CLIボーナス $1,000

1週間。1つのループ。すべてのPRで。

7日間で、TestSpriteをGitHub Appでリポジトリに接続して、すべてのプルリクエストが自動でテストされる状態にします。接続した仕組みはそのまま残り、ハッカソンが終わったあともリポジトリは自分自身をテストし続けます。

Discordに参加仕組みを見る過去のプロジェクトを見る
$4,000
賞金総額
7
日間で開発
5
プロジェクト受賞者
Open Source
CLI · Apache 2.0

Countdown

Season 4 opens

Oct 16 · final schedule confirmed in Discord

00Days
00Hours
00Minutes
00Seconds

Prize pool

$4,000 total.

$3,000 for projects, plus a $1,000 bonus for CLI fixes. Separate pools.

Two ways to win

Project awards

Oct 16–22

$3,000 · 5 winners

Best projects with TestSprite wired into the repo, so every pull request gets tested. Scored out of 100 by human judges.

  1. 1st placeGrand Champion$1,500
  2. 2nd placeRunner Up$750
  3. 3rd placeThird Place$450
  4. 4th placeHonorable Mention$150
  5. 5th placeHonorable Mention$150

CLI Improvement Bonus

Oct 16–29

$1,000 · allocated after close

Find something wrong with the open-source CLI and fix it. Open an issue, then open a PR that closes it. Entirely on GitHub, no forms.

$50+per merged PR
  • Scaled to substance — a $50 floor, more for work that carries more weight, up to three eligible PRs per person.
  • Merged and judged a genuine improvement are two separate bars.
  • One allocation after the window closes, the $1,000 shared out in a single pass.

ループ

4ステップ。1つが繰り返す.

  1. 01

    書く

    Maker

    コーディングエージェントがコードを書きます。Claude Code、Codex、Antigravity など、お使いのツールで。

  2. 02

    テスト

    Checker

    PRを作成すると、チェックが自動で実行されます。誰も実行を覚えておく必要はありません。

  3. 03

    修正

    Maker

    エージェントがPR上の failure bundle を読み、根本原因を修正します。

  4. 04

    再テスト

    Checker

    修正をプッシュすると、チェックが自動で再実行され、PRがグリーンになります。

TestSprite 3.0

実行を覚えておかなければならないループは、いずれ回らなくなります。

Start in 5 minutes

Sign up. Wire it.Forget it.

One account, one live URL, one connection to GitHub — then every pull request gets tested without anyone starting it. Existing projects welcome, no need to start from zero.

  1. 01 · Account

    Create an account

    Free to start. Use the same email you'll submit with. Sign up free →

  2. 02 · Target

    Your live URL

    A deployed app anyone can open. Localhost doesn't count.

  3. 03 · Suite

    Generate the tests

    Agents explore the app and write the suite in the 3.0 portal. The PR check runs the tests you already have, so this comes first.

  4. 04 · Wire it up

    Connect GitHub

    Install the GitHub App on your repo. From then on every PR gets tested on its own.

No repo changes

GitHub App

Install from Settings → GitHub App in the dashboard, pick your repos, done. Nothing is added to your repository. Results come back as a comment on the PR, and three per-repo switches decide the rest: Run on Pull Requests, Include Draft PRs, and Blocking PRs, which turns the result into a status check that holds the merge.

GitHub App docs

提出方法

何を どこに 出すか。

Your proof is a pull request.

Wire TestSprite to your repo, then open a PR. The check runs, TestSprite reports back on the PR, and that thread is the submission. Judges open the link and read the whole story off the PR, then check the suite itself in the portal.

Aim for a PR where the checks pass. A run that caught something first and went green after your fix is the best version of this, and it shows the loop actually works.

Two steps to submit — do both before the deadline

01

In your GitHub repo

Your source, a README with the app and live URL, and at least one PR carrying a TestSprite check.

// コードとその役割

your-project/
├── src/                   // アプリ本体
├── .gitignore             // シークレットはリポジトリに置かない
└── README.md              // 必須: アプリ · ライブURL · スイートの対象範囲
02

Post in Discord

#hackathon-submissions

Your PR link, live URL, and TestSprite account. Demo video optional.

  • A link to a PR with a TestSprite checkA comment or status check from TestSprite on the PR, tests should pass, and the link carries your repo.Required
  • A live public URLYour deployed app, reachable so judges can open it.Required
  • TestSprite email and nameThe account you used, so judges find your suite.Required
  • A demo video linkA short walkthrough — not scored, but judges watch them.Optional

参加要件

チェックリスト。

Three things you hand in, two that have to be true for them to work.

  • アカウント

    必須

    無料のTestSpriteアカウント。提出に使う同じメールアドレスを使ってください。審査員がスイートを見つけられます。

  • 公開リポジトリ

    必須

    ソースは公開リポジトリに。READMEにはアプリ、ライブURL、スイートの対象範囲を記載してください。コミット履歴がアプリの証明になります。

  • PR

    必須

    GitHub Appでリポジトリを接続し、TestSpriteのコメントまたはステータスチェックが付いたPRを1つ以上。テストはパスしている状態が望ましいです。

  • 公開URL

    Prerequisite

    テストはライブアプリに対して実行されます。localhostは不可。早めにデプロイし、期間中は公開したままにしてください。

  • テストスイート

    Prerequisite

    TestSprite 3.0ポータルでライブアプリに対して作成します。PRのチェックはこのスイートを実行するため、先に用意が必要です。

  • デモ動画

    任意

    推奨。Discordにリンクを投稿してください。審査員は必ず視聴します。

審査基準

人間の 審査。

40 pts
プロジェクト品質
作り込み、完成度。ライブアプリは実際にしっかり動きますか?
40 pts
自動で回るテスト
実際に接続されているか、そしてスイートに実行する価値があるか。カバレッジの広さ、アサーションの深さ、シナリオ設計に加えて、すべてのPRでチェックが走りマージを止めるかを見ます。PR、3.0ポータル、コミットから判断します。
20 pts
イノベーション
プロジェクトそのもの、あるいは検証を開発フローに組み込んだ方法の独創性。
∞
エンゲージメントボーナス
Discordの投票、Xでのシェア、ビルドについての長文記事。上限なく加点されます。

Guest judges · Creator Picks

Creator Panel

Five creators are joining Season 4 as guest judges and community supporters. They’ll review the projects and each select a standout project to recognize as their Creator Pick, along with a short quote about what impressed them.

  • Ömer Göçmen
  • Uğur Keşkekçi
  • Astro K Joseph
  • Poyraz
  • Jan Marshal

Creator Picks are separate from the official competition scoring. Prize winners are determined by our judging panel using the official rubric, and Creator Picks do not affect the prize pool.

CLI Improvement Bonus · $1,000 pool · all 14 days · open to everyone

Build it with us.

The whole workflow lives on GitHub. Open an issue, claim it, open a PR that closes it. Entries follow the same rules as any other contribution to the repo, so nothing about this is a special path. Tick one box in the PR template and you’re in.

$npm install -g @testsprite/testsprite-cli
View the repo on GitHubRead the CLI rules →
  1. 01 · Open an issue

    Say what is broken

    Describe the problem and assign the issue to yourself, so everyone can see what's already being worked on. PRs titled docs: skip this step.

    Up to three open claimed issues at a time. A claim with no activity gets a warning at 48 hours and is released at 72, so nobody sits on work they aren't doing.

  2. 02 · Open a PR

    Fix it and tick the box

    Your PR body needs Closes #123 pointing at your issue, the entry checkbox ticked, and your Discord username so we can reach you. Not on Discord? We'll reach you on the PR.

    A bot confirms your entry in a comment. If it looks like an entry but the box is unticked, it asks rather than excludes you. Up to three bonus-eligible PRs per person; contribute as much as you like beyond that.

.github/PULL_REQUEST_TEMPLATE.md
1## Season 4 CLI Improvement Bonus
2 
3- [ ] I'm entering this PR for the Season 4 CLI Improvement Bonus
4 
5 
6 
7---
8 
9## What's broken
10 
11## How you found it
12 
13## Why it matters

The bars

Two bars to clear

A PR has to be merged and judged a genuine improvement. Those are separate bars, so a PR can land and still earn nothing.

  • Fair play
    Losing a duplicate race costs nothing: the first to file keeps that credit and the author of the merged PR keeps theirs. A deadline for allocation is not a quality mark, so a fix that lands just after the window still counts as the work it is. Maintainer-side incidents never count against you.
  • What does not qualify
    These get merged or closed on their own merits, they just don't earn a payout. The list is illustrative, not exhaustive. Bounty farming ends your eligibility for the season.
    • No problem statement
    • Reformatting, whitespace, typo-level edits
    • Behavior change with no tests
    • Comment-only or no-context edits
    • Unexplained dependency bumps
    • One change split across several PRs
    • Spam or bounty farming

    Full CLI rules go live a week before Day 1, so there's time to read the codebase and find something real before the window opens.

The aspects

Four aspects

Each eligible PR is then read against four aspects, with a “meet” and an “exceed” for each. Up to two revision rounds on substance.

  • Impact
    What does it do for a real user?Meetfixes a reproducible bug or adds a capability people asked for.Exceedcloses a class of bug, ships a product-clarity feature, or sets a policy the repo then follows.
  • Problem definition
    Is the problem real?Meetthe problem is real and someone else could reproduce it from what you wrote.Exceeda problem we didn't know we had, or one that reaches further than the fix.
  • Craft
    Does it merge clean?Meettests included, CI green on every platform, diff matches the title.Exceedright on the first review round with no collateral.
  • Discipline
    Does it help others land theirs?Meetproblem stated before code, one concern per PR, credit given to whoever reported it.Exceedreshapes fast on a maintainer's redirect, or files work another contributor picks up and ships.

Feedback · Open all season · every surface

What would you change?

Your feedback shapes what we build next. A week of real builds on codebases we've never seen will surface things we've missed. If something in the 3.0 web portal, the CLI, or the MCP server got in your way, confused you, or you can see a better way to do it, tell us. Specific beats polite: what you tried, what happened, what you expected instead.

Share feedback in Discord

  • Web portal

    Test generation that missed the point, verdicts that were hard to read, anything you had to work around in 3.0.

  • CLI

    Flags, output, docs, install. If it's a bug with a fix, open the issue and PR instead, and it can count toward the bonus.

  • MCP server

    Still supported. If a tool description misled your agent or a call failed silently, tell us — the portal and the CLI come first this season.

Credits for the good stuff. Feedback that changes what we build may earn extra TestSprite credits as a thank-you. It's not a guarantee and it isn't scored, it's how we'd like to say thanks for helping make the product better.

Execution timeline

One week to ship.

  1. Oct 2

    Rules published

    Full rules go live, including the CLI bonus. Two weeks to read the codebase before the window opens.

  2. Oct 16 · Day 1

    Season opens

    Project Track begins: build, generate the suite, and connect the repo so your PRs get tested. The CLI issue and PR window opens the same day and runs the full 14 days.

  3. Oct 22 · Day 7 · 11:59 PM PT

    Project submissions close

    PR link + live URL + account email, posted in Discord by the deadline.

  4. Oct 23 · Day 8

    Judging

    Runs Days 8–12; CLI bonus stays open through Oct 29.

  5. Oct 29 · Day 14 · 11:59 PM PT

    CLI window closes

    PRs must be open and out of draft to be counted.

  6. Oct 30 — Nov 3

    Review & allocation

    Agents screen, a human decides. The $1,000 CLI pool is allocated once, in a single batch.

  7. Nov 6

    Winners

    Announced on X and Discord. Payouts from both pools.

All times Pacific · final schedule confirmed in Discord

参加方法

2 ステップで始めよう.

  1. Step 1

    Xでフォロー

    公式の TestSprite アカウントをXでフォロー。お知らせ、カウントダウン、受賞発表はXで最初に行われます。

    TestSpriteをフォロー
  2. Step 2

    Discordに参加

    ルール、提出、投票、Q&A。シーズン4のルール は #hackathon-info に固定されています。

    Discordに参加

過去のイベント。

ループ全体を作ろう。

1週間で、プルリクエストが自分でテストされる状態を作りましょう。途中でCLIのバグを見つけたら、修正してボーナスを。Xをフォローして、Discordに参加してください。

今すぐDiscordに参加Xで@TestSpriteをフォロー