feat(tests): Add E2E test data creator script for comprehensive testing

[Abhi1992002]

Changes

• Introduced a new script to generate test data for end-to-end (E2E) tests using API functions, ensuring compatibility with future model changes.
• The script creates test users, agent blocks, graphs, profiles, library agents, presets, API keys, and store submissions.
• Utilizes external services for image and video URLs, and includes error handling for data creation processes.
• Provides a summary of created data upon completion, enhancing the testing framework for the AutoGPT platform.

Checklist 📋

For code changes:

• I have clearly listed my changes in the PR description
• I have made a test plan
• I have tested my changes according to the test plan:
  • Test scripts are working perfectly and not breaking anything. Data is also correctly visible in the database.

[netlify]

❌ Deploy Preview for auto-gpt-docs-dev failed.

Name	Link
🔨 Latest commit	a419f21
🔍 Latest deploy log	https://app.netlify.com/projects/auto-gpt-docs-dev/deploys/68773602ba32d00008163555

[netlify]

❌ Deploy Preview for auto-gpt-docs failed.

Name	Link
🔨 Latest commit	a419f21
🔍 Latest deploy log	https://app.netlify.com/projects/auto-gpt-docs/deploys/687736029c65030008056183

[qodo-merge-pro]

You are nearing your monthly Qodo Merge usage quota. For more information, please visit here.

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 4 🔵🔵🔵🔵⚪

🧪 No relevant tests

🔒 Security concerns Credential exposure: The script contains hardcoded test passwords ("testpassword123") and creates API keys with real permissions (EXECUTE_GRAPH, READ_GRAPH). While intended for testing, this could pose security risks if the script is run in production environments or if test data persists beyond testing phases. Additionally, the script bypasses normal authentication flows by directly creating users in Supabase, which could be exploited if not properly secured.

⚡ Recommended focus areas for review Security Risk Hardcoded test password and potential credential exposure in test data creation. The script uses a fixed password for all test users and may create API keys with real permissions. password = "testpassword123" # Standard test password name = faker.name() Error Handling Inconsistent error handling patterns throughout the script. Some methods continue on errors while others may fail silently, potentially leaving the database in an inconsistent state. except Exception as supabase_error: print(f"Supabase user creation failed for {email}, using fallback: {supabase_error}") # Fall back to direct database creation Resource Management Missing proper cleanup mechanisms for created test data and potential database connection leaks if errors occur during execution. try: creator = TestDataCreator() await creator.create_all_test_data() finally: # Disconnect from database await prisma.disconnect()

[deepsource-io]

Here's the code health analysis summary for commits fde3533..a419f21. View details on DeepSource ↗.

Analysis Summary

Analyzer	Status	Summary	Link
JavaScript	✅ Success		View Check ↗
Python	✅ Success	❗ 11 occurences introduced	View Check ↗

---

💡 If you’re a repository administrator, you can configure the quality gates from the settings.