Opened on 07/31/2015 at 05:08:21 AM

Last modified on 01/30/2018 at 11:05:38 PM

#2840 new change

Update reference section on test pages

Reported by: Ross Assignee: Ross
Priority: P5 Milestone:
Module: Unknown Keywords:
Cc: philll, Ross Blocked By:
Blocking: Platform: Unknown / Cross platform
Ready: yes Confidential: no
Tester: Ross Verified working: no
Review URL(s):

Description

Background

It is extremely useful for testers to have some form of reference or specification to test against. Ideal information includes explanations of certain changes, screenshots of how functionality should look when working correctly and so on.

This does party exist in some form but is scattered across the main site, the forums, other sites and is in general in a "help" format. It would be useful instead to have short-form/condensed "it should look and work like this" pages to go along with the tests themselves.

What to change

CMS related

  • Create a template called "reference" in /templates/.
  • Create an include called "references" in /includes/.
  • Include "references" file in home page.

Known issues section

  • Add a section to list noteworthy known issues that may affect testing. A good example is the First Run Page not opening again on reinstall because previous user data is still present.

Screenshots

  • First Run Page - Normal Layout

A full page screenshot of the First Run Page in its normal layout (ie. English). Should include text describing the sections of the page.

  • First Run Page - French Layout

A full page screenshot of the First Run Page in its French layout. In French the order of the social and extra privacy toggles is swapped. Should include text describing this swap.

  • Window/Dialog set - Firefox

How-to's

  • Add/Remove an official subscription.

Basic step through of adding/removing an official subscription and what the UI should look like as it is performed.

  • Add/Remove a custom subscription.

Basic step through of adding/removing a custom subscription and what the UI should look like as it is performed.

  • Add/Remove custom filters.

Basic step through of adding/removing custom filters and what the UI should look like as it is performed.

  • Backup and Restore

Basic step through of using the backup and restore functionality and what the UI should look like as it is performed.

Where to put the changes

Reference pages should live in the testpages repository in the /pages/reference/ directory.

Attachments (0)

Change History (3)

comment:1 Changed on 01/25/2017 at 03:24:39 PM by juliandoucette

@Ross this ticket is aging. I would suggest lowering it's priority or breaking it up into smaller chunks if it's not going to get done. Please reach out to us if you need help.

comment:2 Changed on 08/30/2017 at 03:31:58 PM by juliandoucette

  • Cc Ross added
  • Priority changed from P3 to P5

comment:3 Changed on 01/30/2018 at 11:05:38 PM by juliandoucette

  • Component changed from Websites to Unknown

Add Comment

Modify Ticket

Change Properties
Action
as new .
as The resolution will be set. Next status will be 'closed'.
to The owner will be changed from Ross.
Next status will be 'reviewing'.
 
Note: See TracTickets for help on using tickets.