Skip to content

Suite entries with conversation_id show as 'Unknown Entry' / type 'Suite' in UI #6

Description

@zvonimirfras

Bug: Suite entries linked via conversation_id are not rendered correctly in the Test Suite detail page

Summary

When a test suite contains entries linked by conversation_id (rather than test_id), the suite detail page displays them as:

  • Type: Suite (should be Conversation)
  • Name: Unknown Entry (should be the conversation name)

Root cause

In frontend/src/app/test-suites/[id]/page.tsx:

  1. getEntryName only handles entry.test_id and entry.child_suite_id — there is no branch for entry.conversation_id:
const getEntryName = (entry: SuiteEntry): string => {
  if (entry.test_id) { ... }
  else if (entry.child_suite_id) { ... }
  return 'Unknown Entry'; // conversation_id entries always fall here
};
  1. Type column uses entry.test_id ? 'Test' : 'Suite', so conversation entries always render as Suite:
<TableCell>{entry.test_id ? 'Test' : 'Suite'}</TableCell>
  1. useTestSuiteDetailData fetches allTests and allSuites but never fetches allConversations, so even if getEntryName had a conversation_id branch, it would have nothing to look up against.

Fix

  • Fetch all conversations in useTestSuiteDetailData and expose them (similar to allTests).
  • Add a conversation_id branch to getEntryName that looks up the conversation name.
  • Fix the Type cell to return 'Conversation' when entry.conversation_id is set.

Steps to reproduce

  1. Create a test suite via the data-transfer import API with entries that reference conversations by name (using conversation_name in ExportedSuiteEntry).
  2. Open the suite detail page in the frontend.
  3. All entries show as type Suite / name Unknown Entry.

Impact

Purely cosmetic — the suite runs correctly (execution, scoring, and results all work). Only the display in the suite detail page is affected.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions