Implement Comprehensive Testing for AWS SQS Driver Integration

[saravanasai]

Create a robust testing suite to validate the AWS SQS driver implementation for the GoQueue project. The testing should ensure the SQS driver functions correctly, handles errors appropriately, and integrates properly with the existing middleware, retry, and DLQ functionality.

Requirements

1. Unit Testing
   Create mocks for the AWS SQS service using a mocking library (e.g., go-mock, testify/mock)
   Test all SQS driver methods (Enqueue, Dequeue, Acknowledge, Requeue) with various inputs
   Test error handling for common AWS errors (throttling, permissions, network issues)
   Validate correct message attribute handling and serialization/deserialization
2. Integration Testing
   Create a test that uses LocalStack or actual SQS (with test queues)
   Test the full job lifecycle: enqueue, process, acknowledge
   Verify retry functionality with the SQS driver
   Test visibility timeout handling and message reappearance
   Validate DLQ redirection after max retries
3. Configuration Testing
   Test the SQS config validation logic
   Verify credentials handling (direct credentials, environment variables, IAM roles)
   Test the configuration builder pattern with SQS-specific options
   Validate error handling for invalid configurations
4. Performance Testing
   Create a benchmark comparing SQS vs Redis drivers
   Measure throughput under various concurrency settings
   Test with different batch sizes and payload sizes
   Document performance characteristics and limitations
5. End-to-End Testing
   Create a sample application using the SQS driver
   Test middleware chaining with SQS
   Verify metrics collection works correctly with SQS
   Test graceful shutdown with in-flight SQS messages
   Deliverables
   Unit tests in a drivers/sqs_driver_test.go file
   Integration tests in a test/sqs_integration_test.go file
   Benchmark tests in a benchmark/sqs_benchmark_test.go file
   Sample application demonstrating SQS usage in examples/sqs_example
   Documentation update explaining the testing strategy and results
   Success Criteria
   All tests pass consistently
   Code coverage for SQS driver exceeds 80%
   Documentation clearly explains how to run tests and interpret results
   Performance characteristics are well-documented
   Edge cases (network errors, retries, etc.) are properly handled