-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[UI] Add synchronous start/stop pipeline error notifications #133
Conversation
UI test coverage: 69.89% 🚨 Decreased by -0.21% (was 70.1%) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This reads great! I have one more question left with regards to the stopPipeline
action, but otherwise this should be good to go! ✨
9aaeac5
to
ff4dc5d
Compare
UI test coverage: 70.61% 🎉 Increased by +0.51% (was 70.1%) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This reads great and nice test coverage! ✨
async stopPipeline(pipeline) { | ||
await pipeline.stopPipeline(); | ||
try { | ||
await pipeline.stopPipeline(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice! ✨
await click(page.pipelineStatusStop); | ||
}); | ||
|
||
test('it displays an error notification', function (assert) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice testing addition! ✨
ff4dc5d
to
de3f4b5
Compare
UI test coverage: 70.61% 🎉 Increased by +0.51% (was 70.1%) |
Description
We wrote an error system around handling asynchronous pipeline errors, but it doesnt handle synchronous pipeline errors 😅
This PR addresses that
Fixes #127
Quick checks: