Implement Nightwatch tests

We also need:

1. Own testing tag EG: '@tags': ['navigation'],
2. Add tests in different themes contexts. Umami / Claro / Olivero / NO_THEME

Like was done https://git.drupalcode.org/project/navigation/-/merge_requests/79/diffs

The nightwatch MR has basic accessibility tests running. It's good to have these running, and this demonstrates that adding Nightwatch doesn't require any major errfor.

The Axe A11y tests already caught a duplicate ID, which is now fixed in that same MR. Given that this already caught an accessibility bug, I think this basic implementation should get in sooner than later so it can surface other accessibility problems as this project evolves.

The NW testing can get more comprehensive than what is currently there if we see the need. I think beginning with something simple like this is helpful as it gets basic A11y checks going and is a starting point for additional NW tests.

Also creating some `dark` testing theme could be useful here.
Like:
body { background-color: black; color: white; }

I wonder if 📌 Toolbar doesn't indicate active menu trail for pages not included in Toolbar Active should be a classic test or a Nightwatch one.

finnsky → changed the visibility of the branch nightwatch to hidden.

finnsky → changed the visibility of the branch 3393400-evaluate-adding-nightwatch to hidden.

Added a11y test and expand/collapse test.

Ally reports now

   ✖ 1) Tests/a11y

   – Accessibility - Navigation Module - Claro page (10.3s)

   → ✖ NightwatchAssertError
   aXe rule: button-name - Buttons must have discernible text
        In element: .toolbar-button--icon--sidebar-toggle
   → ✖ NightwatchAssertError
   aXe rule: link-name - Links must have discernible text
        In element: .toolbar-button--icon--system-themes-page
   → ✖ NightwatchAssertError
   aXe rule: link-name - Links must have discernible text
        In element: .toolbar-button--icon--system-modules-list
   → ✖ NightwatchAssertError
   aXe rule: link-name - Links must have discernible text
        In element: .toolbar-button--icon--entity-user-collection

   – Accessibility - Navigation Module - HomePage (6.613s)

   → ✖ NightwatchAssertError
   aXe rule: button-name - Buttons must have discernible text
        In element: .toolbar-button--icon--sidebar-toggle
   → ✖ NightwatchAssertError
   aXe rule: heading-order - Heading levels should only increase by one
        In element: .label
   → ✖ NightwatchAssertError
   aXe rule: landmark-unique - Ensures landmarks are unique
        In element: #admin-toolbar
   → ✖ NightwatchAssertError
   aXe rule: link-name - Links must have discernible text
        In element: .toolbar-button--icon--system-themes-page
   → ✖ NightwatchAssertError
   aXe rule: link-name - Links must have discernible text
        In element: .toolbar-button--icon--system-modules-list
   → ✖ NightwatchAssertError
   aXe rule: link-name - Links must have discernible text
        In element: .toolbar-button--icon--entity-user-collection
   → ✖ NightwatchAssertError
   aXe rule: region - All page content should be contained by landmarks
        In element: #primary-tabs-title

We need to add tooltip tests and mobile. basically will be fine

hello all!
I have small misunderstanding.
We want to add Nightwatch testing. But i don’t really want to reproduce all Drupal Nightwatch infrastructure in module. Currently I’m running tests from core dir like yarn run test:nightwatch --tag navigation
But it will be useless in Navigation module CI.

So idk. I’ll continue in same approach. Probably we need to move Drupal Nightwatch functions into npm package. So it can be useful for modules/themes CI

Idk seems CI runned somehow. Need to check its context.

Ideas on things that we could test:

• Collapse/expand the sidebar
• Scroll the sidebar (if the “content” is higher than the viewport height + footer)
• Open/Close the drawer on hover (submenu level 2)
  • Test it with edge cases, like moving fast to the top of the drawer - so the mouse leaves the targeted hover item
• Navigate to submenu level 3 (accordion)
• Navigate to User menu links
• See labels/tooltips of the 1st level links
• Active menu item on 1st, 2nd and 3rd level items
• (If logo) it takes you to the homepage
• Active item shows as so in the Toolbar

We've discussed this on several occasions and we've agreed on the need to implement these tests. So changing this from "evaluate" to "implement".

Started working on the tests, copied over @bnjmnm test https://git.drupalcode.org/project/drupal/-/merge_requests/7980

Experimental modules can't be installed using the install module command. since it won't be experimental for long, I just used a test setup script

We have a problem here. The scroll wrapper, .admin-toolbar__scroll-wrapper, causes WebDriver to think any elements within it are not visible for interaction. Oddly enough waitForElementVisible passes. Probably because the latter is inspecting the DOM and not interacting with it.

When I made these changes, the tests passed:

.admin-toolbar__scroll-wrapper {
  /*display: flex;*/
  /*overflow-x: hidden;*/
  /*overflow-y: auto;*/
  flex-direction: column;
...
}

@media (min-width: 64rem) {
  .admin-toolbar__scroll-wrapper {
    /*display: contents;*/
    /*background: none;*/
  }
}

I also needed to fix the footer's z-index in 🐛 Fix z-index Needs review . Once the wrapper adjustments were made, the footer was hidden behind the navigation.

Okay, I worked backward and added back styles. It is the display: contents

@media (min-width: 64rem) {
  .admin-toolbar__scroll-wrapper {
    display: contents;

Buttons are not accessible with display: contents applied. See issues for Chromium, Firefox, and WebKit

I guess this is blocked on 🐛 Buttons are not accessible with display: contents applied Active , then.

mglaman → changed the visibility of the branch 3393400-nightwatch-tests to hidden.

The test is green, but:

- cherry-pick fix from 🐛 Buttons are not accessible with display: contents applied Active
- reverts 🐛 Fix z-index Needs review

Also pushed the axe test. It is failing. I think we should:

- Merge 🐛 Buttons are not accessible with display: contents applied Active to apply fix
- Follow @ckrina idea of making this a meta issue
- Commit the test site install script and expandCollapseTest.js (this issue or new child?)
- Make the child issues from #14 including a11y test

I've added special tag for module for :

`yarn test:nightwatch --tag navigation`

I've removed initial titles.
Now they are not defined.
Only block level titles we have now.

Backender review required here.

Test passed now.

I think we can merge it and create META for other tests.

The Needs Review Queue Bot → tested this issue. It no longer applies to Drupal core. Therefore, this issue status is now "Needs work".

This does not mean that the patch necessarily needs to be re-rolled or the MR rebased. Read the Issue Summary, the issue tags and the latest discussion here to determine what needs to be done.

Consult the Drupal Contributor Guide → to find step-by-step guides for working with issues.

css fix in 🐛 Buttons are not accessible with display: contents applied Active committed

Left a comment on MR. Should be small fix.

We just defined an strategy to keep titles for the menus and avoid the problems with cache.

Updated the merge request to address the <h4> issue. See MR comment for details.

Added comment suggesting a different approach to set the <h4> title using the original logic we had in place.
Let's decide the preferred approach and wrap this one!