Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-33730

ATH needs to be made to work with 2.0

XMLWordPrintable

      Acceptance test harness needs to be checked whether it works with the 2.0 targeting changes, and if not, needs to be adapted to work with the 2.0 changes.

          [JENKINS-33730] ATH needs to be made to work with 2.0

          Daniel Beck created issue -

          Spike Washburn added a comment -

          Daniel expects problems need to be addressed during the beta period if possible.

          Spike Washburn added a comment - Daniel expects problems need to be addressed during the beta period if possible.
          Daniel Beck made changes -
          Priority Original: Critical [ 2 ] New: Blocker [ 1 ]
          Daniel Beck made changes -
          Assignee Original: Oliver Gondža [ olivergondza ]
          Daniel Beck made changes -
          Epic Link New: JENKINS-33810 [ 169285 ]
          Daniel Beck made changes -
          Rank New: Ranked higher

          Spike Washburn added a comment -

          Root cause of this: the UI was changed, and broke many of the ATH tests. [Guess] Selenium uses page object to describe the page, and many of the tests rely on ID that have changed.

          [Suggest Tom or Keith fix up the tests]

          Spike Washburn added a comment - Root cause of this: the UI was changed, and broke many of the ATH tests. [Guess] Selenium uses page object to describe the page, and many of the tests rely on ID that have changed. [Suggest Tom or Keith fix up the tests]

          Ulli Hafner added a comment - - edited

          Wouldn't it make sense to run the ATH after each UI change to ensure that nothing has been broken? I would also encourage each developer to add new ATH test cases for each of the new UI features that have been introduced...

          Ulli Hafner added a comment - - edited Wouldn't it make sense to run the ATH after each UI change to ensure that nothing has been broken? I would also encourage each developer to add new ATH test cases for each of the new UI features that have been introduced...
          Spike Washburn made changes -
          Assignee New: Tom FENNELLY [ tfennelly ]

          Daniel Beck added a comment -

          drulli Definitely something we need to improve. ATH is not visible enough. We could make passing ATH in an ATH snapshot/PR a condition for UI changes. Ideally ATH could be run for all pull requests. WDYT?

          For now, I consider this a 2.0 blocker that needs fixing. So from the POV of actual Jenkins releases, we'll still be on time

          Daniel Beck added a comment - drulli Definitely something we need to improve. ATH is not visible enough. We could make passing ATH in an ATH snapshot/PR a condition for UI changes. Ideally ATH could be run for all pull requests. WDYT? For now, I consider this a 2.0 blocker that needs fixing. So from the POV of actual Jenkins releases, we'll still be on time

            tfennelly Tom FENNELLY
            danielbeck Daniel Beck
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: