Update RRM SettingsEdit to handle missing ID error. #10222
Conversation
|
Build files for 51daf92 are ready:
|
There was a problem hiding this comment.
Thanks @juniovitorino, this is looking good, but could use a couple of tweaks. Please see my comments.
Additionally, it would be good to provide a bit more detail to the QA Brief - specifically, how we can reproduce the error in E2E testing. Please feel free to drop me a line if you could use some help with this.
assets/js/modules/reader-revenue-manager/components/settings/SettingsEdit.js
Outdated
Show resolved
Hide resolved
assets/js/modules/reader-revenue-manager/components/settings/SettingsEdit.stories.js
Outdated
Show resolved
Hide resolved
assets/js/modules/reader-revenue-manager/components/settings/SettingsEdit.js
Outdated
Show resolved
Hide resolved
assets/js/modules/reader-revenue-manager/components/settings/SettingsEdit.js
Outdated
Show resolved
Hide resolved
@techanvil I chose to go with your recommendations; they all seemed reasonable to me. Since you know the codebase much better than I do, I’ll learn from your suggestions. Also, could you share an example of a QA Brief to give me a better idea of how to write one? |
…ettingsEdit.js Co-authored-by: Tom Rees-Herdman <[email protected]>
…ettingsEdit.stories.js Co-authored-by: Tom Rees-Herdman <[email protected]>
…ettingsEdit.js Co-authored-by: Tom Rees-Herdman <[email protected]>
…ettingsEdit.js Co-authored-by: Tom Rees-Herdman <[email protected]>
juniovitorino
force-pushed
the
enhancement/10131-handle-error-if-the-saved-product-id-is-no-longer-available
branch
from
8a1a319 to
1277172
Compare
assets/js/modules/reader-revenue-manager/components/settings/SettingsEdit.js
Outdated
Show resolved
Hide resolved
assets/js/modules/reader-revenue-manager/components/settings/SettingsEdit.stories.js
Outdated
Show resolved
Hide resolved
assets/js/modules/reader-revenue-manager/components/settings/SettingsEdit.stories.js
Outdated
Show resolved
Hide resolved
Thanks @juniovitorino! I've left a couple of additional comments, as you've probably noticed. For example QA Briefs, pretty much all issues which have progressed to Code Review and beyond should have one, so you can browse issues in GitHub/ZenHub to get a broad range of examples to help understand how we write them. For a more focused set of examples I'd suggest browsing issues in the RRM Phase 2 epic. And, the most relevant issues to this one are #10065, #9952 and #9954. In fact, #10065 is the issue which actually integrates the ability for the user to set the However we are often in similar situations, so we can use JS snippets to help model scenarios to short-circuit the testing process. In this particular case, I would suggest that the QAB should take the following approach:
googlesitekit.data.select('modules/reader-revenue-manager').getProductIDs();
googlesitekit.data.dispatch('modules/reader-revenue-manager').setProductID( /* Use a product ID from the actual list output from the command above */ "CAownIG4DA:basic-product-id");
googlesitekit.data.dispatch('modules/reader-revenue-manager').saveSettings();
googlesitekit.data.dispatch('modules/reader-revenue-manager').setProductID( /* Use a product ID that doesn't exist in the list output above */ "CAownIG4DA:some-non-existent-product-id");
googlesitekit.data.dispatch('modules/reader-revenue-manager').saveSettings();
It would of course be preferable to test this in a fully integrated manner, which would involve the user setting the I hope that helps, please let me know if you have any further questions. I'm not sure how much exposure you've had to creating publications in the Publisher Center, if you've not done this yet the RRM Phase 1 bug bash instructions has got some useful info on it, although it doesn't get into setting the product IDs which is what Phase 2 tackles. You can add product IDs to a paywall or contribution CTA at the point of creating the subscription plan or contribution amounts. Again, please drop me a line if you want to discuss any of this further, I'd be happy to jump on a call if that would help. |
|
Size Change: +111 B (+0.01%) Total Size: 2.02 MB
ℹ️ View Unchanged
|
There was a problem hiding this comment.
Hey @juniovitorino, please note the VRT suite is currently failing in CI for this PR.
In fact so is the E2E suite, but these are known flaky test failures so you don't need to worry about them for this PR.
You can see which tests are currently known to be flaky by searching for "flaky" in ZenHub for example:
Back to the VRT suite - most of the failures should be fixed by updating the product IDs in the story file as per my other comment.
However, at a minimum you'll need to add the VRT reference images for the new scenario you added for the MissingProductID story.
I don't know if you've seen it yet, but you can download the VRT report for the failing run from the Summary page for the run on GitHub:
Unzip and view the HTML report and you can filter to just show the failed tests.
You'll want to add the new images (or update where relevant, probably not for this PR but in future). You can do this by generating them locally with npm run test:visualtest and then npm run test:visualapprove to copy them into tests/backstop/reference. Or, a shortcut can be to copy relevant images directly from the downloaded report into tests/backstop/reference, that's what I often do.
There's more info on the VRT suite in our documentation, please drop me a line if you've any questions!
There was a problem hiding this comment.
Please update the remaining product IDs in this file :)
The calls to setProductId() need updating, and so does the MissingProductID story.
Summary
Addresses issue:
Relevant technical choices
PR Author Checklist
Do not alter or remove anything below. The following sections will be managed by moderators only.
Code Reviewer Checklist
Merge Reviewer Checklist