Skip to content

nodemavencom/proxy

Folders and files

NameName
Last commit message
Last commit date

Latest commit

Β 

History

36 Commits
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 

Repository files navigation

GitHub Workflows for NodeMaven

This directory contains GitHub Actions workflows that automatically test the NodeMaven Python SDK and allow community members to test with their own API keys.

πŸš€ Available Workflows

1. python-tests.yml - Main Testing Workflow

Triggers:

  • βœ… Automatic: Runs on every push to main/develop branches
  • βœ… Pull Requests: Runs on all PRs to main branch
  • βœ… Manual: Can be triggered manually with custom settings

What it does:

  • πŸ§ͺ Always runs: 31 unit tests (no API key needed)
  • 🌐 Conditionally runs: 17 integration tests (API key required)
  • πŸ“Š Generates: Detailed test reports and summaries
  • πŸ” Tests: Real proxy connections across multiple countries

πŸ”§ How to Use

For Developers (Automatic Testing)

Every time you push code or create a PR, the workflow automatically:

  1. Runs all unit tests
  2. Verifies code quality
  3. Shows results directly in GitHub

For Community Members (Test Your API Key)

Option 1: Manual Workflow Run

  1. Go to Actions tab
  2. Click "NodeMaven Python SDK Tests"
  3. Click "Run workflow"
  4. Fill in your settings:
    • Test Mode: unit-only, integration-basic, or integration-full
    • API Key: Your NodeMaven API key
    • Countries: us,gb,ca (or any combination)
  5. Click "Run workflow"

Option 2: Issue Template

  1. Go to Issues tab
  2. Click "New issue"
  3. Choose "πŸ§ͺ Test with My API Key"
  4. Fill out the form with your requirements
  5. Follow the instructions to run tests

πŸ“Š What Gets Tested

Unit Tests (Always Run - No API Key)

βœ… Proxy username building (12 tests)
βœ… TTL validation (2 tests) 
βœ… Credential validation (4 tests)
βœ… Utility functions (5 tests)
βœ… Client initialization (3 tests)
βœ… Configuration methods (5 tests)

Integration Tests (API Key Required)

βœ… Real API connectivity
βœ… User authentication 
βœ… Proxy connections (HTTP/SOCKS5)
βœ… Multi-country verification
βœ… Session persistence
βœ… Error handling

🌍 Example Test Results

When you run integration tests, you'll see results like:

βœ… API Key Valid - User: your@email.com
βœ… US proxy working: 65.189.94.222
βœ… GB proxy working: 86.22.70.218
βœ… CA proxy working: 50.67.58.150
βœ… Session persistence: Verified

πŸ” Security Features

API Key Protection:

  • βœ… Not logged: API keys never appear in logs
  • βœ… Not stored: Keys are used only during test execution
  • βœ… Temporary: Environment variables cleaned after tests
  • βœ… Masked: GitHub automatically masks sensitive data

Access Control:

  • βœ… Public results: Test results are public (no sensitive data)
  • βœ… Private inputs: API keys remain private
  • βœ… Rate limiting: Prevents abuse with reasonable limits

πŸ“ˆ Benefits for You

As a Repository Owner:

  1. πŸš€ Confidence: Every change is automatically tested
  2. πŸ›‘οΈ Quality: Catch issues before they reach users
  3. πŸ“Š Visibility: Clear status on all PRs and commits
  4. 🀝 Community: Let users test with their own accounts
  5. πŸ“š Documentation: Live examples of how things work

As a Community Member:

  1. βœ… Verification: Test that SDK works with your account
  2. πŸ” Debugging: Identify issues specific to your setup
  3. 🌍 Coverage: Test proxies in your required countries
  4. πŸ“‹ Reports: Get detailed results and troubleshooting info
  5. πŸ’‘ Examples: See real working configurations

🎯 Real-World Benefits

For Development:

  • Faster releases: Automated testing catches issues early
  • Better quality: Comprehensive testing across scenarios
  • User confidence: Community can verify functionality
  • Issue resolution: Clear data when problems occur

For Business:

  • Trust building: Transparent testing builds user confidence
  • Support reduction: Users can self-verify before issues
  • Market reach: Easy for prospects to test functionality
  • Quality assurance: Continuous validation of service quality

πŸš€ Next Steps

  1. Try it out: Run the workflow with your API key
  2. Provide feedback: Let us know how it works for you
  3. Suggest improvements: What other tests would be helpful?
  4. Share results: Help others by sharing your experience

πŸ†˜ Getting Help

  • Documentation: Check the Python SDK README
  • Issues: Create an issue if you find problems
  • Community: Join discussions in existing issues
  • Support: Contact support@nodemaven.com for account issues

This automated testing ensures NodeMaven Python SDK works reliably for everyone! πŸŽ‰

Releases

No releases published

Packages

No packages published

Contributors 2

  •  
  •