[fix]complete the Readme

Author: Potterluo

test/.gitignore

@@ -1,6 +1,7 @@
 reports/
 dataset/
 logs/
+result_outputs/
 .cache/
 backup/
 $null

test/README.md

@@ -1,79 +1,81 @@
 # UCM Pytest Testing Framework
 
-A unified cache management testing framework based on pytest, supporting multi-level testing, flexible marking, performance data collection, and beautiful Allure report generation.
+[English](README.md) | [简体中文](README_zh.md)
+
+A unified cache management testing framework based on pytest, supporting multi-level testing, flexible tagging, performance data collection, and Allure report generation.
 
 ## Framework Features
 
-- [x] 🏗️ **Multi-level Testing**: UnitTest(0) → Smoke(1) → Feature(2) → E2E(3)
-- [x] 🏷️ **Flexible Marking**: Support for feature tags, platform tags, and reliability tags
-- [x] 📊 **Data Collection**: Integrated InfluxDB performance data pushing
-- [x] 📋 **Beautiful Reports**: Allure test report integration, supporting both static HTML and dynamic server modes
-- [x] 🔧 **Configuration Management**: Flexible YAML-based configuration system
-- [x] 🚀 **Automation**: Support for parallel test execution and automatic cleanup
+- [x] 🏗️ **Multi-Level Testing**: UnitTest(0) → Smoke(1) → Feature(2) → E2E(3)
+- [x] 🏷️ **Flexible Tagging**: Supports feature tags and custom tag addition
+- [x] 📊 **Data Collection**: Integrated InfluxDB performance data push
+- [x] 📋 **Beautiful Reports**: Allure test report integration, supporting static HTML and dynamic service modes
+- [x] 🔧 **Configuration Management**: Flexible configuration system based on YAML
+- [x] 🚀 **Automation**: Supports parallel test execution and automatic cleanup
 
 ## Test Level Definitions
 
-| Level | Name | Description | Execution Time |
-|-----|------|------|----------|
-| 0 | UnitTest | Unit Tests | Every code commit |
-| 1 | Smoke | Smoke Tests | Build verification |
-| 2 | Feature | Feature Tests | When features are completed |
-| 3 | E2E | End-to-End Tests | Before version release |
+| Level | Name | Description | Execution Timing |
+|------|------|-------------|------------------|
+| 0 | UnitTest | Unit tests | On every code commit |
+| 1 | Smoke | Smoke tests | Build verification |
+| 2 | Feature | Feature tests | When features are completed |
+| 3 | E2E | End-to-end tests | Before version release |
 
 ## Directory Structure
 
 ```
 test/
 ├── config.yaml              # Test framework configuration file
-├── conftest.py              # pytest configuration and fixtures, main program entry
+├── conftest.py              # pytest configuration and fixtures, main entry point
 ├── pytest.ini              # pytest markers and basic configuration
 ├── requirements.txt         # Dependency package list
 ├── common/                  # Common utility library
 │   ├── __init__.py
-│   ├── config_utils.py      # Configuration file reading tools
-│   ├── influxdb_utils.py    # InfluxDB writing tools
-│   └── allure_utils.py      # Allure reporting tools
+│   ├── config_utils.py      # Configuration file reading utilities
+│   ├── influxdb_utils.py    # InfluxDB write utilities
+│   └── allure_utils.py      # Allure report utilities
 ├── suites/                  # Test case directory
 │   ├── UnitTest/            # Unit tests (stage 0)
 │   ├── Smoke/               # Smoke tests (stage 1)
 │   ├── Feature/             # Feature tests (stage 2)
 │   ├── E2E/                 # End-to-end tests (stage 3)
-│   └── test_demo_function.py# Example test cases
+│   └── test_demo_function.py# Example test case
 ├── reports/                 # Test report directory
-└── logs/          # Test log directory
+└── logs/                    # Log directory
 ```
 
 ## Quick Start
 
-### 1. Environment Setup
+### 1. Environment Preparation
 ```bash
 # Install dependencies
 pip install -r requirements.txt
 
 # Ensure Allure CLI is installed (for report generation)
-# Download from: https://github.com/allure-framework/allure2/releases
+# Download address: https://github.com/allure-framework/allure2/releases  
 ```
 
 ### 2. Configuration File
 The main configuration file is `config.yaml`, containing the following configuration items:
 - **reports**: Report generation configuration (HTML/Allure)
