Nightwatch.js谷歌演示脚本失效，寻求解决方案

I totally get it—Google’s search page structure shifts pretty regularly, which breaks those old demo scripts. Let’s get yours working again with up-to-date element selectors and handling for modern page elements like cookie consent popups.

Updated Working Script #

Here’s a revised version that works with Google’s current page structure (as of 2024):

module.exports = {
  'Demo test Google': function (client) {
    client
      .url('https://www.google.com')
      .waitForElementVisible('body', 1000)
      .assert.titleContains('Google') // More flexible than exact title (accounts for regional suffixes)

      // Handle Google's cookie consent popup (common in many regions)
      .waitForElementVisible('#L2AGLb', 2000) // ID of the "Accept all" button
      .click('#L2AGLb')
      .pause(500) // Give time for the popup to disappear

      // Target the search box using its stable `name` attribute (more reliable than type=text)
      .assert.visible('input[name="q"]')
      .setValue('input[name="q"]', 'rembrandt van rijn')
      .pause(500) // Short pause to ensure input registers

      // Trigger search by pressing Enter (avoids issues with dynamic search button selectors)
      .keys(client.Keys.ENTER)

      // Wait for search results to load and verify content
      .waitForElementVisible('#search', 2000) // Container for search results
      .assert.containsText('#search', 'Rembrandt van Rijn')
      .end();
  }
};

Key Changes & Explanations #

• Cookie Consent Handling: Google now shows a cookie popup in most regions, which can block interactions with the search box if not dismissed. The #L2AGLb selector targets the "Accept all" button (this is consistent for most regions, but if it fails, use DevTools to grab the latest selector).
• Stable Search Box Selector: Instead of input[type=text] (which matches multiple elements now), we use input[name="q"]—this attribute has stayed consistent for years and uniquely targets the main search box.
• Flexible Title Check: Using titleContains instead of exact title matches accounts for regional variations (like "Google.co.uk" instead of "Google").
• Enter Key for Search: Clicking the search button can be flaky if Google changes its selector, so pressing Enter is more reliable.

Debug Tips for Future Changes #

If Google updates the page again, use these steps to fix selectors quickly:

• Add .debug() to your script where it fails—this pauses execution so you can inspect the page.
• Open Chrome DevTools (F12) and use the element picker to find the latest selector/XPath for the element you need.
• Prefer attributes like name, id, or unique data-* attributes over generic types or classes, as they’re less likely to change.

内容的提问来源于stack exchange，提问作者bacizone