What: Three test files each begin their only test method with if (! Features::hasApiFeatures()) { $this->markTestSkipped(...); }. Since Jetstream's Features::api() is commented out/disabled, hasApiFeatures() always returns false, so all three tests unconditionally skip on every run.
Where:
Why it matters: php artisan test reports these as "skipped," not failing, so this has gone unnoticed — but the net effect is zero executed test coverage for API token creation, deletion, or permission updates, despite three files that look like they cover exactly that. This is distinct from #93 itself (which is about the disabled feature breaking the documented REST API's ability to issue tokens) — this issue is the specific, silent test-coverage blind spot that decision creates in CI.
Suggested fix: Once #93 is resolved (API features enabled), these tests will start running for real. Until then, make the skip visible — e.g. a CI summary step that fails/warns if skipped-test count exceeds a threshold, or a README/test-suite note flagging that this coverage is currently dark — so a future regression in these tests can't hide behind a silent skip.
What: Three test files each begin their only test method with
if (! Features::hasApiFeatures()) { $this->markTestSkipped(...); }. Since Jetstream'sFeatures::api()is commented out/disabled,hasApiFeatures()always returns false, so all three tests unconditionally skip on every run.Where:
config/jetstream.php:63—// Features::api(),(commented out — tracked separately as Jetstream's Features::api() is disabled, so the documented REST API has no way to issue tokens #93)tests/Feature/CreateApiTokenTest.phptests/Feature/DeleteApiTokenTest.phptests/Feature/ApiTokenPermissionsTest.phpWhy it matters:
php artisan testreports these as "skipped," not failing, so this has gone unnoticed — but the net effect is zero executed test coverage for API token creation, deletion, or permission updates, despite three files that look like they cover exactly that. This is distinct from #93 itself (which is about the disabled feature breaking the documented REST API's ability to issue tokens) — this issue is the specific, silent test-coverage blind spot that decision creates in CI.Suggested fix: Once #93 is resolved (API features enabled), these tests will start running for real. Until then, make the skip visible — e.g. a CI summary step that fails/warns if skipped-test count exceeds a threshold, or a README/test-suite note flagging that this coverage is currently dark — so a future regression in these tests can't hide behind a silent skip.