-- **log**: Logging configuration
+- **log**: Log configuration
 - **influxdb**: Performance data push configuration
-- **llm_connection**: LLM connection configuration
 
 ### 3. Running Tests
 ```bash
 # Run all tests
 pytest
 
-# Run specific level tests
+# Run tests of a specific level
 pytest --stage=1                    # Run smoke tests
-pytest --stage=2+                   # Run feature and end-to-end tests
+pytest --stage=2+                   # Run feature tests and end-to-end tests
 
-# Run specific tag tests
+# Run tests with specific tags
 pytest --feature=performance        # Run performance-related tests
 pytest --platform=gpu               # Run GPU platform tests
-pytest --reliability=high           # Run high reliability tests
+
+pytest --platform=all               # Run tests for all platforms (all means all items with this tag)
 
 # Combined filtering
 pytest --stage=1 --feature=performance,accuracy  # Performance and accuracy tests in smoke tests
@@ -99,121 +101,126 @@ class TestExample:
         test_data = config_instance.get_config("test_data")
 
         # Act & Assert
-        with allure.step("Execute GPU computation"):
+        with allure.step("Perform GPU calculation"):
             result = perform_gpu_calculation(test_data)
             assert result.is_valid
 
-        # Collect performance data
-        from common.influxdb_utils import push_to_influx
-        push_to_influx("gpu_compute_time", result.duration, {
-            "test_name": "test_gpu_performance",
-            "platform": "gpu"
-        })
+    # Import parameters from yaml example
+    from common.config_utils import config_utils as config_instance
+    @pytest.mark.feature("config")
+    def test_llm_config():  
+        # Example of reading parameters by type
+        llm_config = config_instance.get_config("llm_connection")
+        assert llm_config["type"] == "openai"
+        # Example of reading nested parameters
+        assert config_instance.get_nested_config("llm_connection.model") == "gpt-3.5-turbo"
+        assert config_instance.get_nested_config("llm_connection.models", "gpt-3.5-turbo") == "gpt-3.5-turbo"
 ```
 
-### Marking Usage Guidelines
+### Tag Usage Guidelines
 
-#### 1. Level Markers (Required)
+#### 1. Level Tags (Required)
 ```python
-@pytest.mark.stage(0)    # Unit tests
-@pytest.mark.stage(1)    # Smoke tests
-@pytest.mark.stage(2)    # Feature tests
-@pytest.mark.stage(3)    # End-to-end tests
+@pytest.mark.stage(0)    # Unit test
+@pytest.mark.stage(1)    # Smoke test
+@pytest.mark.stage(2)    # Feature test
+@pytest.mark.stage(3)    # End-to-end test
 ```
 
-#### 2. Feature Markers (Recommended)
+#### 2. Feature Tags (Recommended)
 ```python
-@pytest.mark.feature("performance")     # Performance tests
-@pytest.mark.feature("accuracy")        # Accuracy tests
-@pytest.mark.feature("memory")          # Memory tests
+@pytest.mark.feature("performance")     # Performance test
+@pytest.mark.feature("accuracy")        # Accuracy test
+@pytest.mark.feature("memory")          # Memory test
 ```
 
-#### 3. Platform Markers (Optional)
+#### 3. Platform Tags (Optional)
 ```python
-@pytest.mark.platform("gpu")            # GPU platform tests
-@pytest.mark.platform("npu")            # NPU platform tests
-@pytest.mark.platform("cpu")            # CPU platform tests
+@pytest.mark.platform("gpu")            # GPU platform test
+@pytest.mark.platform("npu")            # NPU platform test
+@pytest.mark.platform("cpu")            # CPU platform test
 ```
 
-#### 4. Reliability Markers (Optional)
+#### 4. Reliability Tags (Optional)
 ```python
-@pytest.mark.reliability("high")        # High reliability tests
-@pytest.mark.reliability("medium")      # Medium reliability tests
-@pytest.mark.reliability("low")         # Low reliability tests
+@pytest.mark.reliability("high")        # High reliability test
+@pytest.mark.reliability("medium")      # Medium reliability test
+@pytest.mark.reliability("low")         # Low reliability test
 ```
 
 ## Allure Report Integration
 
 ### 1. Basic Usage
