[Flaky Test] shows a warning if user does not have permission to create navigation menus

[github-actions]

Flaky test detected. This is an auto-generated issue by GitHub Actions. Please do NOT edit this manually.

Test title

shows a warning if user does not have permission to create navigation menus

Test path

specs/editor/blocks/navigation.test.js

Errors

[2021-12-23T05:40:55.695Z] Test passed after 1 failed attempt on docs/36278-gen-theme-ref.
[2022-01-05T14:17:11.192Z] Test passed after 1 failed attempt on trunk.
[2022-01-13T08:15:44.893Z] Test passed after 1 failed attempt on add-context-i18n-light.
[2022-04-04T09:02:24.920Z] Test passed after 2 failed attempts on try/auto-select-first-nav-menu-if-solo.
[2022-07-19T12:01:31.684Z] Test passed after 1 failed attempt on add/author-nicename-template.
[2022-07-20T11:03:06.317Z] Test passed after 1 failed attempt on add/html-tokenizer-2.

[2022-07-26T07:36:35.735Z] Test passed after 1 failed attempt on fix/replace-clickable-divs-with-buttons.

  ● Navigation › Permission based restrictions › shows a warning if user does not have permission to create navigation menus

    expect(jest.fn()).toHaveErrored(expected)

    Expected mock function to be called.

      1336 | 			// * /wp/v2/settings?_locale=user
      1337 | 			// * /wp/v2/templates?context=edit&post_type=post&per_page=100&_locale=user
    > 1338 | 			expect( console ).toHaveErrored();
           | 			                  ^
      1339 | 		} );
      1340 | 	} );
      1341 |

      at Object.<anonymous> (specs/editor/blocks/navigation.test.js:1338:22)
          at runMicrotasks (<anonymous>)

[getdave]

Ok this one appears to be because the user is still logged in as admin at the point of the assertion. This was working at point of merge and now its regressed.

Here's a screenshot from the artifacts

[getdave]

Reopened by my random branch. Closing again as I know why this failed.

[getdave]

This could be because the endpoints no longer 403 for lower perm users:

// Expect a console 403 for requests to:
// * /wp/v2/settings?_locale=user
// * /wp/v2/templates?context=edit&post_type=post&per_page=100&_locale=user
expect( console ).toHaveErrored();

[talldan]

I've personally seen this fail quite regularly with this error:

TimeoutError: waiting for XPath `//*[contains(@class, 'components-snackbar__content')][ text()="You do not have permission to create Navigation Menus." ]` failed: timeout 30000ms exceeded

examples:

• https://github.com/WordPress/gutenberg/runs/7493638539?check_suite_focus=true
• https://github.com/WordPress/gutenberg/runs/7473918273?check_suite_focus=true

The artifact still shows the logged in user as admin (in the top-right corner it should say 'Howdy, contributor!'), so I think that's where the issue lies:

[talldan]

I'm going to skip this test (#42693).

BTW, I had started migrating the nav block tests to playwright a couple of months ago, but haven't had time to finish this effort. I've pushed a draft PR - #42695.

I actually got stuck on migrating the permissions tests because I hadn't been able to figure out a way to log in as a different user in playwright tests.

[github-actions]

This issue has gone 30 days without any activity.