TASK: More isolated e2e tests (on their own page)

[mhsdesign]

resolves: #3542

I tried to start with my proposed changes. For now i want to run the createNewNodes.e2e.js on their own site. But for some reason i can't create new nodes via the inline ui if there is no existing node in the content collection. (At least thats the difference between when the test is run on the home page. And removing the existing node on the homepage yields the same error)

So i tried to debug this test yarn run testcafe chrome Tests/IntegrationTests/Fixtures -T 'Can create content node from inside InlineUI' --debug-on-fail

It testcafe just says 1) Uncaught object "[object Object]" was thrown. Throw Error instead.. I could narrow it down via a try catch to the following lines. And after refining i found out that the line click(Selector('.neos-contentcollection')) was failing.

neos-ui/Tests/IntegrationTests/Fixtures/1Dimension/createNewNodes.e2e.js

Lines 159 to 169 in 7ea5dd7

	test('Can create content node from inside InlineUI', async t => {
	const headlineTitle = 'Helloworld!';
	subSection('Create a headline node');
	await Page.waitForIframeLoading(t);
	await t
	.switchToIframe(contentIframeSelector)
	.click(Selector('.neos-contentcollection'))
	.click(Selector('#neos-InlineToolbar-AddNode'))
	.switchToMainWindow()
	.click(Selector('button#into'))
	.click(ReactSelector('NodeTypeItem').withProps({nodeType: {label: 'Headline_Test'}}));

After putting it in a try catch, it logged

{
  callsite: CallsiteRecord {
    filename: 'Neos.Neos.Ui/Tests/IntegrationTests/Fixtures/1Dimension/createNewNodes.e2e.js',
    lineNum: 166,
    callsiteFrameIdx: 5,
    stackFrames: [
      [Object],    [Object],
      [Object],    [Object],
      [Object],    [Object],
      CallSite {}, [Object],
      [Object],    [Object]
    ],
    isV8Frames: true
  }
}

which is indeed not an error but a normal object ...

if i dont wrap it in a try catch, testcafe will just fail:

And without the try catch testcafe doesnt find the inline add node button ...

The tests Check the nodetype help in create dialog and Check that nodetype without help has no help button should currently fail due to the same behaviour ...