Do setup before entering editor

test/e2e/specs/site-editor/navigation-editor.spec.js

@@ -20,20 +20,6 @@ test.describe( 'Editing Navigation Menus', () => {
 		editor,
 	} ) => {
 		await test.step( 'Manually browse to focus mode for a Navigation Menu', async () => {
-			// We could Navigate directly to editing the Navigation Menu but we intentionally do not do this.
-			//
-			// Why? To provide coverage for a bug that caused the Navigation Editor behaviours to fail
-			// only when navigating through the editor screens (rather than going directly to the editor by URL).
-			// See: https://github.com/WordPress/gutenberg/pull/56856.
-			//
-			// Example (what we could do):
-			// await admin.visitSiteEditor( {
-			// 	postId: createdMenu?.id,
-			// 	postType: 'wp_navigation',
-			// } );
-			//
-			await admin.visitSiteEditor();
-
 			// create a Navigation Menu called "Test Menu" using the REST API helpers
 			const createdMenu = await requestUtils.createNavigationMenu( {
 				title: 'Primary Menu',
@@ -48,6 +34,20 @@ test.describe( 'Editing Navigation Menus', () => {
 					'<!-- wp:navigation-link {"label":"Another Item","type":"custom","url":"http://www.wordpress.org/","kind":"custom"} /-->',
 			} );
 
+			// We could Navigate directly to editing the Navigation Menu but we intentionally do not do this.
+			//
+			// Why? To provide coverage for a bug that caused the Navigation Editor behaviours to fail
+			// only when navigating through the editor screens (rather than going directly to the editor by URL).
+			// See: https://github.com/WordPress/gutenberg/pull/56856.
+			//
+			// Example (what we could do):
+			// await admin.visitSiteEditor( {
+			// 	postId: createdMenu?.id,
+			// 	postType: 'wp_navigation',
+			// } );
+			//
+			await admin.visitSiteEditor();
+
 			const editorSidebar = page.getByRole( 'region', {
 				name: 'Navigation',
 			} );