-
-
Notifications
You must be signed in to change notification settings - Fork 210
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
Make the PhishingController test
synchronous
#929
Conversation
73a99a9
to
431505b
Compare
431505b
to
1be25dd
Compare
Should we add a test that simulates the issue we just ran into to enforce/demonstrate the broken up pattern - that is to say separating out calls to update the lists and run the check? Or otherwise add comments somewhere about why we want to keep |
Oh, good point. This is incomplete. |
ffb5b9d
to
ab19822
Compare
test
synchronous againtest
synchronous
ab19822
to
b30177f
Compare
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.
With #930 on the docket as well, this LGTM
This PR is now based on #930 , so we'll need to merge that one first. It ended up being easier to reverse the order, |
b06052b
to
facb31f
Compare
The `test` method for the PhishingController was recently made asynchronous so that it could update the phishing configuration if necessary. We found that in practice this was difficult to use, especially when handling multiple simultanous tests. The `test` method has been made synchronous again. Instead we can check whether the config is out of date using the new `isOutOfDate` method, and explicitly update the configuration if required.
facb31f
to
b6595dd
Compare
This should be ready to review now. Additional tests have been added to |
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.
LGTM, just a couple non-blocking questions/comments
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.
LGTM!
The `test` method for the PhishingController was recently made asynchronous so that it could update the phishing configuration if necessary. We found that in practice this was difficult to use, especially when handling multiple simultanous tests. The `test` method has been made synchronous again. Instead we can check whether the config is out of date using the new `isOutOfDate` method, and explicitly update the configuration if required.
The `test` method for the PhishingController was recently made asynchronous so that it could update the phishing configuration if necessary. We found that in practice this was difficult to use, especially when handling multiple simultanous tests. The `test` method has been made synchronous again. Instead we can check whether the config is out of date using the new `isOutOfDate` method, and explicitly update the configuration if required.
The `test` method for the PhishingController was recently made asynchronous so that it could update the phishing configuration if necessary. We found that in practice this was difficult to use, especially when handling multiple simultanous tests. The `test` method has been made synchronous again. Instead we can check whether the config is out of date using the new `isOutOfDate` method, and explicitly update the configuration if required.
The
test
method for the PhishingController was recently made asynchronous so that it could update the phishing configuration if necessary. We found that in practice this was difficult to use, especially when handling multiple simultaneous tests.The
test
method has been made synchronous again. Instead we can check whether the config is out of date using the newisOutOfDate
method, and explicitly update the configuration if required.BREAKING:
test
method is now synchronous again.ADDED:
isOutOfDate
method for checking whether the current configuration is outdatedChecklist