"before all" hook: Create test site for "buildNodeUrl should build a valid URL"
  ❌ Validate the concepts of the tutorial: 2 - Making a Hero Section "before all" hook: Create test site for "buildNodeUrl should build a valid URL"
	CypressError: `cy.request()` timed out waiting `30000ms` for a response from your server.

a node type can be rendered using different views
  ✅ Validate the concepts of the tutorial: 3 - The "About Us" Page a node type can be rendered using different views
about-us.html: the footer should exist (shared template)
  ✅ Validate the concepts of the tutorial: 3 - The "About Us" Page about-us.html: the footer should exist (shared template)
about-us/our-team.html: the footer should exist (shared template)
  ✅ Validate the concepts of the tutorial: 3 - The "About Us" Page about-us/our-team.html: the footer should exist (shared template)
about-us/our-values.html: the footer should exist (shared template)
  ✅ Validate the concepts of the tutorial: 3 - The "About Us" Page about-us/our-values.html: the footer should exist (shared template)
other-page-single-column.html: the footer should exist (shared template)
  ✅ Validate the concepts of the tutorial: 3 - The "About Us" Page other-page-single-column.html: the footer should exist (shared template)
the footer should not exist on the home page (different template)
  ✅ Validate the concepts of the tutorial: 3 - The "About Us" Page the footer should not exist on the home page (different template)

the blog home page should only list published posts in the right order
  ✅ Validate the concepts of the tutorial: 4 - Making a Blog the blog home page should only list published posts in the right order
each article should be clickable and lead to a valid page
  ✅ Validate the concepts of the tutorial: 4 - Making a Blog each article should be clickable and lead to a valid page

a-second-article.html: the hero section should be present on the blog post
  ✅ Validate the concepts of the tutorial: 5 - View Content in Full Page a-second-article.html: the hero section should be present on the blog post
a-second-article.html: the main article should be displayed
  ✅ Validate the concepts of the tutorial: 5 - View Content in Full Page a-second-article.html: the main article should be displayed
a-second-article.html: the page should have a 'back to blog home' link
  ✅ Validate the concepts of the tutorial: 5 - View Content in Full Page a-second-article.html: the page should have a 'back to blog home' link
welcome-to-hydrogen-blog.html: the hero section should be present on the blog post
  ✅ Validate the concepts of the tutorial: 5 - View Content in Full Page welcome-to-hydrogen-blog.html: the hero section should be present on the blog post
welcome-to-hydrogen-blog.html: the main article should be displayed
  ✅ Validate the concepts of the tutorial: 5 - View Content in Full Page welcome-to-hydrogen-blog.html: the main article should be displayed
welcome-to-hydrogen-blog.html: the page should have a 'back to blog home' link
  ✅ Validate the concepts of the tutorial: 5 - View Content in Full Page welcome-to-hydrogen-blog.html: the page should have a 'back to blog home' link

Create a page with .hbs template
  ✅ Check that components of a module are correctly registered Create a page with .hbs template
Verify nodeTypes and icons are registered
  ✅ Check that components of a module are correctly registered Verify nodeTypes and icons are registered

Ensure Content editor UI extension is correctly registered
  ✅ Check that Javascript module settings (UI extensions, rules, configs) are correctly deployed Ensure Content editor UI extension is correctly registered
Ensure Jahia rule is correctly registered and working
  ✅ Check that Javascript module settings (UI extensions, rules, configs) are correctly deployed Ensure Jahia rule is correctly registered and working
Ensure Jahia URLRewrite rule is correctly registered and working
  ✅ Check that Javascript module settings (UI extensions, rules, configs) are correctly deployed Ensure Jahia URLRewrite rule is correctly registered and working

Check the transformed module headers
  ✅ Check that the Javascript module has been transformed properly and has the proper header values Check the transformed module headers

testAbsoluteArea: Basic Area test
  ✅ Absolute Area test testAbsoluteArea: Basic Area test
testAbsoluteArea: Allowed types area
  ✅ Absolute Area test testAbsoluteArea: Allowed types area
testAbsoluteArea: Number of items area
  ✅ Absolute Area test testAbsoluteArea: Number of items area
testAbsoluteArea: areaView Area
  ✅ Absolute Area test testAbsoluteArea: areaView Area
