Skip to content

Website Deployment QA QC Script

CarolLWagner edited this page Jul 5, 2022 · 27 revisions

Home Page

  • Check ouput logs from 'linkchecker'

Header

  • All links functional
  • Comments:
  • don't need period at end of title "Risk Profiler"
  • Probabilistic Risks tab goes to correct page but white tab doesn't change. Should be white rectangle/tab around text in header
  • Training link goes to empty page
  • Download link goes to correct page but descriptive text on page is NOT in English (nor French)
  • On the About page: I think text "About the Project" should be same size as "About Earthquake Scenarios"
  • link for "Learn more about the national earthquake risk assessment" stays on same page
  • In About Earthquake Scenarios section: slight change in text (italic is for you to see change, do not put word in italic; change to "Scenarios are defined by a magnitude, location, and fault type, and are developed ..."
  • the links for "learn more about earthquake scenarios" and "learn more about probabilistic risk" go to the map pages. To me "learn more about" would go to another website with more detailed explanation of these terms. Is this what you want - might not be necessary since the terms are defined/explained on that page. However if you mean for the links to go to the risk profiles map pages, then may I suggest changing the wording to "view the earthquake scenarios" and "view the probabilistic risk"
  • under Earthquake Risk Information and Users:
  1. "For both scenarios and probabilistic analysis, RiskProfiler provides ..." Is "scenarios" supposed to be plural?
  2. " ... experience shaking, and the potential level .." remove comma after shaking.
  3. "What are the consequences of an earthquake?" Since these are modelled consequences shouldn't we used a descriptor/adjective here? Such as "expected consequences" or "modelled consequences"
  • under Uncertainties and Intended Use:
  1. "..utilities, vehicles or high consequence facilities such as ..." put comma after vehicles.
  2. Will the general public know what "fire following" means? I see that as risk lingo. Just asking / open to discussion. (It could be changed to "resulting fires")
  3. The information is based on national-scale models of hazard, ...; change to "The information provided is based on national-scale models of hazard, .."
  • Contact page incomplete

Body

  • Loads without long delay
  • Quick links all work as expected
  • Comments:
  • Probabilistic link goes to map page instead of main Probabilistic page
  • Training link goes empty page
  • Download link goes to correct page but text is not in English
  • Earthquake Scenarios Section/links functional
  • Probabilistic Risks Section/links functional
  • Training Section/links functional
  • Downloads Section/links functional
  • Comments:

Footer

  • All links functional
  • Comments:

Earthquake Scenarios

  • Overall comments:

  • Cascadia Interface Best Fault

    • Shakemap Hexgrid loads 5km & 1km
    • Fatalities, Damage, Dollars * Check All plots at CSD and SAUID Scale
  • Georgia Strait

    • Shakemap Hexgrid loads 5km & 1km
    • Fatalities, Damage, Dollars * Check All plots at CSD and SAUID Scale
  • Leech River Full Fault

    • Shakemap Hexgrid loads 5km & 1km
    • Fatalities, Damage, Dollars * Check All plots at CSD and SAUID Scale
  • Sidney

    • Shakemap Hexgrid loads 5km & 1km
    • Fatalities, Damage, Dollars * Check All plots at CSD and SAUID Scale
  • Val des Bois

    • Shakemap Hexgrid loads 5km & 1km
    • Fatalities, Damage, Dollars * Check All plots at CSD and SAUID Scale

Probabilistic Risks

  • Landing page loads
  • Map at P/T scale loads
  • Zoom into CSD loads and is performant

Training

  • Training content populated

Download

  • All links function as expected

About

  • About content populated
  • All links function as expected

Contact Us

  • Contact content populated and up to date

Repeat For French Language Website Version

Check Accessibility via LightHouse

Check Mandatory Feature issues in repo

  • [ ]

Test for WCAG AA Compliance

  • check pro-grammatically
  • standards are changing

Check Mobile Layout and Responsiveness

Create GitHub actions automation