-
Notifications
You must be signed in to change notification settings - Fork 846
Connection REST API: Unit test for the remote_authorize request.
#16879
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
Conversation
The existing test only verifies the existence of the endpoint, and turned out to be unreliable. The test has been rewritten to actually test the authorization process. Some existing tests were also refactored.
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.
Here are some suggested test cases for this PR.
Connection
- In-place connection with free plan
- In-place connection with paid plan
- In-place connection with product purchase
- Classic connection. Use Safari, or set a constant
JETPACK_SHOULD_NOT_USE_CONNECTION_IFRAMEto true - Disconnect/reconnect connection
- Secondary user connection
- Connection on multisite
If you think that suggestions should be improved please edit the configuration file here. You can also modify/add test-suites to be used in the configuration file.
|
Thank you for the great PR description! When this PR is ready for review, please apply the E2E results is available here (for debugging purposes): https://jetpack-e2e-dashboard.herokuapp.com/pr-16879 Scheduled Jetpack release: September 1, 2020. |
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.
The unit tests pass, so I'm approving! I left comments about a few small improvements that I think we could make to the tests. They're not blockers, though, so merge if you'd like.
Moving the assertions to the end of the tests to ensure that environment cleanup gets performed even if a test fails.
|
Thanks @kbrown9, that's a really good catch. Failing one test did lead to failing other tests too, and you end up not knowing where to look ¯\_(ツ)_/¯ |
kbrown9
left a comment
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!
* master: (23 commits) Premium Blocks: set blocks availability (#16898) Compat Package: Fix method declaration compatibility (#16900) Jetpack Dashboard: More meaningful error notices. (#16883) Connection REST API: Unit test for the `remote_authorize` request. (#16879) use blog token to request jetpack.updateBlog (#16698) Improve Story block media loading (#16663) Simplify error notices for broken connections (#16655) Use new heartbeat package (#16285) wrap-paid-block: remove component. deprecated. (#16895) Social Previews: improve preview description handling (#16889) Stats module use blog token (#16727) Form Block: add a new Consent Field, a new Newsletter setting, and a new newsletter variation (#16808) AAG: Backup card, fall back to VP content in case of /rewind API error. (#16867) Donations: Fix dependencies (#16892) Creative Mail: update option to lowercase (#16861) Premium Blocks: Implement the new design (#16611) Requests to Stats CSV use the blog token (#16716) Update spacing around sharing buttons to avoid no bottom margin below the customize link. (#16811) Jetpack SSO: Cleaning up the `requestNonce` API request. (#16830) Donations: Update plans when currency changes (#16844) ...
…ze` request. (#16879) The existing test only verifies the existence of the endpoint, and turned out to be unreliable. The test has been rewritten to actually test the authorization process. Some existing tests were also refactored.
Rebuilding the connection package unit test
Test_REST_Endpoints::test_remote_authorize().Changes proposed in this Pull Request:
The existing test only verifies the existence of the endpoint, and turned out to be unreliable.
The test has been rewritten to actually test the authorization process. Some existing tests were also refactored.
Does this pull request change what data or activity we track or use?
No.
Testing instructions:
Run unit tests for the
jetpack-connectionpackage.Make sure that all tests pass.
Proposed changelog entry for your changes:
n/a