testAbsoluteArea: absolute Area home page
  ✅ Absolute Area test testAbsoluteArea: absolute Area home page
testAbsoluteArea: absolute Area site root
  ✅ Absolute Area test testAbsoluteArea: absolute Area site root
testAbsoluteArea: absolute Area custom page (sub-level)
  ✅ Absolute Area test testAbsoluteArea: absolute Area custom page (sub-level)
testAbsoluteArea: non editable Area
  ✅ Absolute Area test testAbsoluteArea: non editable Area
testAbsoluteArea: Area type
  ✅ Absolute Area test testAbsoluteArea: Area type
testAbsoluteArea: Limited absolute area editing
  ✅ Absolute Area test testAbsoluteArea: Limited absolute area editing
testAbsoluteArea: should render absolute area with parameters
  ✅ Absolute Area test testAbsoluteArea: should render absolute area with parameters

testAddResources: should not contain a div in the head tag in the page source code
  ✅ Test on add resources component/helper testAddResources: should not contain a div in the head tag in the page source code
testAddResources : should contain a link tag in the head tag to load the CSS styles
  ✅ Test on add resources component/helper testAddResources : should contain a link tag in the head tag to load the CSS styles
testAddResources : should contain a script tag under the body tag
  ✅ Test on add resources component/helper testAddResources : should contain a script tag under the body tag
testAddResources : should contain the test body element created by the body script
  ✅ Test on add resources component/helper testAddResources : should contain the test body element created by the body script
testAddResources : should contain a script tag under the head tag
  ✅ Test on add resources component/helper testAddResources : should contain a script tag under the head tag
testAddResources : should contain the test head element created by the head script
  ✅ Test on add resources component/helper testAddResources : should contain the test head element created by the head script
testAddResources : should contain the test inline script element created by the inline script
  ✅ Test on add resources component/helper testAddResources : should contain the test inline script element created by the inline script

testJArea: Basic Area test
  ✅ Area test testJArea: Basic Area test
testJArea: Allowed types area
  ✅ Area test testJArea: Allowed types area
testJArea: Number of items area
  ✅ Area test testJArea: Number of items area
testJArea: areaView Area
  ✅ Area test testJArea: areaView Area
testJArea: path Area
  ✅ Area test testJArea: path Area
testJArea: non editable Area
  ✅ Area test testJArea: non editable Area
testJArea: Area type
  ✅ Area test testJArea: Area type
testJArea: should render area with parameters
  ✅ Area test testJArea: should render area with parameters

Verify calendar (.jsp content in the template) is correctly bound to the events list
  ✅ Check on bound components Verify calendar (.jsp content in the template) is correctly bound to the events list
Verify that the calendar is correctly refreshed once a new event is added
  ✅ Check on bound components Verify that the calendar is correctly refreshed once a new event is added
Verify that the facets is working correctly
  ✅ Check on bound components Verify that the facets is working correctly
Test boundComponent behavior with area/list creation by edit mode
  ✅ Check on bound components Test boundComponent behavior with area/list creation by edit mode

testConfig: test config in preview
  ✅ Test OSGi configuration in views testConfig: test config in preview
testConfig: test config in edit
  ✅ Test OSGi configuration in views testConfig: test config in edit
testConfig: test config in live guest
  ✅ Test OSGi configuration in views testConfig: test config in live guest
testConfig: test config in live logged
  ✅ Test OSGi configuration in views testConfig: test config in live logged
testConfig: test config in ajax rendered content
  ✅ Test OSGi configuration in views testConfig: test config in ajax rendered content

Verify content template for jnt:event is correctly displayed
  ✅ Content templates resolution testsuite Verify content template for jnt:event is correctly displayed
Verify findDisplayableNode is correctly resolving jnt:event that is using a JS content template
  ✅ Content templates resolution testsuite Verify findDisplayableNode is correctly resolving jnt:event that is using a JS content template
Test default content template is working properly when content doesn't have specific view
  ✅ Content templates resolution testsuite Test default content template is working properly when content doesn't have specific view
Test default content template is working properly when content have specific view
  ✅ Content templates resolution testsuite Test default content template is working properly when content have specific view

testCurrentContent: Check currentContent injected JSON node in current view
  ✅ Test on currentContent injected data testCurrentContent: Check currentContent injected JSON node in current view

Verify all children returned
  ✅ getChildNodes function test Verify all children returned
Verify filtered children returned
  ✅ getChildNodes function test Verify filtered children returned
Verify filtered + offset children returned
  ✅ getChildNodes function test Verify filtered + offset children returned
Verify filtered + limit children returned
  ✅ getChildNodes function test Verify filtered + limit children returned
Verify filtered + limit + offset children returned
  ✅ getChildNodes function test Verify filtered + limit + offset children returned
Verify limited children returned
  ✅ getChildNodes function test Verify limited children returned
Verify limited + offset children returned
  ✅ getChildNodes function test Verify limited + offset children returned
Verify limit is mandatory
  ✅ getChildNodes function test Verify limit is mandatory
Verify offset
  ✅ getChildNodes function test Verify offset
Verify RenderChildren
  ✅ getChildNodes function test Verify RenderChildren
Verify RenderChild
  ✅ getChildNodes function test Verify RenderChild

Verify property values from getNodeProps
  ✅ getNodeProps function test Verify property values from getNodeProps
Verify property values from getNodeProps (multiple)
  ✅ getNodeProps function test Verify property values from getNodeProps (multiple)
Verify property values from getNodeProps (Types and safety)
  ✅ getNodeProps function test Verify property values from getNodeProps (Types and safety)

Test getNodesByJCRQuery, case: all
  ✅ getNodesByJCRQuery function test Test getNodesByJCRQuery, case: all
Test getNodesByJCRQuery, case: limit
  ✅ getNodesByJCRQuery function test Test getNodesByJCRQuery, case: limit
Test getNodesByJCRQuery, case: limitMandatory
  ✅ getNodesByJCRQuery function test Test getNodesByJCRQuery, case: limitMandatory
Test getNodesByJCRQuery, case: offset
  ✅ getNodesByJCRQuery function test Test getNodesByJCRQuery, case: offset
Test getNodesByJCRQuery, case: limitOffset
  ✅ getNodesByJCRQuery function test Test getNodesByJCRQuery, case: limitOffset

Check GQL execution in current view
  ✅ Test GQL Check GQL execution in current view

Should only have the links to the public pages in the initial HTML returned by the server
  ✅ Test hydration of the navigation menu Should only have the links to the public pages in the initial HTML returned by the server
Should have all links available as root after hydration
  ✅ Test hydration of the navigation menu Should have all links available as root after hydration
Should not have restricted links available as guest after hydration
  ✅ Test hydration of the navigation menu Should not have restricted links available as guest after hydration

is polite, says hello and sorts numbers
  ✅ Test OSGi configuration in views is polite, says hello and sorts numbers

testPriorityTemplateExample1: GIVEN multiple templates with different priorities WHEN resolving the template THEN the template with the highest priority (9) is used
  ✅ Test priority parameter on templates testPriorityTemplateExample1: GIVEN multiple templates with different priorities WHEN resolving the template THEN the template with the highest priority (9) is used
testPriorityTemplateExample2: GIVEN multiple templates with different priorities WHEN resolving the template THEN the template with the highest priority (-5) is used
  ✅ Test priority parameter on templates testPriorityTemplateExample2: GIVEN multiple templates with different priorities WHEN resolving the template THEN the template with the highest priority (-5) is used
testPriorityTemplateExample3: GIVEN multiple templates with different priorities WHEN resolving the template THEN the template with the highest priority (50) is used
  ✅ Test priority parameter on templates testPriorityTemplateExample3: GIVEN multiple templates with different priorities WHEN resolving the template THEN the template with the highest priority (50) is used

javascriptExample:testPriorityView1: GIVEN multiple views with different priorities WHEN resolving the view THEN the view with the highest priority (6) is used
  ✅ Test priority parameter on views javascriptExample:testPriorityView1: GIVEN multiple views with different priorities WHEN resolving the view THEN the view with the highest priority (6) is used
javascriptExample:testPriorityView2: GIVEN multiple views with different priorities WHEN resolving the view THEN the view with the highest priority (-3) is used
  ✅ Test priority parameter on views javascriptExample:testPriorityView2: GIVEN multiple views with different priorities WHEN resolving the view THEN the view with the highest priority (-3) is used
