[ABTEST-403] Remove the custom page objects once the proper functionality exists in the testing framework Created: 19/Jan/21  Updated: 26/Aug/22

Status: Open
Project: A/B Testing
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Minor
Reporter: Andrei Ichimescu Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to ABTEST-331 Check and enable ui tests Closed
relates to MGNLTEST-115 Make test-framework case-insensitive Selected
relates to MGNLTEST-131 Align Form PO button lookup by icon v... Selected
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)
Epic Link: ABn Later
Team: AuthorX

 Description   

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.


Generated at Sun Feb 11 22:55:53 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.