Testing

Testing Skill

When to use

• Writing unit or integration tests (Go or frontend)
• Writing E2E/API integration tests in test/ folder with BDD stage patterns
• Applying TDD: failing test first, then implementation, then refactor
• Reproducing a bug with a test before fixing it
• Creating or updating bug reports when not fixing immediately
• Improving or verifying test coverage

Test Structure Pattern

Critical Rule: Main test functions must contain subtests.

Go Tests

• Main test functions (TestXxx) MUST contain one or more subtests using t.Run
• Each test case should be a subtest within the main test function
• Group related scenarios as subtests within the same main test function
• Use separate main test functions for different behaviors or distinct test groups

// ✅ GOOD: Main function contains subtests
func TestNewEmail_WithInvalidInput_ReturnsError(t *testing.T) {
    t.Run("returns error for invalid email format", func(t *testing.T) {
        // test case
    })
    t.Run("returns error for empty string", func(t *testing.T) {
        // test case
    })
}

Frontend Tests

• Main test suites should use describe blocks to organize related test cases
• Each test or it block should test one specific behavior
• Group related test cases within the same describe block

// ✅ GOOD: Main describe block contains multiple test cases
describe('LoginPage', () => {
  test('user can submit login form', async () => { /* ... */ });
  test('displays error when email is invalid', async () => { /* ... */ });
});

References

Converted and distributed by TomeVault — claim your Tome and manage your conversions.