javascriptExample:testPriorityView3: GIVEN multiple views with different priorities WHEN resolving the view THEN the view with the highest priority (0) is used
  ✅ Test priority parameter on views javascriptExample:testPriorityView3: GIVEN multiple views with different priorities WHEN resolving the view THEN the view with the highest priority (0) is used
javascriptExample:testPriorityView4: GIVEN multiple views with different priorities WHEN resolving the view THEN the view with the highest priority (13) is used
  ✅ Test priority parameter on views javascriptExample:testPriorityView4: GIVEN multiple views with different priorities WHEN resolving the view THEN the view with the highest priority (13) is used

Verify property values from getNodeProps
  ✅ proxyProps function test Verify property values from getNodeProps

default: Check that components is hydrated correctly
  ✅ Verify client side component are rehydrated as expected default: Check that components is hydrated correctly
live: Check that components is hydrated correctly
  ✅ Verify client side component are rehydrated as expected live: Check that components is hydrated correctly

Check that components are properly registered
  ✅ Verify that registerJahiaComponents behaves as expected Check that components are properly registered

Without parameter, text should be editable
  ✅ Render should be editable Without parameter, text should be editable
With parameter set to false, text should not be editable
  ✅ Render should be editable With parameter set to false, text should not be editable
With parameter set to true, text should be editable
  ✅ Render should be editable With parameter set to true, text should be editable

testRender: should display page composer create button correctly using createContentButtons helper
  ✅ Test on render and createContentButtons helpers testRender: should display page composer create button correctly using createContentButtons helper
testRender: should render jnt:text JSON node
  ✅ Test on render and createContentButtons helpers testRender: should render jnt:text JSON node
testRender: should render jnt:text JSON node in config: OPTION
  ✅ Test on render and createContentButtons helpers testRender: should render jnt:text JSON node in config: OPTION
testRender: should render javascriptExample:test JSON node in config: OPTION with view: sub
  ✅ Test on render and createContentButtons helpers testRender: should render javascriptExample:test JSON node in config: OPTION with view: sub
testRender: should render JSON node with INCLUDE config
  ✅ Test on render and createContentButtons helpers testRender: should render JSON node with INCLUDE config
testRender: should render JSON node with mixin
  ✅ Test on render and createContentButtons helpers testRender: should render JSON node with mixin
testRender: should render JSON node with parameters passed to render
  ✅ Test on render and createContentButtons helpers testRender: should render JSON node with parameters passed to render
testRender: should render node with parameters passed to render
  ✅ Test on render and createContentButtons helpers testRender: should render node with parameters passed to render
testRender: should render existing child node using relative path
  ✅ Test on render and createContentButtons helpers testRender: should render existing child node using relative path

should display the correct order of templates
  ✅ Template Picker Correct Order Test should display the correct order of templates

testTemplate: Verify 3 sections presence
  ✅ Template testsuite testTemplate: Verify 3 sections presence
testTemplate: Check grouping components
  ✅ Template testsuite testTemplate: Check grouping components
testTemplate: Check 3 sections presence in LIVE workspace
  ✅ Template testsuite testTemplate: Check 3 sections presence in LIVE workspace

should display the current user as root
  ✅ Test current user should display the current user as root

should display the permission
  ✅ Test has permission should display the permission

Test I18n values in various workspace/locales and various type of usage SSR/hydrate/rendered client side
  ✅ Test i18n Test I18n values in various workspace/locales and various type of usage SSR/hydrate/rendered client side

should display the node type
  ✅ test isNodeType should display the node type

should display the locale
  ✅ Test locale should display the locale

should display the url parameters
  ✅ Test url parameters should display the url parameters
should display the url parameters with special chars
  ✅ Test url parameters should display the url parameters with special chars

Generated URLs should be correct
  ✅ Test on url helper Generated URLs should be correct
Generated URLs should be correct with vanity
  ✅ Test on url helper Generated URLs should be correct with vanity

testVirtualNode: Check virtual nodes are correctly rendered in preview mode
  ✅ Test virtual nodes testVirtualNode: Check virtual nodes are correctly rendered in preview mode
testVirtualNode: Check virtual nodes are correctly rendered in customized preview mode
  ✅ Test virtual nodes testVirtualNode: Check virtual nodes are correctly rendered in customized preview mode