Uploaded image for project: 'A/B Testing'
  1. A/B Testing
  2. ABTEST-403

Remove the custom page objects once the proper functionality exists in the testing framework

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Minor Minor
    • None
    • None
    • None

      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.

        Acceptance criteria

              Unassigned Unassigned
              aichimescu Andrei Ichimescu
              AuthorX
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: