Add integration, unit testing CI pipelines

[anhthii]

Add CI/CD Pipeline with Unit & Integration Tests

Overview

This PR adds comprehensive testing infrastructure with CI/CD pipelines for the MPCIUM project.

Key Changes

🔧 CI/CD Pipeline

• E2E Tests: Sequential execution (Key Generation → Signing → Resharing)

🧪 Testing Infrastructure

• Unit Tests: Fast component testing with coverage reporting
• Integration Tests: Full MPC workflow testing with Docker infrastructure
• Enhanced Reliability: Robust cleanup procedures and error handling
• Comprehensive Documentation: Testing guide added to README

📁 Files Modified

• .github/workflows/e2e-tests.yml - E2E integration pipeline
• e2e/base_test.go, e2e/reshare_test.go - Improved timeouts and cleanup
• e2e/Makefile - Fixed clean command with -f flag
• README.md - Added testing documentation

Testing Commands

# Unit tests
make test
make test-coverage

# Integration tests
make e2e-test
cd e2e && go test -v -run TestKeyGeneration

Benefits

• Resource Efficiency: E2E tests only on master branch
• Improved Reliability: Better timeout handling for CI environments
• Better Debugging: Comprehensive logging and failure artifacts
• Quality Assurance: Automated testing before production deployment

This establishes a solid foundation for reliable testing infrastructure supporting the project's growth.

[gitguardian]

⚠️ GitGuardian has uncovered 2 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
18287559	Triggered	Generic Password	3659fb9	pkg/config/config_test.go	View secret
18287560	Triggered	Username Password	3659fb9	pkg/config/config_test.go	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}

[github-advanced-security]

This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation.