As a content manager, I want the Page Audit to launch automatically and also to be able to manually relaunch it

• Type: Story
• Status: Closed
• Priority: Minor
• Resolution: Completed
• Affects Version/s: None
• Fix Version/s: 7.4.1 CE GA2, 7.4.13 DXP GA1, Master
• Component/s: SEO Tools > Page Audit
• Labels:
  • fc_21_05
• Epic Link: tango-page-audit
• Sprint: TANGO | #59 DEV | Apr16-Apr30, TANGO | #60 DEV | Apr30-May14, TANGO | #61 DEV | May14-Jun04
• Git Pull Request: https://github.com/liferay-tango/liferay-portal/pull/1162

Motivation

As the Page Audit takes a while to complete, best way to speed up the process is to launch it at the same moment that the user opens the panel or changes the URL s/he wants to audit. There's also the need for users to be able to relaunch the audit manually, so data can be refreshed incase they're cached or there's an issue with the call.

Design

https://www.figma.com/file/I0BImwTEY740kKEseduLU5/LPS-111803-Page-audit-check-one-page-issues?node-id=810%3A0

Requirements

1. The call to the PageSpeed's API / cached data will be executed:

1a. Whenever the panel is opened

1b. Whenever the user changes the locale from the panel 

1c. When the page is loaded with the panel opened

Note: it will also be called anytime the page or the content has been published., but this requirement will be tackled in LPS-130622.

2. There will be a button to relaunch the audit manually when Google PageSpeed is enabled and the API is configured.

2a. The button will call the API for the selected language at that moment.

Note.- As a result of the bug LPS-132364, we are applying this changes to the URL we send:

• When localized URLs option is enabled, we will send localized canonical URLs of that page 
• If not enabled, we will consult the URL of each language (not the single canonical). As a result, the Canonical URL issue will show for all languages other than the default (because for those languages, the canonical doesn't coincide with the real URL)

Acceptance Criteria

 

Requirements	Acceptance Criteria	Test Strategy	Covered by frontend / backend test? (Yes/No)
1a. The call to the PageSpeed's API / cached data will be executed whenever the panel is opened	Given a page  When the user opens the Page Audit Panel  Then the API / cached data is called for the default language URL and the progress bar shows	Medium	No
1b. The call to the PageSpeed's API / cached data will be executed whenever the user changes the locale from the panel	Given the Page Audit Panel  When the user opens it and changes the language selected Then the API / cached data is called for that URL and the progress bar shows	Medium	No
1c. The call to the PageSpeed's API / cached data will be executed when the page is loaded with the panel opened	Given a site When the user visits a page where s/he had opened the Page Audit Panel previously to that visit Then the API / cached data is called for the selected  language URL and the progress bar shows	Medium	No
2. There will be a button to relaunch the audit manually when Google PageSpeed is enabled and the API is configured.	Given the Page Audit Panel  When the user opens it, Google PageSpeed is enabled and the API is configured Then there's a Reload button in the panel's header	Low	Yes
2a. The button will call the API for the selected language at that moment.	Given the Page Audit Panel  When the user clicks on the Relaunch button Then the API is called for the URL of the selected language	Critical	Yes