You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This results in the following gauge step: Enter "11:00" into the "From" time field below "Time Window"
Logs
Error: TimeField with label From and below Time Window not found
at findElements (node_modules/taiko/lib/elementSearch.js:263:11)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async waitAndGetActionableElement (node_modules/taiko/lib/actions/pageActionChecks.js:150:43)
at async write (node_modules/taiko/lib/actions/write.js:56:11)
at async module.exports.write (node_modules/taiko/lib/taiko.js:1064:16)
at async module.exports.<computed> (node_modules/taiko/lib/taiko.js:2619:14)
at async Object.<anonymous> (tests/step_implementation.js:143:5
Note the additional space after "From" in the error output. I tried remove whitespace from the variable which did not help. I suspect that it tries to find "From " and fails.
Expected behavior
It should locate the field and input the supplied time.
Screenshots
Versions:
It runs in a gitlab pipeline using the offical node:20 Docker image based on debian bookworm.
Describe the bug
It fails to find a TimeField input field.
To Reproduce
await write(time, into(timeField(name.trim(), below(title))));
This results in the following gauge step:
Enter "11:00" into the "From" time field below "Time Window"
Logs
Note the additional space after "From" in the error output. I tried remove whitespace from the variable which did not help. I suspect that it tries to find "From " and fails.
Expected behavior
It should locate the field and input the supplied time.
Screenshots
Versions:
It runs in a gitlab pipeline using the offical
node:20
Docker image based on debian bookworm.Additional context
It works fine locally on macOS:
taiko:
Version: 1.4.1 (Chromium: 128.0.6597.0) RELEASE
Node
v20.16.0
gauge
The text was updated successfully, but these errors were encountered: