Optimize unit test workflow with selective module testing

[michpohl]

🚀 Overview

This PR implements intelligent test execution that only runs tests for modules that have changes or depend on changed modules, significantly reducing CI execution time while maintaining comprehensive test coverage.

📋 Problem Solved

Currently, the unit test workflow runs > Task :buildlogic:checkKotlinGradlePluginConfigurationErrors SKIPPED

Task :buildlogic:compileKotlin UP-TO-DATE
Task :buildlogic:compileJava NO-SOURCE
Task :buildlogic:pluginDescriptors UP-TO-DATE
Task :buildlogic:processResources UP-TO-DATE
Task :buildlogic:classes UP-TO-DATE
Task :buildlogic:jar UP-TO-DATE

Configure project :

[Incubating] Problems report is available at: file:///Users/mpohl/work/tidal-sdk/tidal-sdk-android/build/reports/problems/problems-report.html

Deprecated Gradle features were used in this build, making it incompatible with Gradle 9.0.

You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.

For more on this, please refer to https://docs.gradle.org/8.14.3/userguide/command_line_interface.html#sec:command_line_warnings in the Gradle documentation.
4 actionable tasks: 4 up-to-date which executes tests for ALL modules regardless of what changed. This leads to:

• Longer CI execution times
• Unnecessary resource usage
• Slower feedback cycles for developers

🎯 Solution

Implemented a smart change detection system that:

🔍 Change Detection

• Analyzes Git diff to identify changed files
• Maps files to their corresponding modules based on directory structure
• Handles edge cases like root-level changes that affect all modules

📊 Dependency Analysis

• Automatically includes dependent modules when a dependency changes
• Example: Changing module will also test , , and
• Ensures comprehensive coverage without missing integration issues

⚡ Smart Execution

• Runs selective tests for focused changes
• Falls back to full test suite for root-level changes (build files, workflows, etc.)
• Provides override option to force run all tests when needed

📁 Files Added

Core Scripts

• **:auth:apps:demo:test :auth:test :bom:test :common:test :eventproducer:apps:demo:test :eventproducer:test :player:apps:demo:test :player:test :tidalapi:apps:demo:test :tidalapi:test ** - Main detection logic with dependency analysis
• �[0;34m🔍 Detecting affected modules...�[0m
  �[0;32m📋 Test tasks to run:�[0m :auth:apps:demo:test :auth:test :bom:test :common:test :eventproducer:apps:demo:test :eventproducer:test :player:apps:demo:test :player:test :tidalapi:apps:demo:test :tidalapi:test
  �[0;34m🧪 Running affected tests...�[0m - Convenience wrapper for easy execution
• **Running tests for detect-affected-modules.sh

�[1;33mTest 1: No changes�[0m
�[0;32m✓ PASS�[0m: Got expected output** - Test suite for validation

• **** - Comprehensive documentation

Workflows

• **** - Example standalone workflow
• **** - Updated existing workflow with selective testing

🧪 Testing

The script has been tested with various scenarios:

🎁 Benefits

⏱️ Performance Improvements

• Faster CI: Only runs necessary tests for focused changes
• Resource Efficiency: Reduces compute usage and costs
• Quick Feedback: Developers get faster test results

🛡️ Reliability

• Comprehensive Coverage: Includes dependent modules automatically
• Safe Fallbacks: Runs all tests for infrastructure changes
• Robust Error Handling: Validates Git state and provides clear error messages

🔧 Developer Experience

• Easy Override: input to force full test run
• Clear Logging: Detailed output showing which modules are being tested
• Flexible Usage: Can be used locally or in CI/CD

📖 Usage Examples

In GitHub Actions

Local Development

�[0;34m🔍 Detecting affected modules...�[0m
�[0;32m📋 Test tasks to run:�[0m :auth:apps:demo:test :auth:test :bom:test :common:test :eventproducer:apps:demo:test :eventproducer:test :player:apps:demo:test :player:test :tidalapi:apps:demo:test :tidalapi:test
�[0;34m🧪 Running affected tests...�[0m
:auth:apps:demo:test :auth:test :bom:test :common:test :eventproducer:apps:demo:test :eventproducer:test :player:apps:demo:test :player:test :tidalapi:apps:demo:test :tidalapi:test

🔄 Module Dependencies

The system understands the project's dependency structure:

🧪 Validation

• ✅ Script works correctly with various change scenarios
• ✅ Dependency analysis includes all affected modules
• ✅ Root-level changes trigger full test suite
• ✅ Error handling for invalid Git states
• ✅ Workflow integration tested and functional

This change will significantly improve CI efficiency while maintaining the same level of test coverage and reliability.