GDT Testing Programme: Quick Reference

What testers should do

1. Open /guide/ and choose the Student or Organization guide.
2. Use a ready-made account when you need populated schedules, memberships, events, attendance, and feedback data.
3. Follow the guide's short task flow. Test only the features relevant to you; no feature must be scored if it was not used.
4. Report a single problem at /feedback/ immediately, or submit the complete scorecard at /feedback/rate/ when finished.

Demo accounts

• Student: demo_student
• Officer: demo_officer
• Second member: demo_member

Each uses the same password shown on the Guides page. Choosing its Sign in link fills both fields; the tester still presses Login.

All three start with the same 11-class private test schedule, so nobody needs to import an .ics file before trying Schedule, Smart Search, or AI Plan. demo_officer is the active owner of the demo organization. demo_student and demo_member are active members with Member Cards, so testers can switch between the organization workspace and the student/member experience.

What is included

• The student demo covers schedule-aware search, AI Plan, restaurant preferences, deals, events, organization membership, and a Member Card.
• The officer demo covers organization profile and members, card issuing, member deals, event setup, QR/scanner check-in, attendance, feedback forms, reports, exports, posts, and email.
• Demo event data includes an upcoming RSVP event, a live check-in case, and completed attendance/feedback records for report testing.

How feedback is used

Quick report (/feedback/) is for one concrete issue. Ask for the page/function, task, actual result, expected result, and optional contact information.

Scorecard (/feedback/rate/) is for overall evaluation. Ratings are optional; comments, especially on low scores, identify what should be fixed.

Team review routine

1. Weekly: review new quick reports, group duplicates, set status (triaged, planned, shipped, or not planned), and contact reporters only when needed.
2. Monthly: export feature-score averages, look first at low-rated functions with enough responses, then read their comments alongside activity data.
3. Keep demo accounts clearly labelled and do not treat their activity as real user research.

Extending the programme

When adding a feature, add it once to the appropriate quick guide, add a scorecard row if it needs evaluation, seed demo data when a blank account cannot demonstrate it, and verify the report/export path if it creates organization data.