如何在Protractor中处理错误/异常？自定义报错通知求助

Hey Vijay, let's work through this together! Getting custom, meaningful error messages instead of Protractor's generic red alerts is totally achievable—let's break down the fixes and common pitfalls that might be stopping your code from working.

The most straightforward way to wrap your Protractor actions in custom error handling is using try/catch with async/await (since almost all Protractor operations are asynchronous). This lets you catch the default error and replace it with your own message.

Here's a reusable function example:

async function safeClick(locator, customMsg) {
  try {
    const targetElement = await element(locator);
    await targetElement.click();
  } catch (originalError) {
    // Throw a new error with your custom message + original context
    throw new Error(`⚠️ Custom Error: ${customMsg} \nOriginal Details: ${originalError.message}`);
  }
}

// Use it like this in your tests
await safeClick(by.css('#checkout-btn'), "Failed to click checkout button—verify element is visible/enabled");

Make sure you're using await for every Protractor call inside the try block—if you skip it, the error won't be caught properly.

If you don't want to write a try/catch for every single action, you can override Protractor's default element methods (like click(), sendKeys()) to add global custom error handling. Add this code in your conf.js or at the top of your test files:

// Save the original element function to avoid infinite loops
const originalElement = element;

element = function(locator) {
  const elem = originalElement(locator);

  // Override the click method
  const originalClick = elem.click;
  elem.click = async function() {
    try {
      await originalClick.call(this);
    } catch (err) {
      throw new Error(`⚠️ Custom Click Error: Could not interact with element [${locator.toString()}] \nOriginal Error: ${err.message}`);
    }
  };

  // Override sendKeys for input fields
  const originalSendKeys = elem.sendKeys;
  elem.sendKeys = async function(...keys) {
    try {
      await originalSendKeys.call(this, ...keys);
    } catch (err) {
      throw new Error(`⚠️ Custom Input Error: Could not send keys to element [${locator.toString()}] \nOriginal Error: ${err.message}`);
    }
  };

  return elem;
};

Now every element().click() or element().sendKeys() call will automatically throw your custom error if it fails.

For Jasmine assertions (like expect()), you can add a custom message directly to the assertion itself—this replaces the default "Expected X to equal Y" text:

const pageTitle = await browser.getTitle();
expect(pageTitle).toEqual("My Dashboard", "⚠️ Custom Assertion Error: Page title doesn't match—page may have navigated incorrectly");

If your existing code isn't triggering custom errors, check these common issues:

• Missing async/await: Protractor operations are promise-based. If you don't await actions inside your try block, the error will slip past the catch clause.
• Swallowing errors: If you're only logging the custom message instead of throwing it, Protractor won't register it as a test failure. Always use throw new Error() to make the failure visible.
• Global error handlers: Some test frameworks or plugins might be catching errors before your code does. Try isolating your test to a single file without extra plugins to debug.

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