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

End to end test acceptance tests for personalization

XMLWordPrintable

    • 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

      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)

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

              Created:
              Updated:
              Resolved: