Uploaded image for project: 'PUBLIC - Liferay Portal Community Edition'
  1. PUBLIC - Liferay Portal Community Edition
  2. LPS-112169

Replace service mocks for READS with real AC endpoints

    Details

      Description

      For this story:

      • Reads are mocked data from AC
      • "Total reads" doesn't show "today" data (they're substracted from the total) 
      • Data are retrieved from AC for the full URL, although the canonical is being sent. AC will fix their page report in the next months, so they'll be able to send data for canonical URLs
      • If canonical URL changes (for example by means of default language settings or friendly URL edition), data will be restarted (=a new URL is indexed). A warning whenever and wherever this happens will be needed, but it's not in the scope of this story. Rest of the changes in the web content or the content page will be considered to add an "edition mark" to the views&reads line graphic. Translations shouldn't be taken into account, because each locale version will have its own panel & metrics. 
      • For web content, the date considered for the beginning of the serie of data is the (1) latest between the web content publication date and the display page template publication date.  (2) association date between the Web Content and a Display Page  (3) the latest date between the web content first publish date (olderstJournalArticle.displayDate) and the association date between the web content and a Display Page (assetDisplayPageEntry.getCreateDate()) as the date when the serie of views & reads data begin, so:
        • Reads of the draft won’t be taken into account
        • Reads of the web content “previous life” before being associated with the display page won’t be taken into account
        • When the web content is edited the Content Performance Panel won’t be affected.
        • When the display page is edited the Content Performance Panel won’t be affected.
      • For blog entries, as they don’t support versioning, we are taking the latest date between Blog entry Creation date and the association date between the blog entry and the Display Page  

      See https://issues.liferay.com/browse/LPS-112587 for further details.

      Test Scenarios (Historical reads)

      AC ID Test Strategy Test Scenarios Is it covered by FrontEnd ? (JS-Unit) Is it covered by BackEnd? (unit or integration) Poshi?
      01 Regression Content Performance panel shows a chart with the historial reads (static week) NO NO YES
      02 Smoke Content Performance panel default time range is by week NO NO YES
      03 Regression A legend is displayed with the total reads of the time range YES NO NO
      04 Regression Content Perfomance panel shows a text with the time range YES NO NO
      05 Regression When the user hover a dot of the chart, a pop up with metrics on that time range shows YES NO NO
      06 Smoke Check the information displayed in the Content Performance panel is the same information of AC NO  NO YES 
      07 Sanity Check the reads from today are not being take into account in the historical reads NO YES NO 

      Test Scenarios (Total reads)

      AC ID Test Strategy Test Scenarios Is it covered by FrontEnd ? (JS-Unit) Is it covered by BackEnd? (unit or integration) Poshi?
      01 Smoke Number of total reads is displayed for Asset Display Pages YES NO NO
      02 Sanity Help text icon is displayed along the title "Total Reads" YES NO NO
      03 Smoke An error message is displayed when there is no data or there was a problem A dash character is displayed when there is no data or there was a problem YES NO NO
      04 Sanity Check the reads from today are not being take into account in the total reads NO YES NO

      Test Scenarios (Interval options)

      AC ID Test Strategy Test Scenarios Is it covered by FrontEnd ? (JS-Unit) Is it covered by BackEnd? (unit or integration) Poshi?
      01 Regression Content Performance panel shows a chart with the historical reads and views from the last week YES  YES NO
      02 Smoke When the user selects "Last 24 hours" interval, the chart will show the graphic for the interval selected in hours.  NO  YES NO 
      03 Smoke When the user selects "Last 7 days" interval, the chart will show the graphic for the interval selected in days.  NO  YES NO 
      04 Smoke When the user selects "Last 30 days" interval, the chart will show the graphic for the interval selected in days.  NO  YES NO 
      05 Regression "Next" button is disabled when the user selects "Last 24h", "Last 7 days" or "Last 30 days"  NO  NO YES 
      06 Sanity When the user clicks on the "Previous" button, the chart and title will be updated with the previous interval selected data and the "Next" button is enabled NO   NO YES 
      07 Sanity When the user clicks on the "Next" button, the chart and title will be updated with the next interval selected data  NO NO YES 
      08 Regression When the user clicks on the "Next" button, if the next interval is the last interval available, the "Next" button will be disabled  NO  YES NO 

      Test Scenarios (Overview of the content)

      AC ID Test Strategy Test Scenarios Is it covered by FrontEnd ? (JS-Unit) Is it covered by BackEnd? (unit or integration) Poshi?
      01 Regression Content Performance panel is only displayed for Asset Display Pages associated to Blogs/Web Contents NO NO YES
      02 Smoke Free trial and dismiss buttons are displayed when AC is disabled NO NO YES
      03 Sanity Free trial and dismiss buttons ARE NOT displayed when AC is enabled NO NO YES
      04 Smoke When Content Performance panel is opened, it is shown title, date and author YES YES NO 
      05 Sanity Content Performance panel IS NOT displayed for any page that is not an Asset Display Page associated to Blogs/Web Contents NO NO YES

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Packages

                  Version Package
                  Master