devdox-ai-locust 0.1.1__tar.gz → 0.1.2__tar.gz

{devdox_ai_locust-0.1.1 → devdox_ai_locust-0.1.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: devdox_ai_locust
-Version: 0.1.1
+Version: 0.1.2
 Summary: AI-powered Locust load test generator from API documentation
 Author-email: Hayat Bourji <hayat.bourgi@montyholding.com>
 Maintainer-email: Hayat Bourji <hayat.bourgi@montyholding.com>

{devdox_ai_locust-0.1.1 → devdox_ai_locust-0.1.2}/pyproject.toml

@@ -5,7 +5,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "devdox_ai_locust"
-version = "0.1.1"
+version = "0.1.2"
 description = "AI-powered Locust load test generator from API documentation"
 readme = "README.md"
 license = {text = "Apache-2.0" }
@@ -101,7 +101,7 @@ exclude = ["tests*"]
 
 
 [tool.setuptools.package-data]
-devdox_ai_locust = ["schemas/*.json", "templates/*.j2", "py.typed"]
+devdox_ai_locust = ["schemas/*.json", "templates/*.j2","prompt/*.j2", "py.typed","*.j2"]
 
 # flake8 configuration (legacy - remove if using ruff)
 [tool.flake8]

{devdox_ai_locust-0.1.1 → devdox_ai_locust-0.1.2}/src/devdox_ai_locust/config.py

@@ -8,7 +8,7 @@ from pydantic_settings import BaseSettings
 class Settings(BaseSettings):
     """Application settings."""
 
-    VERSION: str = "0.1.1"
+    VERSION: str = "0.1.2"
 
     API_KEY: str = ""  # Fallback for backward compatibility
 

devdox_ai_locust-0.1.2/src/devdox_ai_locust/prompt/domain.j2

@@ -0,0 +1,33 @@
+Based on this API analysis, create domain-specific user flows for Locust testing:
+{{domain_analysis}}
+
+API Analysis: Use the analyze_api_domain function output which includes:
+- API Title and Description
+- Total Endpoints count
+- HTTP Methods used
+- Common Path Patterns
+- Main Resources identified
+
+Endpoints Available: Complete Swagger documentation with all endpoint details including:
+{{ endpoints }}
+
+# Limit for token efficiency
+
+Generate a Python file with domain-specific user flow classes that extend the base CustomUserFlow. Focus on realistic business workflows that users would actually perform.
+
+Requirements:
+1. Create 2-3 domain-specific flow classes based on the identified main resources
+2. Use sequential tasks for related API calls and use correlation between them
+3. To check payload and update it if it is not valid using the Swagger schemas
+4. Each flow should represent a complete business process workflow
+5. Include proper error handling and realistic wait times
+6. Use the available endpoints from Swagger documentation in logical sequences
+7. Add meaningful logging and data tracking
+8. Parse Swagger schemas to generate valid request payloads
+9. Implement data correlation (e.g., use created resource IDs in subsequent calls)
+10. Add requirement sent by developer:{{ custom_requirement }}
+
+Always return your code wrapped in <code></code> tags with no explanations outside the tags
+DO NOT TRUNCATE THE CODE. IMPORTANT: Return the SAME code with ONLY formatting fixes. Do not enhance or add anything
+
+Format: <code>your_python_code_here</code>

devdox_ai_locust-0.1.2/src/devdox_ai_locust/prompt/locust.j2

@@ -0,0 +1,22 @@
+Enhance this Locust test file to be more professional and realistic and fix the indentation issues:
+
+ ```python
+ {{ base_content }}
+ ```
+
+ Available Endpoints: {{ endpoints_for_prompt }}
+ API Info: {{ api_info.title }} v {{ api_info.version }}
+
+ Fix ONLY the formatting and indentation issues in this Locust test file. 
+
+  STRICT REQUIREMENTS:
+  - Fix indentation and formatting ONLY
+  - Do NOT add new tasks, methods, or endpoints
+  - Do NOT modify existing task logic
+  - Do NOT add new functionality
+  - Keep the exact same tasks and methods
+  - Only fix Python syntax, imports, and indentation
+
+Always return your code wrapped in <code></code> tags with no explanations outside the tags DO NOT TRUNCATE THE CODE. 
+IMPORTANT: Return the SAME code with ONLY formatting fixes. Do not enhance or add anything
+Format: <code>your_python_code_here</code>:

devdox_ai_locust-0.1.2/src/devdox_ai_locust/prompt/test_data.j2

@@ -0,0 +1,62 @@
+Enhance this test data generator with domain-specific realistic data while preserving ALL existing methods and their signatures:
+
+Current File:
+{{base_content}}
+
+API Schemas Found:
+{{ schemas_info }}
+
+API Endpoints Context:
+[
+{% for ep in endpoints -%}
+    "Path: {{ ep.path }}, Method: {{ ep.method }}, Tags: {{ ep.tags }}"{% if not loop.last %},{% endif %}
+{% endfor -%}
+]
+
+REQUIREMENTS - Enhance by adding NEW functionality while keeping ALL existing methods intact:
+
+1. **Domain-Specific Data Generators**:
+   - Add methods like `generate_affiliate_data()`, `generate_user_credentials()`, `generate_product_data()`
+   - Create realistic data based on API endpoint patterns (affiliate, user, product, etc.)
+   - Add specific payload generators for common API patterns
+
+2. **Realistic ID Generation**:
+   - Add `generate_realistic_id(entity_type: str)` for entity-specific IDs
+   - Create correlated IDs (user_id -> session_id -> transaction_id)
+   - Add methods like `generate_affiliate_id()`, `generate_partner_id()`, etc.
+
+3. **Payload Templates**:
+   - Add `get_payload_template(endpoint_path: str, method: str)`
+   - Create endpoint-specific payload generators
+   - Add `generate_login_payload()`, `generate_registration_payload()`, etc.
+
+4. **Data Relationships & Correlation**:
+   - Add session management: `create_user_session()`, `get_session_data()`
+   - Create data dependency chains (parent-child relationships)
+   - Add `link_related_entities(parent_id, child_type)` for realistic relationships
+
+5. **Smart Caching & Performance**:
+   - Add `cache_generated_data(key, data)` and `get_cached_data(key)`
+   - Create reusable entity pools for better performance
+   - Add `get_or_create_entity(entity_type, **kwargs)`
+
+6. **Specialized Pattern Generators**:
+   - Add `generate_api_key_data()`, `generate_webhook_payload()`
+   - Create `generate_pagination_data()`, `generate_filter_data()`
+   - Add `generate_error_scenarios()` for negative testing
+
+7. **Validation & Constraints**:
+   - Add `validate_generated_data(data, schema)`
+   - Create constraint-aware generation
+   - Add business rule validation
+
+CRITICAL CONSTRAINTS:
+- MUST preserve ALL existing method signatures exactly as they are
+- MUST keep all existing functionality working
+- MUST maintain backward compatibility
+- ADD new methods, don't modify existing ones
+- Keep the global `test_data_generator` instance
+
+Focus on making the data generation smarter and more realistic while ensuring all existing code that imports and uses this generator continues to work without changes.
+
+Output: Complete enhanced Python file with ALL existing content preserved + new intelligent features

devdox_ai_locust-0.1.2/src/devdox_ai_locust/prompt/validation.j2

@@ -0,0 +1,17 @@
+Enhance this utils file with smarter response validation:
+
+Current File:
+{{base_content}}
+
+Validation Patterns Needed:
+{{ validation_patterns }}
+
+Enhance by:
+1. Adding endpoint-specific validation rules
+2. Creating schema-based response validation
+3. Adding business logic validation
+4. Implementing response data integrity checks
+5. Adding performance threshold validation
+
+Keep existing utility functions but add smarter validation logic.
+Output: Complete enhanced Python file content.

devdox_ai_locust-0.1.2/src/devdox_ai_locust/prompt/workflow.j2

@@ -0,0 +1,145 @@
+CRITICAL CONSTRAINTS: Only use endpoints that exist in the OpenAPI specification. DO NOT create, modify, or reference any endpoints not listed below.
+        TASK: Enhance this Locust workflow file with realistic load testing patterns and LOGICAL TASK ORDERING.
+        STRICT REQUIREMENTS:
+        1. ONLY use these exact API endpoints from OpenAPI spec:
+        {{  grouped_enpoints }}
+        2. Check Authentication Endpoints :
+        {{ auth_endpoints }}
+            - If their is endpoints to login , add login task at the beginning of the workflow If we don't have login endpoint, we can't login and retry the task
+            - In case of getting 401 so login and retry the task
+            - If their is endpoints to logout , add logout task at the end of the workflow
+        3. PRESERVE EXISTING STRUCTURE:
+           - Keep ALL existing @task methods, classes, and functions
+           - DO NOT remove any existing functionality
+           - DO NOT change existing method signatures unless enhancing them
+           - ADD to existing methods, don't replace them
+       4. ADD NEW FUNCTIONALITY WHEN NEEDED:
+           - If an API endpoint requires specific IDs, ADD new methods to generate/store those IDs
+           - ADD new test data generators to test_data.py functions
+           - ADD new example usage patterns to example.py
+           - CREATE data flow between related API calls
+
+    5. DATA FLOW AND ID MANAGEMENT:
+       - ADD instance variables to store IDs (self.reseller_id, self.user_id, etc.)
+       - ADD methods to extract and store IDs from API responses
+       - ADD logic to use stored IDs in subsequent API calls
+       - CREATE realistic data dependencies between tasks
+
+    6. ENHANCEMENT AREAS (ADD, don't replace):
+       - ADD better error handling to existing methods
+       - ADD realistic test data usage from test_data.py
+       - ADD authentication handling if auth endpoints exist
+       - ADD cleanup methods for created resources
+       - ADD data correlation between sequential tasks
+
+
+        CURRENT WORKFLOW FILE:
+        {{base_content}}
+
+        BASE WORKFLOW: {{base_workflow}}
+
+        TEST DATA AVAILABLE: {{test_data_content}}
+        1. **REORDER TASKS FOR LOGICAL FLOW**: Arrange @task methods in a meaningful business workflow sequence:
+
+   - Start with data creation tasks (e.g., add_reseller)
+
+   - Follow with data retrieval to get IDs for subsequent operations (e.g., get_reseller, get_reseller_by_id)
+
+   - Then perform operations using those IDs (e.g., customize_corporate_price, available_reseller_properties)
+
+   - End with cleanup operations (e.g., delete_reseller)
+
+
+
+2. **DATA CORRELATION**: Use data from previous tasks in subsequent tasks:
+
+   - Store reseller IDs from add_reseller for use in get_reseller_by_id, customize_price, etc.
+
+   - Pass generated data between related API calls
+
+   - Maintain state between sequential tasks for realistic workflows
+
+3. Fix indentation issues
+
+
+4. **Test Data Enhancement** (if needed, suggest additions):
+       If APIs need specific data formats, suggest:
+       - New functions to add to test_data.py
+       - New example patterns to add to example.py
+       - New data generators for specific ID requirements
+
+
+
+5. Use realistic functions and classes from base_workflow.py and don't remove classes or functions from this file
+
+6. Add intelligent request chaining between related API calls
+
+7. Add authentication handling ONLY if auth endpoints exist in OpenAPI spec
+
+8. Add error recovery for existing methods
+
+9. Add data cleanup on stop for resources created during testing
+
+10. Improve data parameterization using available test data generators
+
+
+
+LOGICAL TASK SEQUENCE EXAMPLE:
+
+For reseller workflow, the logical order should be:
+
+1. add_reseller (create) → store reseller_id
+
+2. get_reseller (list/search)
+
+3. get_reseller_by_id (using stored reseller_id)
+
+4. available_reseller_properties (using reseller_id)
+
+5. customize_corporate_price (using reseller_id)
+
+6. customize_corporate_price_csv (using reseller_id)
+
+7. customize_price (using reseller_id)
+
+8. customize_price_csv (using reseller_id)
+
+9. topup_reseller_balance (using reseller_id)
+
+10. edit_reseller (using reseller_id)
+
+11. delete_reseller (cleanup using reseller_id)
+
+VALIDATION RULES:
+    - Every @task method must correspond to an actual OpenAPI endpoint
+    - PRESERVE all existing functionality
+    - ADD new functionality only where needed for data flow
+    - Use only test_data.py functions that exist or suggest new ones to ADD
+    - Ensure realistic user workflows with proper data dependencies
+    - ADD error handling and resource cleanup
+
+    SUGGESTIONS FOR ADDITIONS (if needed):
+    If the workflow needs new test data generators or example patterns,
+    provide suggestions for what to ADD to:
+
+    test_data.py additions:
+    ```python
+    # Suggest new functions to ADD (don't replace existing)
+    def get_specific_id_data():
+        # New function for ID-dependent APIs
+        pass
+    ```
+
+    example.py additions:
+    ```python
+    # Suggest new example patterns to ADD
+    def example_id_workflow():
+        # New example showing ID usage
+        pass
+    ```
+
+    Return the complete enhanced file in <code></code> tags without truncation.
+
+
+    Format:
+    <code>your_complete_enhanced_python_code_here</code>

{devdox_ai_locust-0.1.1 → devdox_ai_locust-0.1.2}/src/devdox_ai_locust.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: devdox_ai_locust
-Version: 0.1.1
+Version: 0.1.2
 Summary: AI-powered Locust load test generator from API documentation
 Author-email: Hayat Bourji <hayat.bourgi@montyholding.com>
 Maintainer-email: Hayat Bourji <hayat.bourgi@montyholding.com>

{devdox_ai_locust-0.1.1 → devdox_ai_locust-0.1.2}/src/devdox_ai_locust.egg-info/SOURCES.txt

@@ -13,6 +13,11 @@ src/devdox_ai_locust.egg-info/dependency_links.txt
 src/devdox_ai_locust.egg-info/entry_points.txt
 src/devdox_ai_locust.egg-info/requires.txt
 src/devdox_ai_locust.egg-info/top_level.txt
+src/devdox_ai_locust/prompt/domain.j2
+src/devdox_ai_locust/prompt/locust.j2
+src/devdox_ai_locust/prompt/test_data.j2
+src/devdox_ai_locust/prompt/validation.j2
+src/devdox_ai_locust/prompt/workflow.j2
 src/devdox_ai_locust/schemas/__init__.py
 src/devdox_ai_locust/schemas/processing_result.py
 src/devdox_ai_locust/templates/base_workflow.py.j2

{devdox_ai_locust-0.1.1 → devdox_ai_locust-0.1.2}/tests/test_config.py

@@ -15,7 +15,7 @@ class TestSettings:
         """Test default settings values."""
         test_settings = Settings(_env_file=".env.example")
 
-        assert test_settings.VERSION == "0.1.1"
+        assert test_settings.VERSION == "0.1.2"
         assert test_settings.API_KEY == ""
 
     def test_settings_with_env_vars(self):
@@ -108,7 +108,7 @@ class TestSettings:
     def test_global_settings_instance(self):
         """Test the global settings instance."""
         assert isinstance(settings, Settings)
-        assert settings.VERSION == "0.1.1"
+        assert settings.VERSION == "0.1.2"
 
 
 class TestSettingsMethods:
@@ -120,7 +120,7 @@ class TestSettingsMethods:
         original_version = test_settings.VERSION
 
         # VERSION should be a class-level constant
-        assert original_version == "0.1.1"
+        assert original_version == "0.1.2"
 
         # Even if we try to change it, it should remain the same
         # (depending on Pydantic implementation)
@@ -131,7 +131,7 @@ class TestSettingsMethods:
 
         # Create new instance to verify class-level value
         new_settings = Settings()
-        assert new_settings.VERSION == "0.1.1"
+        assert new_settings.VERSION == "0.1.2"
 
     def test_settings_field_types(self):
         """Test that settings fields have correct types."""