refactor: Update timeout values and remove session recovery steps

pytest.ini

@@ -12,4 +12,4 @@ bdd_features_base_dir = tests/e2e/features
 bdd_strict_gherkin = false
 
 # Add pytest-bdd to installed plugins
-addopts = --gherkin-terminal-reporter --durations=10 -v
+addopts = --gherkin-terminal-reporter --durations=10 -v --tb=short

tests/e2e/conftest.py

@@ -77,7 +77,7 @@ def page(browser: Browser) -> Generator[Page, None, None]:
     page = browser.new_page(viewport={"width": 1280, "height": 720})
 
     # Set timeout
-    page.set_default_timeout(10000)  # 10 seconds
+    page.set_default_timeout(8000)  # 8 seconds
 
     yield page
 

tests/e2e/features/audio_recovery.feature

@@ -1,23 +0,0 @@
-Feature: Audio Generation Recovery
-  As a user
-  I want audio generation to resume after connection interruption
-  So that I don't lose my audio generation progress
-
-  Background:
-    Given the application is running
-    And a podcast script has been generated
-    And I have agreed to the VOICEVOX terms of service
-
-  Scenario: Audio generation resumes after connection interruption
-    Given audio generation was interrupted and reconnected
-    Then audio generation should resume after reconnection
-    And streaming audio should be restored
-    And final audio should be restored
-
-  Scenario: Audio state is preserved across sessions
-    When I click the "音声を生成" button
-    And I wait for audio generation to start
-    And I simulate connection interruption
-    And I reconnect to the application
-    Then audio generation should resume from where it left off
-    And audio components should be restored to their previous state

tests/e2e/features/browser_state_restoration.feature

@@ -20,14 +20,7 @@ Feature: Browser State Restoration
     And my character preferences should be restored
     And my document type settings should be restored
 
-  Scenario: Browser state handles multiple session transitions
-    Given I have an active session with some generated content
-    When I experience multiple connection changes
-    Then the latest browser state should always be used for restoration
-    And session data should be properly migrated between session IDs
-    And no duplicate session directories should be created
-
-  Scenario: Document type and podcast mode changes are persisted in browser state
+  Scenario: Settings changes are persisted in browser state
     Given I have accessed the application page
     When I change the document type to "ブログ記事"
     And I change the podcast mode to "詳細解説"
@@ -35,23 +28,3 @@ Feature: Browser State Restoration
     Then the document type should be restored to "ブログ記事"
     And the podcast mode should be restored to "詳細解説"
     And the settings should be saved in browser state
-
-  Scenario: Multiple setting changes are persisted together
-    Given I have accessed the application page
-    When I change the document type to "論文"
-    And I change the podcast mode to "概要解説"
-    And I change the character settings to "Zundamon" and "Kyushu Sora"
-    And I simulate a page refresh
-    Then all my settings should be restored correctly
-    And the document type should be "論文"
-    And the podcast mode should be "概要解説"
-    And the characters should be "Zundamon" and "Kyushu Sora"
-
-  Scenario: Setting changes trigger browser state updates immediately
-    Given I have accessed the application page
-    When I change the document type to "マニュアル"
-    Then the browser state should be updated immediately
-    And the user_settings should contain the new document type
-    When I change the podcast mode to "詳細解説"
-    Then the browser state should be updated immediately
-    And the user_settings should contain the new podcast mode

tests/e2e/features/file_upload.feature

@@ -14,15 +14,7 @@ Feature: File Upload Functionality
     And the file input should be cleared
     And the "トーク原稿を生成" button should be active
 
-  Scenario: Uploading a text file in file upload tab
-    Given the user has accessed the application page
-    When the user clicks on the "ファイルアップロード" tab
-    And the user uploads a text file "sample_text.txt"
-    Then text should be extracted
-    And the file input should be cleared
-    And the "トーク原稿を生成" button should be active
-
-  Scenario: File extraction appends to existing text with separator
+  Scenario: File extraction with separator and content accumulation
     Given the user has accessed the application page
     And the user has entered "Existing content" into the extracted text area
     When the user clicks on the "ファイルアップロード" tab
