marcocosta10000
c299a4ae21
- Add database migrations for market_listings, missions and character cosmetics - Create controllers for marketplace, missions, presence and character customization - Implement admin world dashboard with live platform metrics - Add feature tests for world functionality - Include phase 2 design documents and gap analysis
1.9 KiB
Executable File
1.9 KiB
Executable File
Naming and Structure
File Layout
- Name each test file
{ClassName}Test.php. - Place each test file at the same relative path as the class under test. The class
app/Actions/DeleteTeam.phpgets the testtests/Unit/Actions/DeleteTeamTest.php. - Follow the project's convention for fixture files. If none exists, put fixtures in
tests/Fixtures/and load them by path. - Move large literal values out of the test body and into fixture files.
Test Class and Methods
- Extend the base
TestCaseof the project in each test class. - Give each test method the prefix
test_, or add the#[Test]attribute to the method. Use the convention of the other files in the same directory.
Naming Tests
The name of a test method is a specification. Separate the words with underscores. State the user-visible result and the condition that causes it.
- Name the behavior, and not the method under test. The file name already gives the class.
- Give the exact status code in the name of a test for an API error.
- Do not write
given,when, orthenin the name.
public function test_unauthenticated_request_redirects_to_login(): void { ... }
public function test_returns_401_when_no_token_is_provided(): void { ... }
public function test_valid_payload_creates_record_and_returns_201(): void { ... }
Use a verb that describes a result, such as returns, renders, creates, dispatches, rejects, forbids, falls back, or does not.
Do not write test_store(), test_it_works(), or test_validation(), because none of them gives a result.
Grouping
Write one test class for each class under test. Write a separate test class if one file covers separate actions in a lifecycle, such as StoreOrderControllerTest and UpdateOrderControllerTest.
Use the #[Group] attribute to mark the tests that a run must select or must skip. Do not use a group to give structure to a file, because a class gives the structure.