Skip to content
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

Fix the RRM SetupMain story and include a VRT scenario. #9082

Merged
merged 5 commits into from
Jul 26, 2024

Conversation

techanvil
Copy link
Collaborator

@techanvil techanvil commented Jul 26, 2024

Summary

Addresses issue:

Relevant technical choices

PR Author Checklist

  • My code is tested and passes existing unit tests.
  • My code has an appropriate set of unit tests which all pass.
  • My code is backward-compatible with WordPress 5.2 and PHP 7.4.
  • My code follows the WordPress coding standards.
  • My code has proper inline documentation.
  • I have added a QA Brief on the issue linked above.
  • I have signed the Contributor License Agreement (see https://cla.developers.google.com/).

Do not alter or remove anything below. The following sections will be managed by moderators only.

Code Reviewer Checklist

  • Run the code.
  • Ensure the acceptance criteria are satisfied.
  • Reassess the implementation with the IB.
  • Ensure no unrelated changes are included.
  • Ensure CI checks pass.
  • Check Storybook where applicable.
  • Ensure there is a QA Brief.

Merge Reviewer Checklist

  • Ensure the PR has the correct target branch.
  • Double-check that the PR is okay to be merged.
  • Ensure the corresponding issue has a ZenHub release assigned.
  • Add a changelog message to the issue.

Copy link

github-actions bot commented Jul 26, 2024

Build files for 5e0d539 have been deleted.

Copy link

github-actions bot commented Jul 26, 2024

Size Change: 0 B

Total Size: 1.67 MB

ℹ️ View Unchanged
Filename Size
./dist/assets/css/googlesitekit-admin-css-********************.min.css 54.8 kB
./dist/assets/css/googlesitekit-adminbar-css-********************.min.css 11 kB
./dist/assets/css/googlesitekit-authorize-application-css-********************.min.css 846 B
./dist/assets/css/googlesitekit-wp-dashboard-css-********************.min.css 7.35 kB
./dist/assets/js/31-********************.js 2.76 kB
./dist/assets/js/32-********************.js 2.25 kB
./dist/assets/js/33-********************.js 3.64 kB
./dist/assets/js/34-********************.js 935 B
./dist/assets/js/35-********************.js 892 B
./dist/assets/js/36-********************.js 3.12 kB
./dist/assets/js/analytics-advanced-tracking-********************.js 901 B
./dist/assets/js/googlesitekit-activation-********************.js 23.7 kB
./dist/assets/js/googlesitekit-ad-blocking-recovery-********************.js 59.7 kB
./dist/assets/js/googlesitekit-adminbar-********************.js 34.5 kB
./dist/assets/js/googlesitekit-api-********************.js 10 kB
./dist/assets/js/googlesitekit-components-gm2-********************.js 5.88 kB
./dist/assets/js/googlesitekit-components-gm3-********************.js 10.1 kB
./dist/assets/js/googlesitekit-consent-mode-********************.js 25.6 kB
./dist/assets/js/googlesitekit-data-********************.js 2.35 kB
./dist/assets/js/googlesitekit-datastore-forms-********************.js 9.03 kB
./dist/assets/js/googlesitekit-datastore-location-********************.js 2.08 kB
./dist/assets/js/googlesitekit-datastore-site-********************.js 20.4 kB
./dist/assets/js/googlesitekit-datastore-ui-********************.js 9.98 kB
./dist/assets/js/googlesitekit-datastore-user-********************.js 25.1 kB
./dist/assets/js/googlesitekit-entity-dashboard-********************.js 77.3 kB
./dist/assets/js/googlesitekit-events-provider-contact-form-7-********************.js 646 B
./dist/assets/js/googlesitekit-events-provider-easy-digital-downloads-********************.js 624 B
./dist/assets/js/googlesitekit-events-provider-mailchimp-********************.js 630 B
./dist/assets/js/googlesitekit-events-provider-ninja-forms-********************.js 712 B
./dist/assets/js/googlesitekit-events-provider-optin-monster-********************.js 675 B
./dist/assets/js/googlesitekit-events-provider-popup-maker-********************.js 634 B
./dist/assets/js/googlesitekit-events-provider-woocommerce-********************.js 657 B
./dist/assets/js/googlesitekit-events-provider-wpforms-********************.js 633 B
./dist/assets/js/googlesitekit-i18n-********************.js 3.93 kB
./dist/assets/js/googlesitekit-main-dashboard-********************.js 142 kB
./dist/assets/js/googlesitekit-modules-********************.js 22.1 kB
./dist/assets/js/googlesitekit-modules-ads-********************.js 29.5 kB
./dist/assets/js/googlesitekit-modules-adsense-********************.js 113 kB
./dist/assets/js/googlesitekit-modules-analytics-4-********************.js 162 kB
./dist/assets/js/googlesitekit-modules-pagespeed-insights-********************.js 22.6 kB
./dist/assets/js/googlesitekit-modules-reader-revenue-manager-********************.js 13.6 kB
./dist/assets/js/googlesitekit-modules-search-console-********************.js 58 kB
./dist/assets/js/googlesitekit-modules-tagmanager-********************.js 32 kB
./dist/assets/js/googlesitekit-notifications-********************.js 3.63 kB
./dist/assets/js/googlesitekit-polyfills-********************.js 376 B
./dist/assets/js/googlesitekit-settings-********************.js 74.2 kB
./dist/assets/js/googlesitekit-splash-********************.js 74 kB
./dist/assets/js/googlesitekit-user-input-********************.js 48.7 kB
./dist/assets/js/googlesitekit-vendor-********************.js 321 kB
./dist/assets/js/googlesitekit-widgets-********************.js 78.9 kB
./dist/assets/js/googlesitekit-wp-dashboard-********************.js 61.3 kB
./dist/assets/js/runtime-********************.js 1.3 kB

compressed-size-action

Copy link
Collaborator

@aaemnnosttv aaemnnosttv left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @techanvil, just a few small things to update

@@ -27,8 +32,27 @@ function Template() {

export const Default = Template.bind( {} );
Default.storyName = 'Default';
Default.scenario = {
label: 'Modules/ReaderRevenueManager/Setup/SetupMain/Default',
delay: 250,
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We already have a base delay in our backstop config which is much more – does this actually help or is it just copied?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm - fair question. The story does have a brief loading state so I thought we might need the delay. But, maybe the default will suffice. I've removed the delay, let's see how it fares.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

To be honest, I had forgotten the default is 1 second which as you say is much more and will probably be enough.

@@ -27,8 +32,27 @@ function Template() {

export const Default = Template.bind( {} );
Default.storyName = 'Default';
Default.scenario = {
label: 'Modules/ReaderRevenueManager/Setup/SetupMain/Default',
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should avoid hardcoding the label as this is constructed based on other values such as the storyName and the default title below.

Copy link
Collaborator Author

@techanvil techanvil Jul 26, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks - another interesting comment. Most of our stories do specify the label, but you are quite right, it shouldn't be needed.

In fact I've only found one scenario without a label in the codebase (it's one that you updated recently to remove the label :)).

Anyhow - another good shout, I've removed the label. Again, it would be nice to tidy the existing stories up at some point in this regard.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, I did some analysis recently and found that there are a lot of stories where the generated scenario label differed from the one explicitly referenced but yeah it would be nice to clean that up.

.receiveGetPublications( [] );

return (
<WithTestRegistry registry={ registry }>
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please use WithRegistrySetup and the setup func instead – we should almost never need WithTestRegistry

Copy link
Collaborator Author

@techanvil techanvil Jul 26, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the reminder! I had forgotten this, and mostly copied the decorator from one of the existing stories which use WithTestRegistry, e.g.:

export default {
title: 'Components/Header',
component: Header,
decorators: [
( Story ) => {
const registry = createTestRegistry();
provideSiteInfo( registry );
return (
<WithTestRegistry registry={ registry }>
<Story />
</WithTestRegistry>
);
},
],

Anyhow - good to be reminded, I've updated the story!

It would be nice to go through the existing stories at some point with a view to tidying them up in this regard...

Copy link
Collaborator

@aaemnnosttv aaemnnosttv left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great, thanks!

@aaemnnosttv aaemnnosttv merged commit e802a17 into main Jul 26, 2024
25 of 26 checks passed
@aaemnnosttv aaemnnosttv deleted the enhancement/8837-fix-rrm-setupmain-story branch July 26, 2024 18:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants