Test Organization Conventions

Apply these rules when writing any new test, structuring test.step calls, naming tests, classifying failures, or splitting oversized test files.

Test Naming Format

Every test name starts with a ticket key followed by a colon and a description:

test('PREFIX-12345: Search users by email', ...);

// Multiple scenarios for one ticket:
test('PREFIX-12345 Scenario 1: Add a user', ...);
test('PREFIX-12345 Scenario 2: Edit a user', ...);
test('PREFIX-12345 Scenario 3: Delete a user', ...);

The PREFIX matches the project's ticket system (configured via the plugin's userConfig.ticketPrefix). Examples: DEVQA-12345, JIRA-12345, LIN-12345, GH-12345.