Laddawn.com : Key to reporting

Categories

W - Web interface

• Design fidelity - does what got developed match the visual designs, and functional specifications for flow and interactive features?
• Is design displaying properly in different browsers and browser versions? (Insert Google Analytics data on Laddawn users' browsers.)
• Eventually content - for fidelity to styling and design. Ideally proof-reading all copy will be done prior to posting to new website.

TESTERS: Primarily Steve and Suan; occasionally Owen. For now the checklist or test script consists of the functional specifications, bucket by bucket; remains to be seen if we need something detailed.

D - Data updates

• Writing data back to Avante accurately, a.k.a. file updates. For example -  compare a quote done on current site to a quote done the new site. Does the resulting data (pricing, etc.) that gets written back to Avante match?  

TESTERS: Judy? Suggest creation of a checklist of what to test and who will be testing be created, preferably as a child page.

Q - Database queries

When a web action queries the Avante database, is it returning results that match specifications?

• Exact matches and YMAC results; do they match Cliff and Tom's rules, for what is returned, the order in which they are presented, etc.? Do matches include customer-supplied part numbers when applicable?
• Availability and warehouse of origin - do they match new allocation rules for both defaults and alternatives, in results and cart?
• Correct bundling options at checkout?
• Customer information, including end customer drop ship or alternative distributor warehouse location.
• Contact information (the website end user)
• Retrieval of saved carts, items;  include customer numbers where applicable.

TESTERS: Cliff, Tom, possibly CE staff; possibly Owen; possibly IT staff. No database queries should be tested by non-IT staff, until IT indicates readiness.

Priority

The reporter assigns the priority.

1- High

Address ASAP before all other issues. Cannot proceed with testing. Severe.

2 - Medium

Address ASAP, after high priority issues. Moderate severity.

3 - Low

Low severity. If quick and easy to fix (e.g., an isolated typo), address ASAP. Otherwise, fix after all high and medium priority issues have been addressed.

Section where issue found

Even if it seems self-evident from the issue summary or description, please indicate the section of the site where the issue appears or originated from; this will aid in isolating the issue (particularly if the feature is present in more than one section - such as sharing an item from the search results v. sharing an item from the cart), as well as ability to sort the QA list. Sections are as follows:

• Shop tab
• Saved Items tab - includes sharing or saving an item if that's where it originated
• Order History tab
• Saved Carts tab
• Active Cart tab - includes sharing a cart or saving or sharing an item if that's where it originated
• Checkout  
  • Addresses
  • Shipping & Packaging
  • Labeling
  • Payment
  • Summary
  • Giving
    
• My account/user preferences
  
  • My profile + avatar
  • Shipping
  • Worflow
  • CE
    
• Narrative thread

• Global - applies to all pages/screens or many (semi-global) - for example, items in the banner (issue #1 on the QA page); behavior that applies to multiple tabs or screens (e.g. issue # 2 on QA page).

• Content - specific content page; give URL.

Assigned to and Status

• Statuses include Open, In Progress, Test, and Done.
• Issue reporters from IT (primarily John and Judy; occasionally Jim and Cathy) will assign issues to the appropriate developer(s).
• Non-IT issue reporters will assignto Cathy, and give the issue a status of "Open."  Cathy will reassign issues to the appropriate developer(s) to fix.
• Regardless of who assigns an issue to a developer... When the developer commences work, he or she will change status to "In progress." When the developer has fixed the issue, he/she will change the status to "Test." The reporter will re-test the original feature and change the status to "Done" if satisfied the issue is addressed. If the issue is not satisfactorily addressed, the reporter will change status to open and reassign to the developer.
  
• This QA list should be checked daily by everyone to see what has been assigned to them.