-
Task
-
Resolution: Fixed
-
Major
-
-
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):
- Basic favoriting (using Freestyle)
- Ensure freestyle job already exists, exists in subfolder, has been run once
- Navigate to Dashboard
- Click "Favorite" star in pipeline list
- Assert card is added and data is correct
- Click on card's name link
- Assert navigation to Activity tab succeeds
- Assert favorite star is "active"
- Return to Dashboard
- Click anywhere else on card
- Assert navigation to Run Details succeeds
- Favoriting / unfavorite (using Pipeline)
- Ensure pipeline job already exists, exists in subfolder, has been run once
- Navigate to Dashboard
- Click "Favorite" star in pipeline list
- Assert card is added and data is correct
- Click "Favorite" start in dashboard card
- Assert card is removed
- Multibranch
- Ensure multibranch job already exists, has two branches (one w/ gitflow style name), each run once
- Navigate to Dashboard
- Click "Favorite" star next to job
- Assert card is added and data is correct (master branch favorited)
- Click on card's name link
- Assert navigation to Activity tab succeeds
- Assert favorite star is "active"
- Click on Branches tab
- Assert "master" branch has active favorite star
- Click favorite start next to gitflow branch
- Navigate to Dashboard
- Assert card is added and data is correct (for gitflow branch)
- Testing actions
- Ensure multibranch job already exists, has two branches (one w/ gitflow style name), each run once
- Navigate to Dashboard
- Click "Favorite" star next to job
- Assert card is added and data is correct (master branch favorited)
- Click "Run" button
- Assert card shows "running" state
- Click "Stop" button
- Assert card shows "aborted" state
- 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)
- blocks
-
JENKINS-46974 Remove redux from personalization
-
- Resolved
-
- is blocked by
-
JENKINS-42354 ATH must support users and run logged in where needed
-
- Closed
-
- is duplicated by
-
JENKINS-43837 Automate testing of favouriting a pipeline
-
- Resolved
-
- relates to
-
JENKINS-47556 Port highly problematic Nightwatch.js tests to Java Selenium
-
- Open
-
- links to
(3 links to)
jamesdumay three requests:
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.