Skip to content

A free open source IT asset/license management system

Update testing guideline for snake_case method names

Marcus Moore18f5e44adce3
diff --git a/.ai/guidelines/snipe-it-testing.md b/.ai/guidelines/snipe-it-testing.md
index 9f41585ea7..bc754bbcb3 100644
--- a/.ai/guidelines/snipe-it-testing.md
+++ b/.ai/guidelines/snipe-it-testing.md
@@ -3,9 +3,10 @@
- Feature tests live in `tests/Feature/`, organized by entity (e.g. `tests/Feature/Assets/AssetsTest.php`). Unit tests live in `tests/Unit/`.
- Feature tests hit the database. The test environment uses `array` drivers for cache, session, and mail.
- Always build test data with model factories. Check for an existing custom state before setting attributes by hand.
-- UI GET routes should have both a "page renders" test and a permission test — follow the naming used by siblings (`testPageRenders`, `testRequiresPermission`).
+- Test methods are named in snake_case: `test_page_renders()`, `test_requires_permission()`. Never camelCase.
+- UI GET routes should have both a `test_page_renders` test and a `test_requires_permission` test.
```bash
php artisan test tests/Feature/Assets/AssetsTest.php # single file
-php artisan test --filter testSomeMethod # single method
+php artisan test --filter test_some_method # single method
```