@wdio/nightwatch-devtools 2.0.0 → 2.1.0

package/README.md

@@ -197,6 +197,12 @@ When attached, the per-command Chrome performance-log network capture path is ga
 
 **Set `webSocketUrl: true` even without `bidi: true`.** With it, the plugin registers its page collector at document start on every page, so DOM time-travel stays accurate across navigations. Without it, the collector is injected after each navigation instead, which can miss the first moments of a new page.
 
+## Direct WebDriver reads and remote grids
+
+Some reads the plugin makes go straight to the driver over the WebDriver HTTP transport instead of through Nightwatch's command queue: the page collector's probes and drains, the per-action snapshot probes and screenshots, the screencast's screenshots, and, on a session without BiDi, Chrome's performance log. A command issued through the queue while a test command is running would become part of that command and let its `await` return before it finished, so these reads never join the queue and never cut a test command short.
+
+They use the connection Nightwatch itself is configured with: https when `webdriver.ssl` is set, or when it is unset and the port is 443, and basic authentication from `webdriver.username` and `webdriver.access_key`. A remote grid on https or behind credentials therefore needs no extra configuration for the plugin.
+
 ---
 
 ## Screencast
@@ -335,6 +341,8 @@ Nightwatch does not provide the same depth of framework hooks as WebdriverIO, so
 | Flat suite nesting | Nightwatch does not natively support multiply-nested `describe` blocks; the plugin reports a maximum of two levels. |
 | Delayed result availability | Test results are only finalised in `afterEach`, not available mid-test. |
 | Per-test trace slicing (BDD `describe/it`) | The BDD interface fires the plugin's per-test hook once per module, so `traceGranularity: 'test'` collapses to one session-scoped slice. The exports-object (mocha-style) and Cucumber interfaces get real per-test slicing. See [Per-test slicing](#per-test-slicing--the-bdd-describeit-caveat). |
+| Element waits show no polls | A `waitForElement*` wait is one row with nothing nested under it: Nightwatch polls for the element through its own transport, which the plugin does not see. A `waitUntil` row nests the commands its condition issued. See [Waits](https://webdriver.io/docs/devtools/wdio/trace-mode#waits). |
+| A wait that never ran is a failed row | Nightwatch queues every command up front, so a wait queued behind a failing `assert` never runs. Its row is closed at the end of the test as failed, "did not run", rather than left looking like it passed. |
 | Produce-only trace artifacts | Per-test `screenshot` / `video` files are written to the trace output dir (and the manifest when `emitArtifactsManifest: true`) but not attached inline to Allure — Nightwatch has no live Allure attach API. |
 
 Overall feature parity with the WebdriverIO DevTools service is approximately **80–90%**.

package/dist/{bidi-AZX3WRGJ.js → bidi-C67DYUCA.js}

@@ -1,6 +1,6 @@
 import {
   attachBidiHandlers
-} from "./chunk-TUK7ZLQI.js";
+} from "./chunk-DRZC45YG.js";
 
 // src/bidi.ts
 import logger from "@wdio/logger";
@@ -41,4 +41,4 @@ export {
   attachBidiHandlers2 as attachBidiHandlers,
   buildBidiSinks
 };
-//# sourceMappingURL=bidi-AZX3WRGJ.js.map
+//# sourceMappingURL=bidi-C67DYUCA.js.map