+Refer to the official Allure marker usage methods. Here we only introduce some commonly used markers. For more details, refer to test_demo_function.py
 ```python
 import allure
-
-@allure.feature('User Authentication')
-@allure.story('Login Function')
-def test_user_login():
-    """Test user login functionality"""
-    with allure.step("Enter username and password"):
-        login_page.enter_credentials("user", "pass")
-    
-    with allure.step("Click login button"):
-        login_page.click_login()
-    
-    with allure.step("Verify successful login"):
-        assert dashboard_page.is_displayed()
-        
-    # Add attachment
-    allure.attach("Screenshot data", name="Login Screenshot", 
-                  attachment_type=allure.attachment_type.PNG)
+@pytest.mark.feature("allure1")
+@allure.feature('test_success')
+def test_success():
+    """this test succeeds"""
+    assert True
+
+@allure.feature('test_failure')
+@pytest.mark.feature("allure1")
+def test_failure():
+    """this test fails"""
+    assert False
 ```
 
 ### 2. Report Configuration
 Configure Allure reports in `config.yaml`:
 ```yaml
 reports:
+  base_dir: "reports"
+  use_timestamp: true # Whether to use timestamps as report folder names for differentiation
+  directory_prefix: "pytest"
+  html: # pytest-html
+    enabled: false
+    filename: "report.html"
+    title: "UCM Pytest Test Report"
   allure:
-    enabled: true
-    html_enable: true
-    serve_mode: true          # Use dynamic server mode
-    serve_host: "localhost"
-    serve_port: 8081
+    enabled: false # Whether to enable Allure report collection (json, requires pytest-allure-plugin installation)
     directory: "allure-results"
+    html_enable: true # Whether to generate HTML reports (requires Allure program installation)
+    serve_mode: true  # Whether to automatically start Allure service
+    serve_host: "localhost"
+    serve_port: 8081  
 ```
 
 ### 3. Report Viewing
-- **Static HTML Mode**: Automatically generates static HTML reports after test completion
-- **Dynamic Server Mode**: Starts Allure server, providing interactive report interface
+- **Static HTML Mode**: Automatically generates static HTML reports after testing
+- **Dynamic Service Mode**: Starts an Allure server, providing an interactive report interface
 
 ## Performance Data Collection
 
-### InfluxDB Integration
+### InfluxDB Configuration
+```yaml
+influxdb:
+  url: ""
+  token: "" # Can also be read via environment variable INFLUXDB_TOKEN
+  org: "influxdb"
+  bucket: "ucm"
+  offline_file: ".cache/influxdb_offline.jsonl"
+```
+
+### InfluxDB Data Push
 ```python
-from common.influxdb_utils import push_to_influx
-
-# Collect performance data in tests
-def test_performance_metrics():
-    start_time = time.time()
-    
-    # Execute test logic
-    result = perform_operation()
-    
-    # Push performance data to InfluxDB
-    push_to_influx("operation_duration", time.time() - start_time, {
-        "test_name": "test_performance_metrics",
-        "operation_type": "calculation",
-        "success": str(result.success)
-    })
+from common.influxdb_utils import influxdb_utils as influxdb_instance
+@pytest.mark.feature("influxdb")
+def test_influxdb_push(): 
+    influxdb_instance.push_metric("cpu_usage", "value", 3.0, {"host": "server1"})
 ```
 
-## Extensions and Customization
+## Extension and Customization
 
-### Adding New Markers
-1. Add new marker definitions in the `markers` section of `pytest.ini`
-2. Keep the `markers =` and `# end of markers` lines unchanged
-3. Re-run tests to use new markers
+### Adding New Tags
+1. Add new tag definitions in the `markers` section of `pytest.ini`
+2. Keep the lines `markers =` and `# end of markers` unchanged
+3. Re-run tests to use the new tags
 
 ### Custom Configuration
-Customize through `config.yaml`:
+Customize through modifying `config.yaml`:
 - Report format and storage location
 - Log level and output format
 - InfluxDB connection parameters
-- LLM service configuration
+- Custom parameters