adjust behat tests now that adding elements action flow is different

Recent changes to the way that blocks are created and inserted into
an elemental area mean that the granularity of the behat tests was
causing them to fail. Changes here are still reasonably granular,
but a step in simplifying to BDD

client/src/components/ElementEditor/Header.js

@@ -67,7 +67,7 @@ class Header extends Component {
       ElementActionsComponent,
     } = this.props;
 
-    const noTitle = i18n.inject(i18n._t('ElementHeader.NOTITLE', 'Untitled {type} element'), { type: elementType });
+    const noTitle = i18n.inject(i18n._t('ElementHeader.NOTITLE', 'Untitled {type} block'), { type: elementType });
     const titleClasses = classNames({
       'element-editor-header__title': true,
       'element-editor-header__title--none': !title,

tests/Behat/features/add-block-element.feature

@@ -22,13 +22,9 @@ Feature: Add elements in the CMS
     Then I press the "Add block" button
     Then I press the "Content" button in the add block popover
       And I wait 1 second
-      And I fill in "Eve's Block" for "Title"
-      # Note: using un-namespaced fields in PHP GridField
-      And I fill in "<p>Some content III</p>" for the "HTML" HTML field
-      And I press the "Create" button
-    Then I should see a "Saved content block" message
+    Then I should see "Untitled Content block" as the title for block 1
 
     When I go to "/admin/pages/edit/show/6"
       And I see a list of blocks
     Then I wait 1 second
-      And I should see "Eve's Block"
+      And I should see "Untitled Content block"