Fix pre-existing AdminTopicFlowsTest failure

[AndreRobitaille]

Problem

test/integration/admin_topic_flows_test.rb:27 (test_can_view_topics_list_with_sorting) has been failing before the TopicBriefing work. It expects exactly 4 <tr> elements but finds 7.

Reproduction

bin/rails test test/integration/admin_topic_flows_test.rb:27

Failure:
AdminTopicFlowsTest#test_can_view_topics_list_with_sorting [test/integration/admin_topic_flows_test.rb:30]:
Expected exactly 4 elements matching "tr", found 7.
Expected: 4
  Actual: 7

Likely cause

The test's fixture/factory setup creates 3 topics (expecting 3 data rows + 1 header = 4 <tr>), but additional topics exist from other fixtures or the test setup, producing 7 rows total. The assertion needs to account for the actual fixture count or scope more precisely.

Files

• test/integration/admin_topic_flows_test.rb:27-30

[AndreRobitaille]

Fixed. The _topic.html.erb partial renders two <tr> per topic (data row + hidden preview row), so 3 topics = 7 <tr> total (1 header + 3×2). Updated the count assertion and used tbody tr:first-child selector for sorting assertions to skip preview rows.