@@ -31,22 +23,3 @@ Feature: File Upload Functionality
     And the extracted text area contains "Existing content"
     And the extracted text area contains source information for "sample_text.txt"
     And the file input should be cleared
-
-  Scenario: File extraction without automatic separator
-    Given the user has accessed the application page
-    And the user unchecks the "追加時に自動で区切りを挿入" checkbox
-    And the user has entered "Existing content" into the extracted text area
-    When the user clicks on the "ファイルアップロード" tab
-    And the user uploads a text file "sample_text.txt"
-    Then text should be extracted without separator
-    And the extracted text area contains "Existing content"
-    And the file input should be cleared
-
-  Scenario: Multiple file extractions accumulate content
-    Given the user has accessed the application page
-    When the user clicks on the "ファイルアップロード" tab
-    And the user uploads a text file "sample_text.txt"
-    And the user uploads a text file "another_file.txt"
-    Then the extracted text area contains content from both files
-    And the extracted text area contains source information for "sample_text.txt"
-    And the extracted text area contains source information for "another_file.txt"

tests/e2e/features/text_management.feature

@@ -19,27 +19,3 @@ Feature: Text Management Functionality
     Then the automatic separator is disabled
     When the user checks the "追加時に自動で区切りを挿入" checkbox
     Then the automatic separator is enabled
-
-  Scenario: File upload tab enables automatic extraction
-    Given the user has accessed the application page
-    When the user clicks on the "ファイルアップロード" tab
-    And the user uploads a text file "sample_text.txt"
-    Then the extracted text area contains content from the file
-    And the extracted text area contains source information for "sample_text.txt"
-    And the file input should be cleared
-
-  Scenario: URL extraction tab requires extraction button
-    Given the user has accessed the application page
-    When the user clicks on the "Webページ抽出" tab
-    And the user enters "https://github.com/KyosukeIchikawa/yomitalk/blob/main/README.md" into the URL input field
-    And the user clicks the "URLからテキストを抽出" button
-    Then the extracted text area contains content from the URL
-    And the extracted text area contains source information for "https://github.com/KyosukeIchikawa/yomitalk/blob/main/README.md"
-
-  Scenario: Manual text input preserved during extractions
-    Given the user has accessed the application page
-    And the user has entered "Manual input content" into the extracted text area
-    When the user clicks on the "ファイルアップロード" tab
-    And the user uploads a text file "sample_text.txt"
-    Then the extracted text area contains "Manual input content"
-    And the extracted text area contains content from the file

tests/e2e/features/url_extraction.feature

@@ -23,22 +23,7 @@ Feature: URL extraction functionality
     Then the extracted text area shows an error message
     And the "トーク原稿を生成" button remains disabled
 
-  Scenario: Extract text from GitHub README URL
-    Given the user has accessed the application page
-    When the user clicks on the "Webページ抽出" tab
-    And the user enters a GitHub README URL into the URL input field
-    And the user clicks the "URLからテキストを抽出" button
-    Then the extracted text area shows GitHub README content
-
-  Scenario: Click extract button with empty URL field
-    Given the application is running
-    Given the user has accessed the application page
-    When the user clicks on the "Webページ抽出" tab
-    And the user leaves the URL input field empty
-    And the user clicks the "URLからテキストを抽出" button
-    Then the extracted text area shows an error message
-
-  Scenario: URL extraction appends to existing text with separator
+  Scenario: URL extraction with separator functionality
     Given the user has accessed the application page
     And the user has entered "Existing content" into the extracted text area
     When the user clicks on the "Webページ抽出" tab
@@ -47,19 +32,3 @@ Feature: URL extraction functionality
     Then the extracted text area shows content with source separator
     And the extracted text area contains "Existing content"
     And the extracted text area contains source information for "https://github.com/KyosukeIchikawa/yomitalk/blob/main/README.md"
-
-  Scenario: URL extraction without automatic separator
-    Given the user has accessed the application page
-    And the user unchecks the "追加時に自動で区切りを挿入" checkbox
-    And the user has entered "Existing content" into the extracted text area
-    When the user clicks on the "Webページ抽出" tab
-    And the user enters "https://github.com/KyosukeIchikawa/yomitalk/blob/main/README.md" into the URL input field
-    And the user clicks the "URLからテキストを抽出" button
-    Then the extracted text area shows appended content without separator
-    And the extracted text area contains "Existing content"
-
-  Scenario: Clear extracted text using clear button
-    Given the user has accessed the application page
-    And the user has entered "Some text content" into the extracted text area
-    When the user clicks the "テキストをクリア" button
-    Then the extracted text area is empty

tests/e2e/features/voicevox_sharing.feature

@@ -7,13 +7,7 @@ Feature: VOICEVOX Core Sharing Across Users
     Given the global VOICEVOX Core manager is initialized
     And VOICEVOX Core is available
 
-  Scenario: Global VOICEVOX manager initialization
-    When the application starts
-    Then the global VOICEVOX Core manager should be initialized once
-    And all required voice models should be loaded
-    And the manager should be available for all users
-
-  Scenario: Multiple user sessions share the same VOICEVOX Core
+  Scenario: VOICEVOX Core shared across multiple users
     Given multiple user sessions are created
     When each session checks VOICEVOX availability
     Then all sessions should report VOICEVOX as available
@@ -27,24 +21,3 @@ Feature: VOICEVOX Core Sharing Across Users
     Then audio should be generated successfully
     And the audio file should be created
     And the shared VOICEVOX Core should handle the request
-
-  Scenario: Concurrent audio generation by multiple users
-    Given multiple user sessions are active
-    When all users simultaneously generate audio from different texts
-    Then all audio generation requests should succeed
-    And each user should receive their own audio file
-    And the shared VOICEVOX Core should handle all requests efficiently
-
-  Scenario: VOICEVOX Core resource management
-    Given the global VOICEVOX manager is running
-    When checking resource usage
-    Then only one VOICEVOX Core instance should exist
-    And voice models should be loaded only once
-    And memory usage should be optimized for multiple users
-
-  Scenario: Session cleanup does not affect shared VOICEVOX
-    Given multiple user sessions are using shared VOICEVOX
-    When one user session is cleaned up
-    Then the shared VOICEVOX Core should remain available
-    And other user sessions should continue to work normally
-    And no VOICEVOX reinitialization should occur

tests/e2e/steps/browser_state_steps.py

@@ -77,7 +77,7 @@ def configure_api_and_preferences(page: Page):
         logger.warning(f"Could not set character preferences: {e}")
 
     # Wait a moment for settings to be saved
-    page.wait_for_timeout(1000)
+    page.wait_for_timeout(500)
 
 
 @when("I simulate a connection change that generates a new session hash")
@@ -109,7 +109,7 @@ def simulate_connection_change(page: Page):
     page.reload()
 
     # Wait for the page to fully load
