-
Story
-
Resolution: Fixed
-
Minor
-
None
-
-
1.0-m10, 1.0-m11, 1.0-m12, 1.0-pre-beta-1, 1.0-beta-1
Create a v1 acceptance test for testing the the multibranch flow:
- Create the multibranch job. Will need to have branches.
- Inspect structure of the Branches tab. Use a Nightwatch page-object for this.
- Setup an SSE listener in the test to listen for runs of one of the branches.
- Press the "run" widget on the branch being listened to.
- Use the async SSE events to move the test to a successful "done()".
- Verify that the "Queued" and "Started" Toast components appeared at the right time. This will be tricky hmmm.
[JENKINS-36177] Acceptance test for Multi-Branch flow
| Epic Link | New: JENKINS-36178 [ 172150 ] |
| Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
We'd catch those kinds of regressions if we had these kinda of tests but.
some are really hard to test, that is for sure, and this seems pretty sensible (not saying shouldn't do it, but would be nice to find unit tests that can also cover the same where applicable).
I suspect this is the best place to really test SSE, so we don't have a lot of choice.
This is well worth doing
| Priority | Original: Major [ 3 ] | New: Critical [ 2 ] |
With this, I would like to have acceptance test run as part of the main build, I think it may be worth it.
| Status | Original: In Progress [ 3 ] | New: Open [ 1 ] |
| Description |
Original:
Create a v1 acceptance test for testing the the multibranch flow: # Create the multibranch job. Will need to have branches. # Inspect structure of the Branches tab. Use a Nightwatch page-object for this. # Setup an SSE listener in the test to listen for runs of one of the branches. # Press the "run" widget on the branch being listened to. # Use the async SSE events to move the test to a successful "done()". |
New:
Create a v1 acceptance test for testing the the multibranch flow: # Create the multibranch job. Will need to have branches. # Inspect structure of the Branches tab. Use a Nightwatch page-object for this. # Setup an SSE listener in the test to listen for runs of one of the branches. # Press the "run" widget on the branch being listened to. # Use the async SSE events to move the test to a successful "done()". # Verify that the "Queued" and "Started" Toast components appeared at the right time. This will be tricky hmmm. |
These are all good things, but there have been some pretty major regressions that it would be nice to catch with a regular test suite rather than rely on this (eg around SSE)