-
Improvement
-
Resolution: Unresolved
-
Minor
-
None
-
None
-
None
-
-
Empty show more show less
In order to have our tests working, in ABTEST-331 we implemented some custom objects. This way the functionality that did not work as expected from the testing-framework can be avoided.
Things that were missing in the testing-framework (at the moment of writing)
Xpath selectors for clicking the row in a grid try to click on rows in findbar results
Xpath selector for clicking an action button in a dialog (form) is not working.
Generally speaking the selectors are too generic, or they only work on certain scenarios
Suggested solution:
Have Ids in the UI components and use the "selectById" in Selenium
Mika mentioned that either of MGNLTEST-131, MGNLTEST-115 could address this problem.
Goal
Replace the custom page objects (implemented in ABTEST-331) with a general purpose solution from the test framework. Such a solution could become available with MGNLTEST-131 or MGNLTEST-115. Check once these tickets are resolved or help by contributing PRs. File more tickets against the test framework if needed and contribute PRs where necessary.
- relates to
-
ABTEST-331 Check and enable ui tests
- Closed
-
MGNLTEST-115 Make test-framework case-insensitive
- Selected
-
MGNLTEST-131 Align Form PO button lookup by icon vs. by text
- Selected