-
Notifications
You must be signed in to change notification settings - Fork 3
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
testing(ui): banner #715
testing(ui): banner #715
Conversation
I've asked QA to test the banners and make sure they all work |
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 looks good to me. Let's get it to QE/QA
Code Climate has analyzed commit 1ea0e37 and detected 0 issues on this pull request. The test coverage on the diff in this pull request is 60.4% (50% is the threshold). This pull request will bring the total coverage in the repository to 54.4% (0.6% change). View more on Code Climate. |
🎉 This PR is included in version 1.5.0-val.74 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Purpose
To prepare the codebase for the eventual forms revamp and lay the ground for best test practices, I'm making the transition easier by removing our reliance on React-centric logic. AlertContext relied on two things: a Provider and React's rules of hooks, both limiting what we can do when it comes to defining banner.
Linked Issues to Close
https://qmacbis.atlassian.net/browse/OY2-29602
Approach
Please read the approach I took in #713 as it's pretty much the same. I've added one more test to
userPrompt
to make sure the button texts match whatever the user passed.