-
Notifications
You must be signed in to change notification settings - Fork 211
Unit tests for the banners refactoring #4397
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
base: develop
Are you sure you want to change the base?
Conversation
Co-authored-by: Mayisha <[email protected]>
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.
Things are looking good enough to me, with the exception of using the test IDs.
That said, might it be worth aiming for more integration-y tests that validate we see the expected banners in the main UI, and not just rely on lower-level unit tests? (That work could be tackled in a follow-up PR.)
value: { assign }, | ||
} ); | ||
} ); | ||
it( 'should create error notice when oauth URLs are invalid', () => { |
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.
Can we test that we throw an error when the expected live and test URLs are null separately?
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.
I'm sorry, but I'm not sure if I understand. Do you mean move it to a separate describe
clause?
Base PR #4328
Changes proposed in this Pull Request:
On the base PR I did a considerable refactoring of the promotional banners. I am adding unit tests for all the new JS files here to make the code more reliable.
Testing instructions
Code review. Check if the tests make sense and are still passing.
Changelog entry
Changelog Entry Comment
Comment
Post merge