Open dgr opened 2 weeks ago
Just happened again with Edge. Different error. First time happened at the beginning of the string. This time an extra "g" was inserted in the middle.
=== test-input [jvm][edge]
.... fill multiple inputs
.... fill human multiple inputs
.... fill multiple vars
.... fill active
.... fill active human
FAIL in (test-input) (api_test.clj:250)
fill active human
expected: (str/ends-with? (e/get-url *driver*) "?login=MyLogin2&password=MyPassword2&message=Some+text+2")
actual: (not (str/ends-with? "http://localhost:49382/test.html?login=MyLoggin2&password=MyPassword2&message=Some+text+2" "?login=MyLogin2&password=MyPassword2&message=Some+text+2"))
Version This was a private development branch, but the most recent common parent is 602e0ecb47a189e3e08a9d796034fed6ed6a575d.
Platform
bb tools-versions
reports:Symptom
Failure of a test. Browser was Edge. Rerunning the text resulted in success. You can see that the failure is the difference between "MyLogin" (expected) for the "login" field, versus "mMyLogin" (actual). This suggests that the field is not getting cleared properly. This might be a timing thing with Edge, or possibly a bug in the way that
fill-human-el
does the underlying filling of the text field.Reproduction Difficult to reproduce. Monitor and see if it happens again, either with Edge (might suggest an issue with Edge timing that would require some browser-specific delays in the test suite for Edge, similar to what is done for Safari today) or another browser (would suggest a more subtle bug in
fill-human-el
, possibly with the semi-random "mistakes").Actual behavior Does not fill in the field correctly and that it caught by the test suite.
Expected behavior Should fill in the field correctly.
Diagnosis Nope. Could not reproduce on subsequent runs.
Action Will monitor for now and report if it happens again.