Open edX® Palm Test Sheet

	A	B	C
1	Open edX® Testing	COMMUNICATION CHANNELS
2
3
4	Welcome to the community test sheet readme.	Slack:	https://app.slack.com/client/T02SNA1T6/C01AGTSB1LL/thread/C0G15M90X-1644334070.218999
5		Confluence:	https://openedx.atlassian.net/wiki/spaces/COMM/pages/1022099494/Build+-+Test+-+Release+Working+Group
6	ACCESSIBILITY	Discuss:	https://discuss.openedx.org/c/working-groups/build-test-release/30
7	Screen reader support is turned on.
8	Braille support is turned on.
9	Screen magnifier support is turned on.
10		HOW-TO VIDEO
11	TEST INSTANCE ACCESS: MANY THANKS TO THE TEST INSTANCE SPONSOR RÉGIS BEHMO, FOUNDER OF TUTOR	HOW-TO VIDEO
12	The demo platform will be deployed WEEKLY on Mondays at 7am UTC and will be available at: https://apps.palm.demo.overhang.io/ and https://studio.palm.demo.overhang.io/home/. This means the user accounts are wiped weekly, so you may need to re-register your account when the platform redeploys each Monday. The admin and student login details won't change, so use those anytime.	https://www.youtube.com/watch?v=WpNFZbqSkbc
13	The credentials for the superuser/staff account are listed in the project readme. The superuser details are admin@overhang.io with password "admin", and the student details are student@overhang.io with password "student".
14	There is a repository to host the deployment scripts here: https://github.com/overhangio/openedx-release-demo/blob/master/.github/workflows/deploy.ymldemo
15	Changes to the instance configuration can be made as PRs here
16	The SMTP service is enabled, but the server is not configured for email authentication (DKIM, SPF, etc.). This means that emails do get sent, but it's very likely that they will end up in spam, depending on your email client configuration. Just use the Admin account to activate any test accounts you create.
17
18
19	HOW TO USE THE SHEET
20	Step 1: Browse unassigned Test Cases and self-assign from the dropdown list (contact us if your name is not there).
21	Step 2: When you are ready to perform the test, update the Status column to 'In Progress'.
22	Step 3: Perform the test.
23	Step 4: Update the Status column to 'Complete'.
24	Step 5: Update the Result column to 'Passed' or 'Failed'.
25	Step 6: IF test 'Failed', create an issue in the Build-Test-Release GitHub repo and link it in the column. Make sure to add the Test Case ID into GitHub. The correct repo for adding your issues is: https://github.com/openedx/wg-build-test-release/issues. Once created, you should add a label. To add a label you can comment the following string label: palm testing then waiting 10 seconds for the bot to add the label. Here is a good example of a GitHub issue: https://github.com/openedx/build-test-release-wg/issues/222
26	Step 7: IF the GitHub issue is resolved, go back to Step 2 and start the testing process again. It should work this time.
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100