Test Report Metadata System

Build a test suite metadata management system that generates enhanced test reports with comprehensive metadata information.

Requirements

Create a Python test suite for an e-commerce API that includes the following test cases with proper metadata:

1. User Authentication Test - A test that verifies user login functionality

   • Should have a descriptive title indicating it tests user authentication
   • Should include a text description explaining what the test validates
   • Should be marked as CRITICAL severity
   • Should be tagged with "api" and "auth"

2. Product Search Test - A test that verifies product search functionality

   • Should have a custom title describing the search functionality
   • Should include an HTML-formatted description with bold text highlighting key validation points
   • Should be marked as NORMAL severity
   • Should be tagged with "api" and "search"

3. Payment Processing Test - A test that verifies payment processing

   • Should have a descriptive title
   • Should include a detailed description
   • Should be marked as BLOCKER severity
   • Should be tagged with "api", "payment", and "critical-path"
   • Should include a custom label "payment_gateway" with value "stripe"

4. Admin Dashboard Test - A test that verifies admin dashboard access

   • Should dynamically set its title based on a test parameter
   • Should be marked as MINOR severity
   • Should be tagged with "admin"

All tests should use appropriate metadata decorators to enhance the test report. Tests should pass (use simple assertions or pass statements).

Implementation

Create the following files:

1. test_ecommerce_api.py - Contains all four test functions with proper metadata decorators

Test Cases { .tests }

Test Case 1: Verify metadata is applied { @test }

When the test file is created with all required tests:

• All four test functions should be present
• Each test should have appropriate metadata decorators applied
• The tests should be runnable (even if they just pass)

Expected: Test file can be imported and contains all required test functions

Test Case 2: Verify severity levels { @test }

When examining the test metadata:

• User Authentication Test should use CRITICAL severity
• Product Search Test should use NORMAL severity
• Payment Processing Test should use BLOCKER severity
• Admin Dashboard Test should use MINOR severity

Expected: Each test uses the correct severity level from the allure severity levels

Test Case 3: Verify tags and labels { @test }

When examining the test metadata:

• All tests should have appropriate tags
• Payment Processing Test should have a custom label

Expected: Tags and labels are properly applied to organize and categorize tests

Dependencies { .dependencies }

allure-python-commons { .dependency }

Provides test metadata and reporting capabilities for enhanced test documentation.