[MGNLTEST-69] Improve support for paginated ComboBox Created: 16/Jul/20 Updated: 09/Nov/23 |
|
| Status: | Selected |
| Project: | Magnolia Test Framework |
| Component/s: | None |
| Affects Version/s: | 1.0 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Low |
| Reporter: | Mikaël Geljić | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
| Date of First Response: | |
| Epic Link: | core-TF-features-bugs-improvements |
| Team: | |
| Work Started: |
| Description |
|
Improve ComboBox/Form PO support for selection with lazy-loading / pagination Could forge sample definition / ad-hoc UI with ComboBox having 100/1000 items. |
| Comments |
| Comment by Christoph Meier [ 22/Jul/20 ] |
|
Related to this, I had to check whether we have a self-test testing to set values on a combobox. We have => FormTest#setComboBoxOption I remember that I was refactoring this test, but that's not yet committed. When I run the re-enabled test (without my changes), it fails in ~50% of the attempts. When I run the refactored version of FormTest#setComboBoxOption then I get 100% success rate. But the 1st / original version also should not fail. Check this gist to compare the 2 versions of the set combobox value test(s). |