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

End to end test acceptance tests for personalization

    Details

    • Similar Issues:
    • Sprint:
      1.0-beta-1, pacific, atlantic, 1.0-b05/b-06, Blue Ocean - 1.1-beta-1, Blue Ocean - 1.1-beta2, Blue Ocean 1.1-beta4, Blue Ocean 1.1, Blue Ocean 1.1, Blue Ocean 1.2-beta1, Blue Ocean 1.2-beta2, Blue Ocean 1.2-beta3, Blue Ocean 1.2-beta4, Blue Ocean 1.2, Blue Ocean 1.3, Blue Ocean 1.4 - beta 3, Blue Ocean 1.4 - beta 2

      Description

      Scenarios for favouring (suggested): 

      1. Basic favoriting (using Freestyle)
        • Ensure freestyle job already exists, exists in subfolder, has been run once
        1. Navigate to Dashboard
        2. Click "Favorite" star in pipeline list
          • Assert card is added and data is correct
        3. Click on card's name link
          • Assert navigation to Activity tab succeeds
          • Assert favorite star is "active"
        4. Return to Dashboard
        5. Click anywhere else on card
          • Assert navigation to Run Details succeeds
      2. Favoriting / unfavorite (using Pipeline)
        • Ensure pipeline job already exists, exists in subfolder, has been run once
        1. Navigate to Dashboard
        2. Click "Favorite" star in pipeline list
          • Assert card is added and data is correct
        3. Click "Favorite" start in dashboard card
          • Assert card is removed
      3. Multibranch
        • Ensure multibranch job already exists, has two branches (one w/ gitflow style name), each run once
        1. Navigate to Dashboard
        2. Click "Favorite" star next to job
          • Assert card is added and data is correct (master branch favorited)
        3. Click on card's name link
          • Assert navigation to Activity tab succeeds
          • Assert favorite star is "active"
        4. Click on Branches tab
          • Assert "master" branch has active favorite star
        5. Click favorite start next to gitflow branch
        6. Navigate to Dashboard
          • Assert card is added and data is correct (for gitflow branch)
      4. Testing actions
        • Ensure multibranch job already exists, has two branches (one w/ gitflow style name), each run once
        1. Navigate to Dashboard
        2. Click "Favorite" star next to job
          • Assert card is added and data is correct (master branch favorited)
        3. Click "Run" button
          • Assert card shows "running" state
        4. Click "Stop" button
          • Assert card shows "aborted" state
        5. Click "Replay" button (need to verify this is applicable in this scenario)
          • Assert card shows "running" state
          • Assert card shows "success" state (once run finishes)

        Attachments

          Issue Links

            Activity

            Hide
            cliffmeyers Cliff Meyers added a comment -

            James Dumay three requests:

            1. Could we reduce the scope of this ticket to cover just ATH for favorites / personalization?
            2. Could we create a separate ticket to cover the rewrite of flaky nightwatch tests to Java selenium?
            3. Could we then assign this ticket to me?

            I've marked this ticket as a blocker for JENKINS-46974 (port favorites from redux to mobx) which I'd like to get to at some point in the next month or so. Makes sense for me to add some tests for favorites, land them to master, then refactor redux out of personalization with the safety net of good ATH coverage.

            Show
            cliffmeyers Cliff Meyers added a comment - James Dumay three requests: Could we reduce the scope of this ticket to cover just ATH for favorites / personalization? Could we create a separate ticket to cover the rewrite of flaky nightwatch tests to Java selenium? Could we then assign this ticket to me? I've marked this ticket as a blocker for JENKINS-46974 (port favorites from redux to mobx) which I'd like to get to at some point in the next month or so. Makes sense for me to add some tests for favorites, land them to master, then refactor redux out of personalization with the safety net of good ATH coverage.
            Hide
            jamesdumay James Dumay added a comment -

            Cliff Meyers thats fine by me. Can you split and assign the ticket as you see fit?

            Show
            jamesdumay James Dumay added a comment - Cliff Meyers thats fine by me. Can you split and assign the ticket as you see fit?
            Hide
            cliffmeyers Cliff Meyers added a comment -

            Split off JENKINS-47556 to cover Nightwatch.js porting.

            Show
            cliffmeyers Cliff Meyers added a comment - Split off JENKINS-47556 to cover Nightwatch.js porting.
            Hide
            cliffmeyers Cliff Meyers added a comment -

            Since JENKINS-46974 is in current sprint and this ticket blocks it, I am pulling this one in too. If this is undesirable feel free to pull both out to future sprint or backlog. I don't plan to work this immediately but perhaps late this week or sometime next.

            Show
            cliffmeyers Cliff Meyers added a comment - Since JENKINS-46974 is in current sprint and this ticket blocks it, I am pulling this one in too. If this is undesirable feel free to pull both out to future sprint or backlog. I don't plan to work this immediately but perhaps late this week or sometime next.
            Hide
            cliffmeyers Cliff Meyers added a comment - - edited

            The structure of the final ATH is a bit different than described in the ticket. It follows this general pattern:

            • Adding / removing favorites via the Dashboard list of pipelines (freestyle, classic pipeline, multibranch)
            • Checking navigation to other important screens via cards (activity, run details) and activity tab state (for all three types)... and the branches tab (for multibranch)
            • Testing run, replay and remove favorite buttons on the card (all three types)
            Show
            cliffmeyers Cliff Meyers added a comment - - edited The structure of the final ATH is a bit different than described in the ticket. It follows this general pattern: Adding / removing favorites via the Dashboard list of pipelines (freestyle, classic pipeline, multibranch) Checking navigation to other important screens via cards (activity, run details) and activity tab state (for all three types)... and the branches tab (for multibranch) Testing run, replay and remove favorite buttons on the card (all three types)

              People

              • Assignee:
                cliffmeyers Cliff Meyers
                Reporter:
                jamesdumay James Dumay
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: