nciocpl / cgov-digital-platform-qa Goto Github PK

View Code? Open in Web Editor NEW

1.0 1.0 10.0 58.36 MB

QA Automation framework for the Cancer Gov Digital Platform

Java 100.00%

cgov-digital-platform-qa's People

Contributors

Stargazers

Watchers

Forkers

supriyasaxena0605 alinai popkhadzeg daquinohd bryanpnih viswanath11 kate-mashkina blairlearn blairl-nih qakiran

cgov-digital-platform-qa's Issues

Test Case: Verify Cross-Cutting Elements - Site Banner

Pre-requisites

Test content pages are created

Content Types Covered:

Steps:

Verify Site Banner exists on the page.
For each content type, does the Site Banner appear exactly once
Verify that Site Banner is correctly displayed
Assert site Banner link is not broken

Test Case: Verify Browser Title

Pre-requisites

Create YAML Content for all content type pages below
Import YAML Content to test environment

Content Types Covered:

Test scenarios:

Browser Title:

Navigate to page URL for each content type
Assert Browser Title is presented
Assert that the Browser title text is non-empty

Negative Tests:

Step1

YAML Content Request for Article with Lead image

Content Type: Article with lead image with credit, caption, alt text

Live Site URL: https://www.cancer.gov/about-cancer/treatment/side-effects/

Detect whether browser version matches driver version

Browser drivers tend to be tied to specific versions of the browser. A mechanism is needed to report when they aren't in sync.

One possible solution is for the test driver to download the driver.

Pre-requisites

pre-condition

Content Types Covered:

Cgov Article
Blog Posts
Press Release
Cancer Center
Biography
Event
PDQ Drug Info Summary
Mini Landing Page
Cancer Type Home Pages
Infographic
Video
File

Steps:

Verify that the Body section is visible if it is present on the content
Verify that the Body section is not visible if it is not present on the content
Verify that On this section appears in the body if the Heading of Body is populated on the content.
Verify that On this section is not visible in the body if the Heading of Body is not populated on the content.
Verify that the correct translation is displayed on the Body section
Verify that the correct Inline feature card is displayed if it is embedded on the content.
Verify that the correct video player is displayed if it is embedded on the content.
Verify that the correct Image is displayed if it is embedded on the content.
Verify that the correct Infographic is displayed if it is embedded on the content.
Verify that the correct call-out box is displayed if it is embedded on the content.
Verify that the correct pull-quote is displayed if it is embedded on the content.
Verify that the correct sortable table is displayed if it is embedded on the content.
Verify that the correct normal table is displayed if it is embedded on the content.
Verify that the correct glossification is displayed if it is embedded on the content.
Verify that the correct Tweet this is displayed if it is embedded on the content.
Verify that the correct Raw HTML block is displayed if it is embedded on the content.
Verify that the correct Managed Link is displayed if it is embedded on the content.
Verify that the correct External link is displayed if it is embedded on the content.

Depends on Issue #

Requirement Reference

https://github.com/NCIOCPL/cgov-digital-platform/wiki/Common-Fields#Body

Pre-requisites

Create YAML Content for all content type pages below
Import YAML Content to test environment

Content Types Covered

Article - #879
Press Release - http://ncigovcdstg.prod.acquia-sites.com/node/281
Blog - #880
Cancer Center -http://ncigovcdstg.prod.acquia-sites.com/about-cancer/coping/feelings/relaxation/dfharvard
Bio - http://ncigovcdstg.prod.acquia-sites.com/about-cancer/coping/feelings/relaxation/loukissas-jennifer

Test scenarios:

Navigate to page URL for each content type
Assert Lead Image is presented on the page
Assert image has ALT text visible if available
Assert image Credit is visible if available
Assert image caption is visible if available

Negative tests for Cancer center, Biography or any other content type having no lead image:

Assert Lead Image is NOT presented on the page (URL with no image)
Assert image ALT text is NOT visible if no ALT text is present (Url with Image/No ALT text)
Assert image Credit is NOT visible if no Credit is present (URL with Image/no Credit)
Assert image caption is NOT visible if no caption is present(URL with Image/No caption)

Depends on Epic

#114

Story: Verify Cross-Cutting Elements on all pages

Common UI elements Covered:

Site Banner (manual script)
Utility Bar(Out of Scope for automation at this time) NCIOCPL/cgov-digital-platform-acceptance-tests#125
Main Menu https://github.com/NCIOCPL/cgov-digital-platform-acceptance-tests/blob/master/cypress/integration/Crosscutting/MegaMenuTest.feature
Page Options/ Social Media -#11
Breadcrumbs https://github.com/NCIOCPL/cgov-digital-platform-acceptance-tests/blob/master/cypress/integration/Crosscutting/BreadcrumbTest.feature
Footer-https://github.com/NCIOCPL/cgov-digital-platform/issues/1160
Back To Top NCIOCPL/cgov-digital-platform-acceptance-tests#150
Language Toggle-https://github.com/NCIOCPL/cgov-digital-platform/issues/1392

Test Case: Verify Feature Card on Pages with Feature card

Pre-requisites

Create YAML Content for all content type pages below
Import YAML Content to test environment

Content Types Covered

Mini Landing Page
Home & Landing Page
Cancer Type Home Pages
Blog Landing Page (Series page)

Test scenarios:

Assert Feature card is displayed on the page if available
Check the Card title #36
Check the Card Description #39
Assert Promotional Image is presented on the page
Assert image has ALT text visible if available
Verify the Image source is not empty
Verify the Image source is not null
Verify the Image source url starts with "/"

Negative tests for PDQ Cancer Info Summary, PDQ Drug Info Summary and other content types having no Promotional image:

Assert Promotional Image is displayed on a feature card if lead image is not present. (URL with no lead image)
Assert that the correct crop of Lead Image is displayed on a feature card if Promotional image is not present.
Assert image ALT text is NOT visible if no ALT text is present (Url with Image/No ALT text)

Depends on Issue #
##Requirement Reference
https://github.com/NCIOCPL/cgov-digital-platform/wiki/Common-Fields#Promotional-Image

Pre-requisites

Create YAML Content for all content type pages below
Import YAML Content to test environment

Content Types Covered

Article - #885
Blog - #886

Test scenarios:

Navigate to page URL for each content type
Assert Intro text is presented

Negative Tests:

