failing cuke tests

cucumber -p builder builder/cluster_update.feature:139 # Scenario: Verify that units that already belong to a cluster won't show in the list when editing that cluster
cucumber -p builder builder/form_update.feature:92 # Scenario: Verify that clusters that already belong to a form won't show in the list when editing that form
cucumber -p builder builder/form_update.feature:104 # Scenario: View link to delete a cluster from a form
cucumber -p builder builder/form_update.feature:112 # Scenario: Delete a cluster from a form that has one cluster
cucumber -p builder builder/test_publish.feature:60 # Scenario: Visit delete form page for a form that belongs to a published and receive an error message
cucumber -p builder builder/test_publish.feature:92 # Scenario: Visit edit cluster page for a cluster that belongs to a published and receive an error message
cucumber -p builder builder/test_publish.feature:108 # Scenario: Visit delete cluster page for a cluster that belongs to a published and receive an error message
cucumber -p builder builder/test_publish.feature:125 # Scenario: Visit units page with one unit that belongs to a published test and not see edit/delete links
cucumber -p builder builder/test_publish.feature:144 # Scenario: Visit edit unit page for a unit that belongs to a published and receive an error message
cucumber -p builder builder/test_publish.feature:162 # Scenario: Visit delete unit page for a unit that belongs to a published and receive an error message
cucumber -p builder builder/test_publish.feature:209 # Scenario: Visit edit test page for a form that belongs to a unpublished test and not see locked
cucumber -p builder builder/test_publish.feature:227 # Scenario: Visit edit cluster page with one cluster that belongs to a unpublished test and not see locked
cucumber -p builder builder/test_publish.feature:253 # Scenario: Visit tests page with one published test and see locked
cucumber -p builder builder/test_publish.feature:261 # Scenario: Visit forms page with one form that belongs to a published test and see locked
cucumber -p builder builder/test_publish.feature:272 # Scenario: Visit clusters page with one cluster that belongs to a published test and see locked
cucumber -p builder builder/test_publish.feature:286 # Scenario: Visit units page with one unit that belongs to a published test and see locked
cucumber -p builder builder/test_update.feature:109 # Scenario: Verify that forms that already belong to a test won't show in the list when editing that test