Testing/QA plan

[thrijith]

Test site information

The easiest way to test these migrations is to clone one of these test sites, and then switch the theme.

• http://10up-responsi.cms-devl.bu.edu/flexi/
• http://10up-responsi.cms-devl.bu.edu/responsi-1x/
• http://10up-responsi.cms-devl.bu.edu/responsi-2x/

Test migrations

• Migrate a site from Flexi Framework to 3x
• Migrate a site from Flexi Kenmore to 3x
• Migrate a site from 1x to 3x
• Migrate a site from 2x to 3x
• Migrate a site from r-childrens-center to 3x
• Migrate a site from r-pardeeschool to 3x
• Migrate a site from r-dining to 3x

Test comments

• If a site has comments enabled, 3x should respect that.
• If a site has comments disabled, 3x should respect that.
• A 3x child theme should be able to disable all comments, regardless of site settings.
• If a 3x child theme is disabling comments, user feedback should appear on the Discussion Settings page as well as on single posts to notify the user that the theme is controlling this setting.

VRT Testing

• Run visual regression testing
• Follow up with browser testing if VRT fails

[thrijith]

@ashleykolodziej

• For migration and comments testing, can you confirm if that has to be done manually and should also contain steps to help others in migrating?

• For VRT, I see a PR here, please let me know if I should look into that

• Follow up with browser testing if VRT fails ( To confirm, do manual tests using third party services like BrowserStack? to make sure everything is working as expected? )

[ashleykolodziej]

@thrijith I'd love help with that pull request for VRT! It's not working right now and I'm not sure why, but it looks really promising.

Migration testing will need to be done manually - if you can leave the migrated sites here, I can double check the correct values are in site options.

And yes - if VRT fails, that line basically means just open the sites up manually in a browser. We don't need to use BrowserStack or anything, it's more to double check that the error is actually an error, and find out why. Sorry for the confusion!

[thrijith]

Thanks for the info @ashleykolodziej !

I started testing with flexi, but I am pausing for now in order to move remaining changes found in the audit, will post updates about testing here once that is done.

Initial test of site migrated from flexi to 3x here, seems to have issue with menu styling an footer missing, will re-verify after moving remaining items found in audit.

---

Updates: 8-7-2020

All sites were migrated with the following steps:

1. Clone site from the original site.
2. Activate 3x framework theme.
3. Activate bu-responsive-customizations plugin.
4. Run wp responsi migrate flexi --url={siteurl} to migrate options data, this step may change later.

• Migrated a site from Flexi Framework to 3x -> http://10up-responsi.cms-devl.bu.edu/3x-flexi-test-7-8-20/
• Migrated a site from 1x to 3x -> http://10up-responsi.cms-devl.bu.edu/responsi-1x-to-3x-test-7-8-20
• Migrated a site from 2x to 3x -> http://10up-responsi.cms-devl.bu.edu/responsi-2x-3x-test-7-8-20/ ( Everything seems to be ok, except there is an issue with footer on homepage due to widget not being migrated )

---

Updates: 8-10-2020

Test migration of child themes :

• @ashleykolodziej Can you provide URL(s) for sites above mentioned old child themes?

• If a site has comments enabled, 3x should respect that.
• If a site has comments disabled, 3x should respect that.
• A 3x child theme should be able to disable all comments, regardless of site settings.

I tried enabling/disabling using the responsive_has_comment_support filter, please let me know if that was the expected way to test this out?

• If a 3x child theme is disabling comments, user feedback should appear on the Discussion Settings page as well as on single posts to notify the user that the theme is controlling this setting.

@ashleykolodziej can you provide an example of the notification that should appear on above mentioned pages?