Details
-
Type:
Improvement
-
Status: Closed
-
Priority:
Blocker
-
Resolution: Fixed
-
Affects Version/s: 3.5.12, 3.7.6, 3.8.3, 3.9.1
-
Component/s: Automated functional tests (behat)
-
Labels:
-
Testing Instructions:
-
Affected Branches:MOODLE_35_STABLE, MOODLE_37_STABLE, MOODLE_38_STABLE, MOODLE_39_STABLE
-
Fixed Branches:MOODLE_310_STABLE, MOODLE_35_STABLE, MOODLE_38_STABLE, MOODLE_39_STABLE
-
Pull from Repository:
-
Pull 3.5 Branch:
MDL-69107-35-2 -
Pull 3.5 Diff URL:
-
Pull 3.8 Branch:
MDL-69107-38-2 -
Pull 3.8 Diff URL:
-
Pull 3.9 Branch:
MDL-69107-39-2 -
Pull 3.9 Diff URL:
-
Pull 3.10 Branch:
MDL-69107-310-2 -
Pull 3.10 Diff URL:
-
Pull 3.11 Branch:
MDL-69107-311-2 -
Pull 3.11 Diff URL:
-
Pull Master Branch:
MDL-69107-master-2 -
Pull Master Diff URL:
-
Story Points:0
-
Sprint:Internationals - 3.11 Sprint 1, Internationals - 3.11 Sprint 2, Internationals - 3.11 Sprint 3
Description
Where a autocomplete element is used outside of a Moodle form, it is not always detected as being an autocomplete by the behat field manager.
This means that you instead up with an additional set of steps like:
I press key "13" in the field "foo"
The reason it is not detected as an autocomplete is that the detection comes from the parent div created by the form template.
The autocomplete code can easily add a new data attribute to more readily identify itself as an autocomplete to give a more consistent use.
