Issue 128505

Summary:	flaky tests in the automated test suites
Product:	QA	Reporter:	Carl Marcum <cmarcum>
Component:	testscripts	Assignee:	AOO issues mailing list <issues>
Status:	ACCEPTED ---	QA Contact:	Carl Marcum <cmarcum>
Severity:	Minor
Priority:	P5 (lowest)	CC:	issues
Version:	4.2.0-dev
Target Milestone:	---
Hardware:	All
OS:	All
Issue Type:	DEFECT	Latest Confirmation in:	---
Developer Difficulty:	---

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.