ABCDEFGHIJKLMNOPQRST
1
Test Case:TC-UC-01 From Issuer site, user pushes badge to Mozilla backpack, customizes badge backpack interface and shares out a group to display badges publicly
2
Description:After earning a badge from issuer site, enable user to select to push earned badge into Mozilla badge backpack. Allow user to configure the backpack and manage badges earned and display them publicly.
3
Primary Actors:User, SystemExecuted By:
4
Preconditions:- User has earned a badge from issuer site/organization
- Issuer is OBI compliant		Date Executed:
5
Setup:User goes to OBI compliant issuer site, earns badge, issuer presents user with option to continue earning badges or push earned badge into Mozilla backpack.
6
Other:Try on all major browsers: FF, Chrome, Safari, IE?
7
8
TC-UC-01-MainProcedure / InputsExpected ResultsPass/Fail
9
0. From OBI compliant issuer site, user selects to push earned badge into Mozilla backpackPresentation of options may vary according to issuer. Likely a button option available with earned badge that communicates that user may push badge to Mozilla backpack. User selects/pushes this button option. Some message indicating user is being redirected to beta.openbadges.org along with progress indicator, after which beta.openbadges.org sign in page is displayed.
10
1. System serves beta.openbadges.org
11
2. User selects to sign inUser pushes sign in button
12
3. User inputs email addressThis is to associate email to backpack for first time user. User provides Persona product with their email.
13
4. System displays disclaimer information related to user's email as well as use of Mozilla's Persona product
14
5. System presents user's authenticated backpack ghosted with popup of information of earned badge that has yet to be added to backpack. User has option to accept or reject badge.
15
6. User selects to accept badge into backpackNewly earned badge displayed in user's backpack
16
7. User's backpack has newly earned badge displayed
17
8. User clicks earned badge to view properties (metadata spec of badge earned)Popup overlay of badge-specific metadata displays
18
9. User changes, adds, deletes appearance properties (eg create group, name group, delete group)UI adjusts accordingly
19
10. User selects to upload badge directly into badge backpack
20
11. User clicks on Help:On button to view tooltips associated with backpack management featuresTooltips overlay ontop of badge interface
21
12. User sets privacy controls for groups (clicks "make public" checkbox to make group public or omits checking box to keep private)How do we test this? Is there a URL?
22
13. User makes group shareable (distinct from public) by selecting share optionWhen users select share, they are not changing the privacy control of that group from public to private. Rather simply making that group shareable.
23
24
TC-UC-01-01Procedure / InputsExpected ResultsPass/Fail
25
3.a. First time backpack creation for user (inputting of user email is to create backpack and associate that backpack with an identity, in the form of an email)User inputs the email they would like associated with their backpackSystem ties that user email identity to their backpack
26
1. System serves Persona browserID protocol
27
2. User inputs email
28
3. System displays disclaimer information related to user's email as well as Mozilla's Persona product
29
4. System by way of browserID serves SMTP challenge
30
5. User goes to personal email account to click on link in email received to verify email address
31
6. Continue at step 5 above in TC-UC-01-Main
32
33
TC-UC-01-02Procedure / InputsExpected ResultsPass/Fail
34
3.b. First time backpack creation for user (inputting of user email is to create backpack and associate that backpack with an identity, in the form of the email)
35
1. System serves Persona browserID protocol
36
2. User cancels out of browserID protocolPopup closes. User is back at issuer site.
37
38
TC-UC-01-03Procedure / InputsExpected ResultsPass/Fail
39
6.a. User selects to reject earned badgeBackpack should not display rejected badge.
40
1. System serves user's authenticated backpack without that rejected badge
41
2. Continue at step 9 in TC-UC-01-Main
42
43
TC-UC-01-04Procedure / InputsExpected ResultsPass/Fail
44
9.a. User creates a new group
45
1. User drags a badge into a group boxNew group formed with user-dragged badge residing inside
46
2. User names the group Group name updated
47
48
TC-UC-01-05Procedure / InputsExpected ResultsPass/Fail
49
9.b. User deletes a group
50
1. User hits the "x" (delete button) at the corner of a created group
51
2. System prompts user if they are sure they want to delete that group
52
3.1. User selects yes to delete groupGroup is deleted and gone from backpack management interface
53
3.2. User selects no to cancel out of deleting that groupGroup persists on backpack management interface
54
2. System deletes groupGroup is deleted and gone from backpack management interface
55
56
TC-UC-01-06Procedure / InputsExpected ResultsPass/Fail
57
10.a. User selects to upload an OBI compliant badge directly into backpack
58
1. User hits choose file button
59
2. System serves user's desktop file folder
60
3. User selects file they want to upload into backpackn.b. badge must be an OBI compliant badge
61
4. User hits upload buttonUploaded badge appears among user's badges
62
63
TC-UC-01-07Procedure / InputsExpected ResultsPass/Fail
64
10.b. User selects to upload a badge that is not OBI compliant directly into backpack
65
1. User hits choose file button
66
2. System serves user's desktop file folder
67
3. User selects file they want to upload into backpackn.b. badge must not be an OBI compliant badge
68
4. User hits upload buttonBadge does not upload
69
5. System generates error message with explanation textSystem is unable to display non-OBI complaint badges in the backpack. Generates error message
70
71
TC-UC-01-08Procedure / InputsExpected ResultsPass/Fail
72
13.a. User makes group shareable by selecting share option
73
1. User hits the share icon
74
2. User names groupIs this optional like the sub-title field? Currently, user is able to save portfolio page without naming group
75
3. User inputs optional sub-titleThis is optional
76
4. User hits save this page button
77
5. User selects to tweet portfolio page out by hitting the tweet button
78
6. System serves popup prompting user to login to their twitter account
79
7. User logs in to their twitter account
80
8. System serves edit-able pre-canned tweet message
81
9. User hits tweet button
82
10. System aggregates tweet number on backpackCurrently, backpack does not appear to be aggregating tweet number
83
11. Tweet goes out to user's network of followers
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100