Navigate to other content type pages and verify Intro text is not present (URL's with other pages)

Look for "Español" instead of "Spanish" in the language toggle.

Commit bfd3a90 modifies the language toggle test data (test-data/languagetoggle-data.xlsx) to expect the word "Spanish" in the language toggle instead of "Español".

This is because the language toggle currently displays the incorrect text. After NCIOCPL/cgov-digital-platform#1541 is resolved, the test data should be switched back.

YAML Content Request for Press release in Spanish with Lead image

Content Type: Press Release in Spanish with lead image with credit, caption, alt text
Live Site URL: https://www.cancer.gov/espanol/noticias/comunicados-de-prensa/2018/llc-ibrutinib-estudio

Add tests for media links in Related Resources

Related resources can include links to files, infographics, and videos.

Test Case: Verify Feature Card Description

Pre-requisites

YAML content is ready for all the content types mentioned below

Content Types Covered:

Article
Blog Posts
Press Release
Cancer Center
Biography
Event
Mini Landing Page
Home & Landing Page
Cancer Type Home Pages
Blog Landing Page (Series page)
Infographic
Video
File

Steps:

Verify that the Feature card description is visible if Feature card description field is populated on the card on the content.
Verify that the Feature card description is not visible if Feature card description field is empty on the card on the content.
Verify that the correct text is displayed on the Feature Card description.

Depends on Issue #

###Requirement Reference
https://github.com/NCIOCPL/cgov-digital-platform/wiki/Common-Fields#Feature-Card-Description

Need capability to test HTTP status codes

Selenium does not expose functionality to examine HTTP status codes (or much of anything else that low level). This prevents us from creating tests to verify redirects, HTTP headers, etc.

Proposed solution:

Create an HttpProtocolPage class, similar to PageObjectBase to request a URL and expose the desired information.

YAML Content Request for Date display - Infographic

Content Type: Infographic

Need to create Infographic YAML content file to test Posted, Reviewed and Updated date display

Test Case: Verify Reviewed Date

Pre-requisites

Create YAML Content for all content type pages below
Import YAML Content to test environment

Content Types Covered

Article - #873

Test scenarios:

Navigate to page URL for Article Page
Assert Reviewed Date Label is presented on the page
Assert Reviewed Date is presented on the page
Negative Tests:
Assert Reviewed date is not present for the URL having no Reviewed date

Test Case: Verify Cross-Cutting element: Language Toggle

Pre-requisites

pre-condition

Content Types Covered:

All

Steps for Language Toggle:

Verify Language Toggle is present
Verify Language Toggle is present as 'Espanol' on English pages
Verify Language Toggle is present as 'English' on Espanol pages
Verify that Language Toggle is not present for pages having no translation pages.

Depends on Issue #

Test Case: Verify Cross-Cutting Elements - Main Menu

Pre-requisites

pre-condition

Content Types Covered:

All Content Types

Steps: (Desktop)

The system shall display a main navigational menu on desktop below the blue information bar (mega menu) and a search option in the main navigational menu
2.The system shall display the following primary nav sections and the site-wide search field in the mega menu:

About Cancer
Cancer Types
Research
Grants & Training
News & Events
About NCI
Site-wide search field
3.The system shall display the mega menu when the user has hovered over a primary navigation label using a mouse for a set period of time
4.The system shall close the mega menu when the user moves the mouse pointer off of a primary nav label on the main navigation bar
5.The system shall display level 2 and level 3 items within that selected section when the user has hovered over a primary nav label in the mega menu
6.The system shall display level 2 items within its respective primary navigation section as list headers with its corresponding level 3 items listed below it.
7.The system shall only display sections no more than three levels deep.
8.The following primary nav sections will display all level 2 and level 3 in the mega menu:
About Cancer
Research
Grants & Training
About NCI
9.The Cancer Types primary nav section will display:
• A to Z List of Cancers
• Common Cancer Types (list header that is not a link)
10.The common cancer types and other cancer categories will be separate with a pipe.

Test steps for Tablet/Mobile

1.The system shall display the mobile menu when user selects the mobile menu icon.
2.The system shall display the mobile menu as a fly out canvas.
3.The system shall allow users to close the mobile menu using a swipe gesture for tablet and mobile, or by clicking on the menu button
4.The system shall display the site banner above the mobile menu
5.The system shall display the same menu sections as on desktop (no more than 3 levels deep)
6.The system shall display expand/collapse options next to navigation labels on mobile
7.The system shall display a minus (-) next to a navigation label if it is currently expanded to display its child items in the mobile menu.
8.The system shall display a plus (+) next to a navigation label that section has child items beneath the level 1 heading
9.The system shall expand its corresponding section and display only the child items within that section when user selects the +
10.The system shall not display plus(+)/minus(-) sign next to a navigation label if it has no children to display in the mobile menu.
11.The system shall display the +/- options and the navigation label as separate and distinct touch areas.
12.The system shall load the page a user selects when the user touches a navigation label.
13.The system shall allow users to expand (+) or collapse (-) a section on touch.
14.The system shall show the expand and collapse with a sliding down and sliding up animation, respectively.
15.The system shall not allow a user to expand more than one sibling section at a time.
16.The system shall collapse any sections that are currently expanded if the user selects the expand option for a sibling section.
17.The system shall allow the user to collapse the active path when a sibling section is expanded

Depends on Issue #

Test Case: Verify Recommended Content

Pre-requisites

Create YAML Content for all content type pages below
Import YAML Content to test environment

Content Types Covered

Blog - #892

Test scenarios:

Navigate to page URL for Blog Post Content type
Assert Recommended From NCI section title is presented (verify in Espanyol)
Assert Recommended From NCI Cards images present and links are active
Asset Recommended From NCI Card URLs are active

Negative Tests:

Navigate to Blog Post Content type and verify Recommended From NCI Cards doesn't appear when title is absent
Navigate to Blog Post Content type and verify Recommended From NCI Title doesn't appear when cards are absent

Add Test Data: Spanish Blog Post with Intro Text

All currently existing blog posts with "Spanish" actually contain English text.

The goal of this ticket is to either locate or create a blog series containing Spanish data and at least one post with the Intro Text field and add it to the Intro Text test data.

YAML Content Request for Press Release with lead image

Content Type: Press Release in English with lead image with credit, caption, alt text
Live Site URL: https://www.cancer.gov/news-events/press-releases/2018/melanoma-immunotherapy-predictor

Test Case: Verify Card Title

Pre-requisites

pre-condition

Content Types Covered:

Type 1
Type 2
Type 3

Steps:

Step
Step
Step

Depends on Issue #

Requirement Reference:

https://github.com/NCIOCPL/cgov-digital-platform/wiki/Common-Fields#Card-Title

Test Case: Verify Short Title

Pre-requisites

pre-condition

Content Types Covered:

Type 1
Type 2
Type 3

Steps:

Step
Step
Step

Depends on Issue #

Requirement Reference:

https://github.com/NCIOCPL/cgov-digital-platform/wiki/Common-Fields#Short-Title

Test Case: Verify Citations

Pre-requisites

Content Type Article, Press Release, Blog, PDQ CIS have been migrated.

Content Types Covered

Article
Press Release
Blog
PDQ CIS - (will be tested in #76)

Test scenarios for Citations:

1.Navigate to page URL for each content type
2.Verify that the Citation Section is present
3.Verify that the Citation Header is visible
4.Verify that the Citation Text is correct
5.Verify that the Citation Text length is correct (within a specified range) for each Citation
6.Verify that the Pub Med link Exists for Citations
7.Verify that the PubMed link point to PubMed URL

Negative Tests for Citations:

Navigate to other content type pages (except Article, Press Release, Blog Posts) and verify Citation Section doesn't appear.
Verify that Pub Med links does not appear in citations where it is not expected to appear.

Test Case: Verify Cross-Cutting Elements: Verify the right metadata is being pulled for page options

Pre-requisites

pre-condition
Page options requires metatags to be done for them to work

Content Types Covered:

All

Steps:

Verify that the system shall have the following social media metadata:

og:title
og:description
og:type
og:image
og:url
og:sitename
twitter:card

Verify that the system shall map the og:title metadata to the "Short Title" field on content items

Reference: NCIOCPL/cgov-digital-platform#1551
Depends on Issue #NCIOCPL/cgov-digital-platform#197
#NCIOCPL/cgov-digital-platform#1509

YAML Content Request Blog post with Lead Image

Content Type: Blog post with Lead Image with credit, caption, alt text
Live Site URL: https://www.cancer.gov/news-events/cancer-currents-blog/2019/transition-lowy-nci-acting-director

YAML Content Request for Spanish Article with Lead Image

Content Type: Article in Spanish with lead image with credit, caption, alt text
Live Site URL: https://www.cancer.gov/espanol/cancer/tratamiento/efectos-secundarios

Expand test data for Language toggle.

The language toggle test data only checks the language toggle for Article, Cancer Info Summary, Blog and Press Release in English, and only checks Press Release in Spanish.

This should be expanded to cover all content types in both English and Spanish.

Test Case: Verify Date Display Mode

Pre-requisites

pre-condition

Content Types Covered:

Type 1
Type 2
Type 3

Steps:

Step
Step
Step

Depends on Issue #
##Requirement Reference
https://github.com/NCIOCPL/cgov-digital-platform/wiki/Common-Fields#Content-Dates

Test Case: Verify Related Resources

Pre-requisites

Create YAML Content for all content type pages below
Import YAML Content to test environment

Content Types Covered

Article - /about-cancer/coping/feelings
Press Release - /news-events/press-releases/2018/tmds-aml-risk-chemo
Blog - /about-cancer/coping/feelings/relaxation/vitamin-d-supplement-cancer-prevention
Cancer Center - /about-cancer/coping/feelings/relaxation/duke-university
Bio - /about-cancer/coping/feelings/relaxation/loukissas-jen

Test scenarios:

Assert Related Resources section exists on the page
Assert Related Resources internal links exists on the page
Assert non-zero number of Related Resources internal links are present.
Assert all Related Resources internal links have non-blank hrefs.
Assert all Related Resources internal link hrefs contain no whitespace. (i.e. no leading/trailing/embedded spaces, tabs, new lines.)
Assert all Related Resources external links have “Exit Disclaimer” styling

Negative Tests:

Assert no Related Resources section/links appear on the page

Depends on Epic

#599

Test Case: Handle pop-ups for Page Options

Content Types Covered:

Article, Biography, Blog Post, Cancer Research List Page, Cancer Center, Event, Press Release, PDQ Cancer Info Summary, Blog Series, CTHP, Home & Landing Page, Mini Landing Page, Infographic, Video

Steps:

-[ ] 1. Verify that the Print Preview App shows up on clicking the Print icon on the Page Options.
-[ ] 2. Verify that the pop up for Email appears on clicking the Email icon
-[ ] 3.Verify that the Email icon points to the href.
-[ ] 4. Verify that the pop up appears on clicking the Facebook icon.
-[ ] 5.Verify that the pop up appears on clicking the Twitter icon.
-[ ] 6.Verify that the browser title displays in the Twitter pop up.
-[ ] 7. Verify that the pop up for Pinterest appears on clicking the Pinterest icon

Depends on Issue #1551

Test Case: Verify Public Use

Pre-requisites

Create YAML Content for all content type pages below
Import YAML Content to test environment

Content Types Covered

Article - /about-cancer/coping/feelings/relaxation/stress-fact-sheet
Press Release - /news-events/press-releases/2018/oropharyngeal-hpv-cisplatin
- /espanol/noticias/comunicados-de-prensa/2018/oropharyngeal-hpv-cisplatin
Blog - about-cancer/coping/feelings/relaxation/hpv-vaccine-presidents-cancer-panel-improving-uptake

Test scenarios:

Navigate to page URL for each content type:

Assert Public Use Text is presented on the page.
Verify that Public Use text is correctly displayed (English and Spanish pages)
Verify that Public Use text size is at least 200 characters and less than 400 characters
Assert Content Title is presented in Public Use Text (English and Spanish pages)
Assert that Reuse link that appears in Public Use Text is active (English and Spanish pages)

Negative Tests:

Verify Public Use Text and Link doesn't appear (URL's with other pages)

Test Case: Verify Cross-Cutting Elements - Search

Pre-requisites

pre-condition

Content Types Covered:

Type 1
Type 2
Type 3

Steps:

Step
Step
Step

Depends on Issue #

Add test scenarios for "accessible text version" field.

Images and infographics have an "Accessible Text Version" field containing a plain-text description of the image's content. When this field is set, and the image is used as an article's Lead Image, the image is rendered with a longdesc attribute which retrieves the text. For infographics, this attribute is always rendered when the field is set.

Test Case: Verify Pretty URL

Pre-requisites

All content types with Pretty Url

Content Types Covered:

All Content Types, home pages and list pages

Steps:

Navigate to given URL
Assert the current page URL contains pretty-url
Assert page displays with no errors

Depends on Issue #

#Requirement Reference
https://github.com/NCIOCPL/cgov-digital-platform/wiki/Common-Fields#Pretty-URL

Test Case: Verify Search Engine Restrictions

Pre-requisites

pre-condition

Content Types Covered:

Article
Press Release
Cancer Center
Biography
Event
Mini Landing Page
Home & Landing Page
Cancer Type Home Pages
Blog Landing Page (Blog Series)
Blog Posts
Infographic
Cancer Reserach List
Video
File (???)

Steps:

Verify that meta name="robots" content="index" appears in the source code if the Include in search is selected
2.Verify that meta name="robots" content="noindex" appears in the source code if the Exclude from search is selected

Depends on Issue #

Requirement Reference

https://github.com/NCIOCPL/cgov-digital-platform/wiki/Common-Fields#Search-Engine-Restrictions

Test Case: Verify Cross-Cutting element: Footer

This covers the automation of the footer - see details:
https://github.com/NCIOCPL/cgov-digital-platform-qa/wiki/Cross-Cutting-Elements#footer

Test Case: Verify Cross-Cutting Elements - Back To Top

Pre-requisites

pre-condition

Content Types Covered:

The system shall display a "Back to Top" option across all pages on the desktop site

Steps:

The system shall not display the "Back To Top" option when the user is viewing the site in mobile size
The system shall allow the Back to Top option to appear when user has scrolled to 600 px down the screen
The system shall not display the Back to Top option when user is at the top of the screen on desktop

Depends on Issue #

Add Test data for Blog Page and Press Release to Lead image test data sheet

Add Test data for Blog Page and Press Release to Lead image test data sheet once the issue#1574 for empty p tags for Image caption is resolved.

Test Case: Verify Managed List

Pre-requisites

Content Type : Home/Landing, Mini Landing, Cancer Research pages

Content Types Covered

Displays in:

Lists on Home page
Lists on Landing pages
Lists on Mini Landing pages

Test scenarios for Managed List:

1.Verify that the Managed List Section is present
2.Verify the count of List items in the Managed List.
3.Verify that the title of the List item in the Managed List
4.Verify the Managed List Description Text length
5.Verify the thumbnail image source in the Managed List
6.Verify the Alt text of thumbnail image in Managed Lists
7.Verify the internal links in the Managed List
8.Verify the external links in the Managed List

Negative Tests for List Descriptions:

1. Navigate to other content type pages (except Home/Landing pages, Mini Landing pages) and verify if Managed List section doesn't appear.

###Depends on

[#74] (#74)

###Requirement Reference
https://github.com/NCIOCPL/cgov-digital-platform/wiki/Common-Fields#List-Description

Test Case: Verify Page Title

Pre-requisites

Create YAML Content for all content type pages below
Import YAML Content to test environment

Content Types Covered:

Article -/about-cancer/coping/feelings
Article -/espanol/cancer/sobrellevar/sentimientos
Blog - /about-cancer/coping/feelings/relaxation/vitamin-d-supplement-cancer-prevention
Blog - /espanol/about-cancer/coping/feelings/relaxation/vitamina-d-complemento-cancer-prevencion
Press - /news-events/press-releases/2018/tmds-aml-risk-chemo
Press - /espanol/noticias/comunicados-de-prensa/2018/tmds-aml-riesgo-quimio

Test scenarios:

Content Title/H1:

Navigate to page URL for each content type
Assert Page Title is presented
Assert that the Page title text is non-empty

Test Case: Verify Cross-Cutting Elements - Breadcrumbs

Pre-requisites

pre-condition

Content Types Covered:

All pages except Home and Landing Pages

Steps:

The system shall display breadcrumbs on desktop and tablet breakpoints
The system shall not display breadcrumbs on the homepage or landing pages.
The system shall not display breadcrumbs on mobile breakpoints
The system shall display each breadcrumb in the path as a link
The system shall not display the breadcrumb of the user's current page location

Test Case: Verify Site Section / Left Nav

Requirement Reference:

https://github.com/NCIOCPL/cgov-digital-platform/wiki/Vocabularies-Site-Sections

Pre-condition

Active Parent and child page Url's

Content Types Covered:

####Desktop Breakpoint

Verify Left Navigation on Desktop breakpoint
Verify left navigation Level 1 heading is active page
Verify Level 1 heading can be expanded in to child level of items
Verify Left Navigation heading label matches the expected page title (From data provider)

Mobile/Tablet Breakpoint

Verify Section Menu Nav appears ( left nav / tongue on mobile) on Mobile/Tablet breakpoint
Verify mobile navigation Level 1 heading is active page
Verify mobile navigation Level 1 heading can be expanded to child level of items
Verify mobile navigation heading label matches the expected page title (From data provider)

Test Case: Verify Posted Date

Pre-requisites

Create YAML Content for all content type pages below
Import YAML Content to test environment

Content Types Covered

Test scenarios:

Navigate to page URL for each content type
Assert Posted Date Label is presented on the page (**not applicable for BLOG)
Assert Posted Date is presented on the page
Negative Tests:
Assert posted date is not present for the URL having no posted date

Test Case: Verify Updated Date

Pre-requisites

Create YAML Content for all content type pages below
Import YAML Content to test environment

Content Types Covered

Article - http://ncigovcdstg.prod.acquia-sites.com/about-cancer/coping/feelings
Press Release - http://www.devbox/news-events/press-releases/2018/tmds-aml-risk-chemo
Cancer Center - http://ncigovcdstg.prod.acquia-sites.com/about-cancer/coping/feelings/relaxation/dfharvard
Biography - http://ncigovcdstg.prod.acquia-sites.com/about-cancer/coping/feelings/relaxation/loukissas-jennifer

Test scenarios:

Navigate to page URL for each Content Page
Assert Updated Date Label is presented on the page
Assert Updated Date is presented on the page

Negative Tests:
1 Assert Updated date is not present for the URL having no Updated date

Test Case: Verify Syndicate

Pre-requisites

Create YAML Content for all content type pages below
Import YAML Content to test environment

Content Types Covered

Article - #881

Test scenarios:

Navigate to page URL for Article content type
Assert Page Syndicate Text is presented
Assert Page Syndication link is active
Assert Syndication icon is presented

Negative Tests:

Navigate to other content type pages and verify Syndication Text and Link doesn't appear (URL's with other pages)

Story: QA Test Plan

1. Introduction

This document records the detailed test plan for the quality assurance effort necessary to validate the final functionality of CancerGov Digital Platform migration to Drupal CMS.

2. Test Approach

The Test Approach presents the overall strategy for verifying the requirements to be tested.

3. Test Objectives

The major testing objectives are:
• Functional Testing to ensure that the CancerGov Digital Platform is developed as per the scope captured in respective User Stories, Annotated Wireframes
• Define the test cases for the stories within that iteration
• Test the stories being implemented during that iteration
• Test Scripts preparation for automation regression testing

4. YAML Content Request for:

5. Test Case Scenarios

Verify Cross-Cutting Elements on pages:

Verify Cross-Cutting Elements #23
- Verify Cross-Cutting Elements: Page Options/Social Media #11
- Verify Cross-Cutting element: Footer https://github.com/NCIOCPL/cgov-digital-platform/issues/1160
- Verify Cross-Cutting element: Language Toggle https://github.com/NCIOCPL/cgov-digital-platform/issues/1392
- Verify Site Banner
- Verify Search
- Verify Main Menu
- Verify Back To Top

Verify common UI elements on content type pages:

6. Bugs

- Intro Text styling on Article/Blog pages #843
- Footer class and the child div tag are appearing twice #1376
- Public Use text should reference the content title on Blog Post page #1507

Test Case: Verify Cross-Cutting Elements: Page Options/Social Media

Requirement Reference for Font Resizers:
https://github.com/NCIOCPL/cgov-digital-platform/wiki/Page-Options

# Pre-requisites
Test content pages are created

# Content Types Covered for Page Options:
All

**#Steps for Page Options Control: **

Verify if the Page Options Control are displayed on pages where they are expected.

# Content Types Covered for verifying Font Resizer Present:
Article, Biography,Blog Posts, Cancer Research List Page, Cancer Center, Event, Press Release,PDQ Cancer Info Summary, PDQ Drug Info Summary.

Tests for Font Resizer: (Desktop)

Verify if the Font Resizer icon is displayed where it is expected to display at desktop breakpoint.

Tests for Font Resizer: (Tablet)

Verify that the font Resizer is NOT displayed when they are NOT expected to display at Tablet breakpoint for the same set of pages that display Fontresizer at Desktop breakpoint.

Tests for Font Resizer: (Mobile)

Verify that the font Resizer is NOT displayed when they are NOT expected to display at Mobile breakpoint for the same set of pages that display Fontresizer at Desktop breakpoint.

**Test to veify that Font Resizer is NOT displayed on the following Content Types:
Blog Series, CTHP pages, Home and Landing Pages, Mini Landing Pages, Infographic, Video

Verify that the font Resizer is NOT displayed when they are NOT expected to display on the above Content Types at default breakpoint.

Tests for Print Button: (Desktop)

Verify if the Print Button is displayed where it is expected to display at desktop breakpoint.

Tests for Print Button: (Tablet)

Verify that the Print Button is NOT displayed when they are NOT expected to display at Tablet breakpoint for the same set of pages that display Print Button at Desktop breakpoint.

Tests for Print Button: (Mobile)

Verify that the Print Button is NOT displayed when they are NOT expected to display at Mobile breakpoint for the same set of pages that display Print Button at Desktop breakpoint.

Test for Email Button:
1.Verify that the E-mail button is displayed at default breakpoint.

Test for Facebook button:
1.Verify that the Facebook button is displayed at default breakpoint.

Test for Twitter Button:
1.Verify that the Twitter button is displayed at default breakpoint.

Test for Pinterest Button:
1.Verify that the Pinterest button is displayed at default breakpoint.

Test Case: Verify Meta Description

Pre-requisites

Page content with meta description related or imported on environment for testing.

This testcases was combined and Completred in:

Test Case: Verify Syndication Keywords

Pre-requisites

pre-condition

Content Types Covered:

Article
Blog Posts
PDQ Cancer Info Summary
PDQ Drug Info Summary
Infographic

Steps:

Step
Step
Step

Depends on Issue #

##Requirement Reference
https://github.com/NCIOCPL/cgov-digital-platform/wiki/Common-Fields#Syndication-Keywords