Add comprehensive E2E tests for unshielded balances and DUST/cNIGHT features

[roman98Z]

Add Comprehensive E2E Tests for Unshielded Balances and DUST/cNIGHT Features

Overview

This Pull Request implements comprehensive end-to-end tests for two critical features in the Midnight Indexer ecosystem, addressing the following GitHub issues:

• Add e2e tests for contract unshielded balances (High Priority)
• Plan and implement tests for DUST/cNIGHT features once integration is available (High Priority)

Changes Summary

1. Unshielded Balances E2E Testing

Added a new test function test_unshielded_balances_e2e() that validates the complete lifecycle of unshielded balance management for contract actions. This test ensures data consistency and correctness across the entire indexer stack.

Key validations:

• Contract actions have unshielded balances correctly populated from blockchain data
• Balance data consistency between GraphQL queries and WebSocket subscriptions
• Token types and amounts are valid and properly formatted
• ContractDeploy actions have empty balances as per specification
• Proper handling of contracts with zero balances

Test coverage:

• Query-subscription consistency checks
• Token type validation (hex-encoded format)
• Amount parsing and validation (u128 format)
• Edge case handling (empty balances, deploy vs call actions)

2. Enhanced DUST Generation Status Testing

Extended the existing test_dust_generation_status_query() function with comprehensive validation scenarios for DUST/cNIGHT functionality.

New test scenarios:

• Empty reward address list handling
• Unregistered Cardano stake addresses validation
• Duplicate address handling
• Single address queries
• Numeric field validation (generation_rate, current_capacity, night_balance)

Improvements:

• Better logging and test output for debugging
• Validation of all numeric fields as proper u128 values
• Descriptive assertion messages for easier troubleshooting

3. Improved DUST Ledger Events Subscription

Enhanced test_dust_ledger_events_subscription() with additional validation and better error handling.

Enhancements:

• Logging for test visibility and debugging
• Graceful handling when no DUST events are present
• Structural validation of event data
• Count verification for expected events

Technical Details

Code Quality:

• Follows existing code patterns and conventions in the repository
• Uses proper Rust error handling with anyhow::Context
• Comprehensive assertions with descriptive error messages
• No breaking changes to existing functionality
• Compiles cleanly with cargo check (no warnings or errors)

Testing Approach:

• Integration with existing E2E test framework
• Uses GraphQL queries and subscriptions via indexer API
• Validates data consistency across multiple API endpoints
• Tests both success and edge case scenarios

Files Modified

• indexer-tests/src/e2e.rs: Added ~200 lines of new test code

Testing

The code has been validated with:

cargo check --package indexer-tests

Result: ✅ Compiles successfully with no warnings or errors

Impact

This PR significantly improves test coverage for:

1. Unshielded balance management - Critical for contract state tracking
2. DUST generation mechanics - Essential for the Midnight privacy features
3. Data consistency - Ensures reliability across query and subscription APIs

Next Steps

After this PR is merged, the test suite will:

• Automatically validate unshielded balance correctness in CI/CD
• Catch regressions in DUST generation status calculations
• Ensure API consistency between queries and subscriptions

Related Documentation

• Midnight Indexer API Documentation
• DUST Specification
• Contract Balance Storage

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

---

Manus AI seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}