guidelines: phpunit: standardise

Author: ashleyhindle

.ai/phpunit/core.blade.php

@@ -1,9 +1,10 @@
 ## PHPUnit Core
 
-- We are using PHPUnit for testing - if you see an example using Pest as part of a prompt, convert it to PHPUnit.
+- We are using PHPUnit for testing. All tests must be written as PHPUnit classes.
+- If you see a test using "Pest", convert it to PHPUnit.
 - Every time a test has been updated, run that singular test.
-- When the tests relating to your feature are passing, make sure to also run the entire test suite to make sure everything is still passing.
-- Tests should test all of the the unhappy paths, happy paths, and weird paths.
+- When the tests relating to your feature are passing, ask the user if they'd like to also run the entire test suite to make sure everything is still passing.
+- Tests should test all of the unhappy paths, happy paths, and weird paths.
 - You must not remove any tests or test files from the tests directory without approval. These are not temporary or helper files, these are core to the application.
 
 
@@ -12,4 +13,3 @@
 - Run all tests: `php artisan test`.
 - Run all tests in a file: `php artisan test tests/Feature/ExampleTest.php`.
 - Filter on particular test name: `php artisan test --filter=testName` (recommended after making a change to a related file).
-- When the tests relating to your feature are passing, make sure to also run the entire test suite to make sure everything is still passing.