TASK: More isolated e2e tests (on their own page) #3543
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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 lineclick(Selector('.neos-contentcollection'))
was failing.neos-ui/Tests/IntegrationTests/Fixtures/1Dimension/createNewNodes.e2e.js
Lines 159 to 169 in 7ea5dd7
After putting it in a try catch, it logged
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
andCheck that nodetype without help has no help button
should currently fail due to the same behaviour ...