A couple of tests use the step

When(/^I click the Post Actions link on the 3rd comment on the topic$/) do
  on(FlowPage).third_post_actions_link_element.when_present.click
end

The selector for third_post_actions_link is

a(:third_post_actions_link, css: ".flow-topic .flow-post .flow-menu-js-drop a", index: 3)

but if the first three topics only have one post each, this will happily select the action link for the first post on the third topic.

I think the selector has to get the first ".flow-topic" (there is a flow_first_topic_element already defined), and then within this look for '.flow-menu-js-drop a', index: 3. In jQuery/Sizzle, this would be $( '.flow-topic:first .flow-post .flow-menu-js-drop a:eq(2)').click() (JavaScript/jQuery uses 0-based index, so 2 is the third item).

I think the third_post_actions_menu_element has a similar flaw.

If you look at the screencast of a browser test failing near this, you see that a bunch of extraneous topics appear on the page, I think because another test is running at the same time. The test fails at `And I click Hide comment button' but the real error is before that. Fixing this bug will make the test fail at the right place, but it will still fail. What all Flow tests really need to do is target "The topic I just added", instead of assuming that the topic they've added will always be the first one on the board.