[QA] Chrome browser test input flakiness

• Previous message: [QA] how to skip an expected fail test in IE, where documented
• Next message: [QA] Chrome browser test input flakiness
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Hey. The Flow browser tests on Chrome have recently gone from fairly stable
to lots of failures.

Many are failing on the login screen with invalid password, but the
password seems legit. Others are failing in tests where if you look at the
Sauce Labs screen captures, input fields have incomplete contents.

For example, <https://saucelabs.com/jobs/fa95acf9c20548d1bc48fddac02f7a90>
types a simple string into an input field
 POST element/0.10030324407853186-1/value
33s (+0.75s)

value: "Reply test0.296384610148551 browsertest edit"

but the screenshot shows "Reply test 0.29" in the input field and then
"384" in the textarea below.  The characters weren't inserted correctly.

So maybe the browser test login failures are actually missing characters.

Any ideas?
-- 
=S Page  Features engineer
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.wikimedia.org/pipermail/qa/attachments/20140807/1efd8a9c/attachment.html>

• Previous message: [QA] how to skip an expected fail test in IE, where documented
• Next message: [QA] Chrome browser test input flakiness
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]