Issue 128505 - flaky tests in the automated test suites
Summary: flaky tests in the automated test suites
Status: ACCEPTED
Alias: None
Product: QA
Classification: Unclassified
Component: testscripts (show other issues)
Version: 4.2.0-dev
Hardware: All All
: P5 (lowest) Minor
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact: Carl Marcum
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-03-27 17:11 UTC by Carl Marcum
Modified: 2022-03-27 17:13 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description Carl Marcum 2022-03-27 17:11:41 UTC 
This issue is to capture work on flaky automated tests.

When running the BVT and FVT tests there are still some that tests that intermittently fail on some runs and not others. I believe this is generally due to the faster processor speeds available now and usually can be fixed by identifying where a thread sleep can be effective in allowing the test time to catch up.
Some examples are getting the value of a text field of a property in an assertion and it's evaluated before the value is completely retrieved. This can be fixed by getting the value first and then using it in the assertion.
Other times focus is requested on a field and then the data is removed with ctrl-a followed by delete but not all the data was selected in time and some was left behind before typing in new data and similar scenarios.