webdriverio/webdriverio

[🐛 Bug]: negated assertions fail in component tests

Open

#14,059 创建于 2025年1月10日

在 GitHub 查看
 (1 评论) (0 反应) (0 负责人)JavaScript (6,029 star) (1,793 fork)batch import
Bug 🐛help wanted

描述

Have you read the Contributing Guidelines on issues?

WebdriverIO Version

latest

Node.js Version

latest

Mode

Standalone Mode

Which capabilities are you using?

n/a

What happened?

When having assertions like:

await expect($('nonExisting')).not.toBeExisting()

it fails with:

[chrome 131.0.6778.265 mac #0-0] Expect $(`div`) not to be existing

Expected [not]: "not existing"
Received      : "existing"
[chrome 131.0.6778.265 mac #0-0] Error: Expect $(`div`) not to be existing
[chrome 131.0.6778.265 mac #0-0]
[chrome 131.0.6778.265 mac #0-0] Expected [not]: "not existing"
[chrome 131.0.6778.265 mac #0-0] Received      : "existing"

even though $('nonExisting').isExisting() correctly returns false.

What is your expected behavior?

The assertion should pass properly.

How to reproduce the bug.

n/a

Relevant log output

n/a

Code of Conduct

  • I agree to follow this project's Code of Conduct

Is there an existing issue for this?

  • I have searched the existing issues

贡献者指南

技术栈
javascripttypescriptnodejs
领域
testing
议题类型
bug
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
2
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
1-3 hours
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
fresh
清晰度议题是否清楚说明期望改动、验收标准和下一步。
clear
前置要求
JavaScriptBasic understanding of test assertions
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
65
研究方向
The bug is in the negated assertion path for `toBeExisting`. Look in the WebdriverIO source code, likely in the `expect` package or element commands, for the implementation of `toBeExisting` matcher. The error message shows the expected/not is reversed, so the issue is probably a simple logic error in how the negated condition is evaluated. Check the matcher's `run` method or the `expect` wrapper that handles `not`.