Details
-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
None
Description
Context
Issues appear e.g. on
- #setTextField -> leads to validation error (see Detail example of a failure below)
- #save -> leads to an issue - if the form has not yet disappeared as expected.Â
Â
Detail example of a failure
IÂ (Maxime) was testing upgrading Docker when I ran into this failing test. It looks like the test algorithm is not accounting for all the internal dialog mechanics. When slowed down, what happens is the following:
- dialog opens
- field is cleared
- 'Save changes' button is clicked
- validation error happens
- new name is typed into the field (too late)
Which obviously leads to a failed test.
Â
Acceptance criteria
- Usage of form field setter methods work reliable.
- Have test methods on FormTest with repetitions (via JUnit).
- If possible - use VaadinWebDriverWrapper to ensure async communication with the server is finished.
Developper notes
A 1st PR was using Selenium to check whether "things are done"
- whether a field has the expected value after setting it.
- whether the form disappeared
But that seems too explicit. Instead we should rather check whether async communication to server is done.
Â
Checklists
Acceptance criteria
Attachments
Issue Links
- is related to
-
MGNLTEST-178 Sporadic test failures on Form#setCodeFieldValue
-
- Closed
-
- relates to
-
MGNLTEST-89 pageobjects.Form#openTab does not work in security app
-
- Closed
-
- mentioned in
-
Page Loading...