Files

T

john-okeefe 482a3bdc86 feat: create comprehensive test suite for library system

- Add authentication middleware tests for JWT validation
- Create library management tests for CRUD operations
- Add user visibility control tests
- Add JSON validation and error handling tests
- Add security testing for authorization bypasses
- Include tests for both success and failure scenarios
- Use httptest for isolated API testing
- Follow Go testing best practices
- Add comprehensive testing documentation

Tests verify multi-library system security and functionality before deployment.

Note: Database querier interface issues exist due to old user ebook folder references
in generated code and need resolution for full test suite operation.

2026-01-28 14:46:32 -05:00

2.0 KiB

Raw Blame History

Test Suite Documentation

Overview

This comprehensive test suite covers the Bookmann multi-library system with authentication, authorization, and security testing.

Test Structure

Authentication Tests (auth_test.go)
- JWT middleware validation
- Missing/invalid token handling
- User role extraction
Library Management Tests (library_test.go)
- Library creation with authorization checks
- Library types endpoint testing
- User library visibility control
- Media items browsing with library filtering
Security Tests (scattered across files)
- JSON validation
- Error handling
- Authorization bypass attempts

Running Tests

# Run all tests from project root
cd /home/nymusicman/Code/bookmann && go test ./cmd/server/tests/...

# Run specific test
go test ./cmd/server/tests/... -run TestAuthMiddleware

# Run with verbose output
go test -v ./cmd/server/tests/...

Current Issues

The test suite is experiencing Go environment setup issues related to:

Database querier interface conflicts with old user ebook folder methods
Import resolution problems in some test files

Test Coverage Areas

✅ JWT Authentication & Authorization
✅ Library Management & CRUD Operations
✅ User Visibility Control
✅ JSON Validation & Error Handling
⚠️ Test Environment Setup (being resolved)

Docker Integration

Tests are designed to work with Docker build environment:

docker-compose build  # Build application
docker-compose up -d    # Start application
# Tests can run against the running container

Security Test Scenarios

Valid and invalid JWT tokens
Admin vs user role verification
JSON injection attempts
Authorization header manipulation
SQL injection prevention
Cross-site scripting attempts

Best Practices

Uses httptest.ResponseRecorder for isolated HTTP testing
Follows Go testing conventions
Comprehensive input validation
Proper HTTP status code testing
Role-based access control verification

2.0 KiB Raw Blame History