Separate opencode plugin tests from application tests #248

New issue

Closed

opened 2026-05-18 11:05:52 -07:00 by jwilger · 0 comments

jwilger commented

2026-05-18 11:05:52 -07:00

Owner

Context

The tests that cover our opencode plugins currently live under the main application tests directory. Those tests are not testing the auto_review application behavior; they are testing the coding harness/opencode plugin behavior under .opencode/.

Because they are mixed into the application test layout, it is easy to treat them as part of the product test suite instead of as a separate harness/tooling concern.

Desired outcome

Move or recreate the opencode plugin tests so they are co-located with the plugins under .opencode/.
Add a separate, explicit way to run the opencode plugin test suite.
Keep the plugin tests important and visible, but distinguish them from application behavior tests.
Update any relevant docs, just recipes, or developer guidance so contributors know how to run both application tests and opencode harness/plugin tests.

Notes

This is not about reducing coverage. It is about making the boundary clear: application tests should cover the product, while .opencode plugin tests should cover the project coding harness.

## Context The tests that cover our opencode plugins currently live under the main application tests directory. Those tests are not testing the auto_review application behavior; they are testing the coding harness/opencode plugin behavior under `.opencode/`. Because they are mixed into the application test layout, it is easy to treat them as part of the product test suite instead of as a separate harness/tooling concern. ## Desired outcome - Move or recreate the opencode plugin tests so they are co-located with the plugins under `.opencode/`. - Add a separate, explicit way to run the opencode plugin test suite. - Keep the plugin tests important and visible, but distinguish them from application behavior tests. - Update any relevant docs, `just` recipes, or developer guidance so contributors know how to run both application tests and opencode harness/plugin tests. ## Notes This is not about reducing coverage. It is about making the boundary clear: application tests should cover the product, while `.opencode` plugin tests should cover the project coding harness.

jwilger added this to the 1.0 milestone

2026-05-18 11:06:14 -07:00

jwilger added the

bug

label

2026-05-18 11:06:21 -07:00

jwilger referenced this issue from a commit

2026-05-18 11:52:20 -07:00

test(opencode): separate plugin test suite

jwilger referenced this issue from a pull request that will close it,

2026-05-18 11:52:30 -07:00

test(opencode): separate plugin test suite #253