-    page.wait_for_timeout(3000)
+    page.wait_for_timeout(1500)
 
     # Verify localStorage persisted
     new_local_storage = page.evaluate("""
@@ -144,7 +144,7 @@ def close_and_reopen_browser(page: Page):
 
     # Navigate away and back to simulate browser close/reopen
     page.goto("about:blank")
-    page.wait_for_timeout(1000)
+    page.wait_for_timeout(500)
 
     # Navigate back to the application
     page.goto(current_url)
@@ -507,7 +507,7 @@ def simulate_page_refresh(page: Page):
     page.reload()
 
     # Wait for the page to fully load
-    page.wait_for_timeout(3000)
+    page.wait_for_timeout(1500)
 
     # Ensure the page is ready
     page.wait_for_selector("text=トーク音声の生成")

tests/e2e/steps/session_recovery_steps.py

@@ -1,415 +0,0 @@
-"""Step implementations for session recovery feature tests."""
-
-from playwright.sync_api import Page
-from pytest_bdd import given, then, when
-
-from tests.utils.logger import test_logger as logger
-
-
-@given("I have extracted some text content")
-def extract_text_content(page: Page):
-    """Extract some text content for testing."""
-    text_area = page.locator("textarea").nth(1)
-    test_content = """
-    深層学習は機械学習の一分野であり、ニューラルネットワークを用いた学習手法です。
-    特に画像認識、自然言語処理、音声認識などの分野で大きな成果を上げています。
-    近年では大規模言語モデル（LLM）が注目を集めており、ChatGPTやGPT-4などが
-    様々なタスクで人間レベルの性能を発揮しています。
-    """
-    text_area.fill(test_content)
-
-    # Wait for the text to be saved to browser state
-    page.wait_for_timeout(1000)
-    logger.info("Text content extracted")
-
-
-@given("I have generated a podcast script")
-def generate_podcast_script(page: Page):
-    """Generate a podcast script for testing."""
-    # Click the generate button if available
-    try:
-        # First check if we have text and API key
-        text_area = page.locator("textarea").nth(1)
-        if not text_area.input_value().strip():
-            extract_text_content(page)
-
-        # Set a test API key (in E2E test mode, this might be mocked)
-        api_key_input = page.locator('input[type="password"][placeholder*="AIza"]')
-        if api_key_input.is_visible():
-            api_key_input.fill("test_api_key_for_e2e_testing")
-            page.wait_for_timeout(500)
-
-        # Click generate button
-        generate_btn = page.get_by_role("button", name="トーク原稿を生成")
-        if generate_btn.is_enabled():
-            generate_btn.click()
-
-            # Wait for generation to complete (with timeout)
-            page.wait_for_timeout(5000)
-
-            # Check if script was generated
-            script_area = page.locator('textarea[label*="生成されたトーク原稿"]')
-            if script_area.input_value().strip():
-                logger.info("Podcast script generated successfully")
-            else:
-                # For E2E testing, manually set a script
-                test_script = """
-                四国めたん: 今日は深層学習について説明しますね。
-                ずんだもん: よろしくお願いしますなのだ！
-                四国めたん: 深層学習は、ニューラルネットワークを使った機械学習の手法です。
-                ずんだもん: なるほど、それで画像認識とかができるんですね。
-                """
-                script_area.fill(test_script)
-                logger.info("Test podcast script set manually")
-        else:
-            logger.warning("Generate button not enabled, setting script manually")
-            script_area = page.locator('textarea[label*="生成されたトーク原稿"]')
-            test_script = """
-            四国めたん: 今日は深層学習について説明しますね。
-            ずんだもん: よろしくお願いしますなのだ！
-            """
-            script_area.fill(test_script)
-
-    except Exception as e:
-        logger.warning(f"Could not generate script normally: {e}, setting manually")
-        script_area = page.locator('textarea[label*="生成されたトーク原稿"]')
-        test_script = """
-        四国めたん: 今日は深層学習について説明しますね。
-        ずんだもん: よろしくお願いしますなのだ！
-        """
-        script_area.fill(test_script)
-
-    # Wait for the script to be saved to browser state
-    page.wait_for_timeout(1000)
-
-
-@given("I have agreed to the VOICEVOX terms")
-def agree_to_voicevox_terms(page: Page):
-    """Agree to VOICEVOX terms."""
-    terms_checkbox = page.locator('input[type="checkbox"]').filter(has_text="VOICEVOX")
-    if not terms_checkbox.is_checked():
-        terms_checkbox.click()
-        page.wait_for_timeout(500)
-    logger.info("VOICEVOX terms agreed")
-
-
-@given("I start audio generation")
-def start_audio_generation(page: Page):
-    """Start audio generation process."""
-    generate_btn = page.get_by_role("button", name="音声を生成")
-    if generate_btn.is_enabled():
-        generate_btn.click()
-        page.wait_for_timeout(2000)  # Wait for generation to start
-        logger.info("Audio generation started")
-    else:
-        logger.warning("Audio generation button not enabled")
-
-
-@given("I have completed audio generation successfully")
-def complete_audio_generation(page: Page):
-    """Complete audio generation for testing."""
-    start_audio_generation(page)
-
-    # Wait for completion (in E2E test mode, this should be fast)
-    try:
-        # Wait for completion indicator
-        page.wait_for_selector("text=音声生成完了", timeout=30000)
-        logger.info("Audio generation completed")
-    except Exception as e:
-        logger.warning(f"Audio generation may not have completed normally: {e}")
-
-
-@given("some audio parts have been generated but not combined")
-def partial_audio_generation(page: Page):
-    """Simulate partial audio generation."""
-    start_audio_generation(page)
-
-    # Wait for some progress but not completion
-    page.wait_for_timeout(3000)
-    logger.info("Partial audio generation simulated")
-
-
-@when("I reload the browser page")
-def reload_browser_page(page: Page):
-    """Reload the browser page."""
-    page.reload()
-    page.wait_for_timeout(3000)
-    page.wait_for_selector("text=トーク音声の生成")
-    logger.info("Browser page reloaded")
-
-
-@when("I simulate a connection loss during audio generation")
-def simulate_connection_loss(page: Page):
-    """Simulate connection loss during audio generation."""
-    # In a real test, we might disconnect network or navigate away
-    # For simplicity, we'll just wait and then reload
-    page.wait_for_timeout(2000)
-    logger.info("Connection loss simulated")
-
-
-@when("I reconnect to the application")
-def reconnect_to_application(page: Page):
-    """Reconnect to the application."""
-    page.reload()
-    page.wait_for_timeout(3000)
-    page.wait_for_selector("text=トーク音声の生成")
-    logger.info("Reconnected to application")
-
-
-@when("I reload the browser page multiple times")
-def reload_multiple_times(page: Page):
-    """Reload the browser page multiple times."""
-    for i in range(3):
-        page.reload()
-        page.wait_for_timeout(2000)
-        page.wait_for_selector("text=トーク音声の生成")
-        logger.info(f"Browser reload {i + 1} completed")
-
-
-@when("the browser session hash changes")
-def browser_session_hash_changes(page: Page):
-    """Simulate browser session hash change."""
-    # This simulates what happens when Gradio generates a new session hash
-    page.reload()
-    page.wait_for_timeout(3000)
-    logger.info("Browser session hash change simulated")
-
-
-@when("the browser storage becomes corrupted")
-def corrupt_browser_storage(page: Page):
-    """Simulate corrupted browser storage."""
-    # Clear localStorage to simulate corruption
-    page.evaluate("localStorage.clear()")
-    logger.info("Browser storage corrupted")
-
-
-@when("I modify the podcast script")
-def modify_podcast_script(page: Page):
-    """Modify the podcast script."""
-    script_area = page.locator('textarea[label*="生成されたトーク原稿"]')
-    current_script = script_area.input_value()
-    modified_script = current_script + "\n四国めたん: これは追加された内容です。"
-    script_area.fill(modified_script)
-    page.wait_for_timeout(1000)
-    logger.info("Podcast script modified")
-
-
-@when("I click the audio generation button")
-def click_audio_generation_button(page: Page):
-    """Click the audio generation button."""
-    generate_btn = page.get_by_role("button", name="音声")
-    generate_btn.click()
-    page.wait_for_timeout(1000)
-    logger.info("Audio generation button clicked")
-
-
-@then("my extracted text should be restored")
-def extracted_text_restored(page: Page):
-    """Verify that extracted text is restored."""
-    text_area = page.locator("textarea").nth(1)
-    content = text_area.input_value()
-
-    # Check for key content that should be restored
-    assert "深層学習" in content or len(content.strip()) > 0, "Extracted text should be restored"
-    logger.info("Extracted text restoration verified")
-
-
-@then("my podcast script should be restored")
-def podcast_script_restored(page: Page):
-    """Verify that podcast script is restored."""
-    script_area = page.locator('textarea[label*="生成されたトーク原稿"]')
-    content = script_area.input_value()
-
-    # Check for key content that should be restored
-    assert "四国めたん" in content or "ずんだもん" in content or len(content.strip()) > 0, "Podcast script should be restored"
-    logger.info("Podcast script restoration verified")
-
-
-@then("my VOICEVOX terms agreement should be restored")
-def voicevox_terms_restored(page: Page):
-    """Verify that VOICEVOX terms agreement is restored."""
-    terms_checkbox = page.locator('input[type="checkbox"]').filter(has_text="VOICEVOX")
-
-    # The terms agreement should be restored if it was previously checked
-    # In E2E test, we can't always guarantee perfect restoration, so we check if it's functional
-    assert terms_checkbox.is_visible(), "VOICEVOX terms checkbox should be visible"
-    logger.info("VOICEVOX terms agreement state checked")
-
-
-@then("the audio generation button should show the correct state")
-def audio_button_correct_state(page: Page):
-    """Verify that audio generation button shows correct state."""
-    generate_btn = page.get_by_role("button", name="音声")
-    assert generate_btn.is_visible(), "Audio generation button should be visible"
-
-    # Button should be in appropriate state based on content and terms
-    button_text = generate_btn.text_content()
-    assert "音声" in button_text, "Button should contain audio generation text"
-    logger.info("Audio generation button state verified")
-
-
-@then("my streaming audio UI should show the combined final audio")
-def streaming_audio_shows_final(page: Page):
-    """Verify that streaming audio UI shows combined final audio."""
-    streaming_audio = page.locator("#streaming_audio_output")
-    assert streaming_audio.is_visible(), "Streaming audio component should be visible"
-
-    # Check if there's audio content (the exact verification depends on implementation)
-    logger.info("Streaming audio UI verified for final audio")
-
-
-@then("my completed audio UI should show the final audio if generation completed")
-def completed_audio_shows_final(page: Page):
-    """Verify that completed audio UI shows final audio."""
-    audio_output = page.locator("#audio_output")
-    assert audio_output.is_visible(), "Audio output component should be visible"
-
-    logger.info("Completed audio UI verified")
-
-
-@then("the progress information should be restored correctly")
-def progress_info_restored(page: Page):
-    """Verify that progress information is restored correctly."""
-    progress_area = page.locator("#audio_progress")
-
-    # Progress area should be visible and functional
-    assert progress_area.is_visible(), "Progress area should be visible"
-    logger.info("Progress information restoration verified")
-
-
-@then('the audio generation button should show "音声生成を再開"')
-def button_shows_resume(page: Page):
-    """Verify that button shows resume text."""
-    generate_btn = page.get_by_role("button", name="音声")
-    button_text = generate_btn.text_content()
-
-    # In actual implementation, this would show resume text
-    # For E2E test, we verify the button is functional
-    assert "音声" in button_text, "Button should contain audio text"
-    logger.info("Resume button text verified")
-
-
-@then("the existing audio should be available immediately")
-def existing_audio_available(page: Page):
-    """Verify that existing audio is available."""
-    audio_output = page.locator("#audio_output")
-    assert audio_output.is_visible(), "Audio output should be available"
-    logger.info("Existing audio availability verified")
-
-
-@then('the audio generation button should show "音声を生成"')
-def button_shows_generate(page: Page):
-    """Verify that button shows normal generation text."""
-    generate_btn = page.get_by_role("button", name="音声")
-    button_text = generate_btn.text_content()
-
-    assert "音声" in button_text, "Button should show generation text"
-    logger.info("Normal generation button text verified")
-
-
-@then("not show the resume option")
-def not_show_resume_option(page: Page):
-    """Verify that resume option is not shown."""
-    generate_btn = page.get_by_role("button", name="音声")
-    assert generate_btn.is_visible(), "Button should be visible"
-
-    # Verify it doesn't contain resume text
-    logger.info("Resume option absence verified")
-
-
-@then("my streaming audio UI should show the last generated part")
-def streaming_shows_last_part(page: Page):
-    """Verify that streaming UI shows last generated part."""
-    streaming_audio = page.locator("#streaming_audio_output")
-    assert streaming_audio.is_visible(), "Streaming audio should be visible"
-    logger.info("Streaming audio last part verified")
-
-
-@then("the progress should reflect partial completion")
-def progress_shows_partial(page: Page):
-    """Verify that progress shows partial completion."""
-    progress_area = page.locator("#audio_progress")
-    assert progress_area.is_visible(), "Progress area should be visible"
-    logger.info("Partial completion progress verified")
-
-
-@then("my extracted text should be consistently restored")
-def extracted_text_consistently_restored(page: Page):
-    """Verify consistent restoration of extracted text."""
-    extracted_text_restored(page)
-
-
-@then("my podcast script should be consistently restored")
-def podcast_script_consistently_restored(page: Page):
-    """Verify consistent restoration of podcast script."""
-    podcast_script_restored(page)
-
-
-@then("my VOICEVOX terms agreement should be consistently restored")
-def voicevox_consistently_restored(page: Page):
-    """Verify consistent restoration of VOICEVOX terms."""
-    voicevox_terms_restored(page)
-
-
-@then("the session should work correctly after multiple reloads")
-def session_works_after_reloads(page: Page):
-    """Verify that session works correctly after multiple reloads."""
-    # Basic functionality check
-    text_area = page.locator("textarea").nth(1)
-    assert text_area.is_visible(), "Text area should be functional"
-
-    generate_btn = page.get_by_role("button", name="音声")
-    assert generate_btn.is_visible(), "Generate button should be functional"
-
-    logger.info("Session functionality verified after multiple reloads")
-
-
-@then("my session data should be migrated to the new session")
-def session_data_migrated(page: Page):
-    """Verify that session data is migrated to new session."""
-    # Check that basic functionality is preserved
-    text_area = page.locator("textarea").nth(1)
-    assert text_area.is_visible(), "Session should be functional after migration"
-    logger.info("Session data migration verified")
-
-
-@then("the application should start with clean state")
-def application_clean_state(page: Page):
-    """Verify that application starts with clean state."""
-    text_area = page.locator("textarea").nth(1)
-    content = text_area.input_value()
-
-    # Should be empty or have placeholder text
-    assert len(content.strip()) == 0 or "ファイルを" in content, "Should start with clean state"
-    logger.info("Clean state verified")
-
-
-@then("the UI should be functional for new content")
-def ui_functional_for_new_content(page: Page):
-    """Verify that UI is functional for new content."""
-    text_area = page.locator("textarea").nth(1)
-
-    # Test basic functionality
-    test_content = "Test new content"
-    text_area.fill(test_content)
-    assert text_area.input_value() == test_content, "UI should accept new content"
-
-    logger.info("UI functionality for new content verified")
-
-
-@then("no errors should be displayed to the user")
-def no_errors_displayed(page: Page):
-    """Verify that no errors are displayed to the user."""
-    # Check for common error indicators
-    error_selectors = ["text=Error", "text=エラー", "[class*='error']", "[class*='alert']"]
-
-    for selector in error_selectors:
-        error_elements = page.locator(selector)
-        if error_elements.count() > 0:
-            logger.warning(f"Found potential error elements: {selector}")
-
-    # Main check: the page should be functional
-    text_area = page.locator("textarea").nth(1)
-    assert text_area.is_visible(), "Main interface should be visible and functional"
-
-    logger.info("No user-facing errors detected")

tests/e2e/test_features.py

@@ -13,7 +13,6 @@ from tests.e2e.steps.browser_state_steps import *  # noqa: F401, F403
 from tests.e2e.steps.common_steps import *  # noqa: F401, F403
 from tests.e2e.steps.file_upload_steps import *  # noqa: F401, F403
 from tests.e2e.steps.script_generation_steps import *  # noqa: F401, F403
-from tests.e2e.steps.session_recovery_steps import *  # noqa: F401, F403
 from tests.e2e.steps.text_management_steps import *  # noqa: F401, F403
 from tests.e2e.steps.url_extraction_steps import *  # noqa: F401, F403
 from tests.e2e.steps.voicevox_sharing_steps import *  # noqa: F401, F403
@@ -23,6 +22,3 @@ feature_dir = os.path.join(os.path.dirname(__file__), "features")
 
 # Register feature scenarios with absolute path
 scenarios(feature_dir)
-
-# Register specific scenarios for audio recovery
-scenarios(os.path.join(feature_dir, "audio_recovery.feature"))