Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

No CI: 152 smoke tests, rigs and a fuzz harness exist but nothing runs them

オープン
  • 何か問題がありますか？
#414 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
3/5
見積もり時間
1〜2日
初心者へのやさしさ
78/100
issue の種類
機能追加
明瞭さ
明確に書かれている
活発さ
活発
技術スタック
github-actions, php
領域
ci-cd, testing

調査の方向性

Start with homeboy.json and its scripts.lint and scripts.test recipes, then inspect the repository for the absent .github/workflows directory. Add a workflow that invokes those recipes for pull requests and pushes to main, and verify it reports status checks while a failing smoke test prevents a green result. Use tests/smoke-*.php as the suite being exercised.

索引モデルが issue の本文から書いたものです。

説明

Summary

This repository has no CI. There is no .github/workflows directory and no configuration for any other CI system. The only automation running against it is Dependabot's dependency graph updates.

Pull requests therefore report no checks reported, and nothing verifies a change on merge or catches a regression afterwards.

What already exists and is not being run

The repository is well equipped for verification. None of it is wired to anything:

Asset Count / detail
Smoke tests 152 tests/smoke-*.php
Declared recipes homeboy.json → scripts.lint, scripts.test
Rigs rigs/mdi-native, rigs/mdi-primary, rigs/mdi-sqlite
Fuzz harness fuzz/
Benchmarks bench/native-sqlite-differential.workload.json

homeboy.json already declares exactly what a pipeline would need:

"scripts": {
  "lint": ["php -l markdown-database-integration.php && for file in inc/*.php tests/*.php; do php -l \"$file\" || exit 1; done"],
  "test": ["for test_file in tests/smoke-*.php; do php \"$test_file\" || exit 1; done"]
}

So the gap is wiring, not authoring. The full suite runs in seconds locally.

Why this matters more than usual here

MDI is not a peripheral plugin — when MARKDOWN_DB_MODE is primary it is the database. WP_Markdown_Native_WPDB replaces $wpdb and every option, post and table read on the site goes through it.

A silent read-side regression in this component does not surface as a failing feature. It surfaces as data that appears not to exist. #412 is a worked example: an indeterminate option read was reported as "this option is absent", which caused WordPress to regenerate auth_key/auth_salt and permanently destroy every credential encrypted under the previous salt. That happened twice in four days, and was not noticed for three days, because the only symptom was an unrelated remote HTTP 401.

That class of defect is precisely what a test suite catches and a human review does not.

The fix for it (#413) merged — or will merge — with zero automated verification. Its evidence is a local run and a manual mutation check recorded in the PR body. That is not a durable guarantee, and it will not stop the same read path regressing later.

Proposed

Add a workflow that runs the recipes this repository already declares:

  • scripts.lint and scripts.test from homeboy.json on pull requests and on pushes to main.
  • Required status checks on main so a red suite blocks merge.

Worth considering once the basics are green:

  • Run the mdi-native / mdi-primary / mdi-sqlite rigs, since backend parity is the property most likely to drift.
  • Schedule the differential fuzz harness rather than running it per-PR, to keep PR latency low while still exercising it.

152 smoke tests running on every PR is a large improvement over nothing, and needs no new test authoring.

Acceptance

  • A pull request runs lint and the smoke suite and reports a status check.
  • A failing smoke test blocks merge on main.
  • The workflow invokes the recipes declared in homeboy.json rather than duplicating them, so the local command and the CI command cannot drift.

AI assistance disclosure: Claude Sonnet 4.5 via Claude Code noticed this while opening #413 and finding no checks reported, inventoried the existing unused test assets, and drafted this issue at Chris Huber's request.

主要言語
PHP
スター
5
フォーク
1
平均マージ
2時間 37分
マージ済み PR（30日）
80

環境構築

このプロジェクトの環境構築ファイルはまだ確認していません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

Automattic/markdown-database-integration のほかの issue

Automattic/markdown-database-integration の issue をすべて見る

似ている issue

PHP の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。