Skip to content

Application interaction patterns (testing)

lu haorui edited this page Oct 25, 2015 · 5 revisions

français




Use cases

Please use the Use case template when adding new use cases for consideration.

Application sign-in/sign-out

Research question(s):

  • Where should the link to sign-in/sign-out of an application displayed?
  • Should the link be displayed as text or as a button?
Other considerations:
  • Types of applications:
    • Standalone (w/ and w/o it's own domain or sub-domain)
    • Integrated
  • How are people getting to a Web application?
    • Are they accessing it through a domain or sub-domain?
    • Are they clicking on a standalone link?
    • Are they clicking on a link integrated into the content of a page?
  • On which type of pages would sign-in links be displayed?
    • Home pages.
    • Content pages (w/ and w/o left navigation bar, w/ and w/o right column or floating box).
  • On which type of pages would sign-out links be displayed?
    • Application content pages.
  • What happens when a user clicks on a link that would take them away from the application while signed-in to an application (e.g., the canada.gc.ca link)?
  • Accessibility.
Potential solutions:
  • Above the H1
    • But the Skip to Content link sends the user to the H1, which would skip the sign-in/sign-out link.
  • Below the H1
    • What happens if there is no H1 (visible or at all)?
    • What happens if the is content in the right column below the H1 (e.g., related links)?
  • To the right of the breadcrumb
    • What happens if there is no breadcrumb?
  • In the footer
    • Under what heading? In which order under that heading?
    • What if the footer is empty?
  • In the GC navigation bar
    • Before or after the language toggle?
  • In the site navigation bar
    • Following other menu items or to the right?
  • In a left navigation bar
    • Under what heading? In which order under that heading?
  • In the content
Scope:
  • Testing of two positions for the sign-in/sign-out, to the right of the breadcrumb and in the Government of Canada navigation bar.
  • Testing of how the sign-in/sign-out would integrate with the breadcrumb when the breadcrumb is long.
  • Testing of the workflow from sign-in to sign-out.
Related issues: Tasks:
Name Description Assigned to Status
Test plan Develop test plan. Not started

Materials:

Mockups:

Test plan: Application sign-in/sign-out test plan

Test results: Application sign-in/sign-out test results



Comments:

Clone this wiki locally