This repository has been archived by the owner on Mar 1, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 10
Cross Cutting Elements
Kate Mashkina edited this page Nov 21, 2019
·
35 revisions
- Footer Tests
- Public Use Tests
- Page Options Tests
- Simple Date Tests
- Related Resources Tests
- Language Toggle Tests
- Intro Text Tests
- Left Navigation Tests
All
- Verify Footer exists on the page.
- Verify that Footer Header is correctly displayed for English and Spanish pages
- For each content type, does the footer appear exactly once?
- For English content, is the footer in English?(already included)
- For Spanish content, is the footer in Spanish?(already included)
- If you take the entire text appearing in the footer, is the length at least 450 characters and less than 800 characters? (You should check English and Spanish to make sure these are "reasonable" numbers.)
- Does the rendered text contain any instances of the literal "<a"? (The expected answer is no, otherwise, the footer may have been rendered incorrectly.)
- There was a mention of specific elements which render differently at specific breakpoints. There should be a test for those elements (and only those elements) at each breakpoint.
- Article
- Press Release
- Blog
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)
All
- Verify if the Page Options Control are displayed on pages where they are expected.
Article, Biography,Blog Posts, Cancer Research List Page, Cancer Center, Event, Press Release,PDQ Cancer Info Summary, PDQ Drug Info Summary.
- Verify if the Font Resizer icon is displayed where it is expected to display at desktop breakpoint.
- 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.
- 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.
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.
-
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.
- 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.
- Verify that the E-mail button is displayed at default breakpoint.
- Verify that the Facebook button is displayed at default breakpoint.
- Verify that the Twitter button is displayed at default breakpoint.
- Verify that the Pinterest button is displayed at default breakpoint.
- Article
- Press Release
- Cancer Center
- Biography
- 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
- Article
- Blog
- Press Release
- 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
- Article
- 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
- 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
- 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
All
- Verify Language Toggle is present
- Verify Language Tog le 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.
- Article
- Blog
- 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)
All
####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)