-
Notifications
You must be signed in to change notification settings - Fork 4
/
.env.example
116 lines (95 loc) · 5.57 KB
/
.env.example
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
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
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
# Sample .env file. Copy this to .env and modify as desired. Sample values are defaults, unless
# surrounded by angle brackets. Values in angle brackets are examples and have no default.
##### Timeouts #####
## Helpful for local development. Configure the wait times of timeouts to your needs. All values given in seconds.
## Note: Official timeout settings for the suite set in settings.py - go there if you need to add a new type or length
## of timeout to the suite, to be used in scheduled remote runs of the tests.
# QUICK_TIMEOUT=4
# TIMEOUT=10
# LONG_TIMEOUT=30
# VERY_LONG_TIMEOUT=60
##### Driver config #####
## Which browser/software stack to run the tests under.
## DRIVER: which browser to test in. Valid options are 'Chrome', 'Firefox', 'Edge', Remote'
## 'Chrome' requires that chromedriver is available in $PATH
## 'Firefox' requires that geckodriver is available in $PATH
## 'Edge' requires that msedgedriver is available in $PATH
## 'Remote' will run the tests via BrowserStack
##
## HEADLESS: Should selenium hide the browser gui as the tests are being run?
## True = Hide the gui
## False = Show the gui
## Not relevant when DRIVER=Remote
# DRIVER=Firefox
# HEADLESS=False
## If DRIVER=Remote (will be run on BrowserStack), then the following apply and are MANDATORY.
## TEST_BUILD: This tells BrowserStack which driver to use
## Valid options are 'chrome', 'firefox', or 'edge'
## BSTACK_USER: BrowserStack username
## BSTACK_KEY: BrowserStack api key
# TEST_BUILD=chrome
# BSTACK_USER=<quality-human>
# BSTACK_KEY=<meowmeowmeow>
##### Testing environment #####
## Where to run the tests
## DOMAIN: On what environment will the tests be executed?
## valid options are: 'test', 'stage1', 'stage2', 'stage3', or 'prod'
## note: if you do not select a domain, the default is stage1
## PREFERRED_NODE: When DOMAIN=prod, don't create new projects. Instead, run all tests under
## this guid. MANDATORY if DOMAIN=prod. You must ask QA team for its guid and add it here.
## EXPECTED_PROVIDERS: Only applies when DOMAIN=prod. A comma-separated list of storage
## providers connected to the PREFERRED_NODE.
# DOMAIN=stage1
# PREFERRED_NODE=<mst3k>
# EXPECTED_PROVIDERS=bitbucket,box,dataverse,dropbox,figshare,github,gitlab,googledrive,osfstorage,owncloud,onedrive,s3
##### Fixtures #####
## Users: Need to create two users for testing purposes. Add their logins and passwords here.
## NB!!! In a non-prod environment, all these users' nodes will be deleted during the test.
## DO NOT USE a user with projects you care about.
##
## USER_ONE: Email address of first test user. User must already exist on DOMAIN env.
## USER_ONE_PASSWORD: Password of first test user.
## USER_TWO: Email address of second test user. User must already exist on DOMAIN env.
## USER_TWO_PASSWORD: Password of second test user.
## NEW_USER_EMAIL: Email address used for new user signup. Email should be in the form
## email+{}@gmail.com in order to make unique emails.
## DEACTIVATED_USER: Email address for a user with a deactivated account. Used for CAS testing
## DEACTIVATED_USER_PASSWORD: Password of deactivated user account.
## UNCONFIRMED_USER: Email address for a user with an unconfirmed account. Used for CAS testing
## UNCONFIRMED_USER_PASSWORD: Password of unconfirmed user account.
## CAS_2FA_USER: Email address for a user with 2 factor authentication enabled. Used for CAS testing
## CAS_2FA_USER_PASSWORD: Password of user account with 2 factor authentication enabled.
## CAS_TOS_USER: Email address for a user that has not accepted the OSF terms of service. Used for CAS testing
## CAS_TOS_USER_PASSWORD: Password of user account that has not accepted the OSF terms of service.
## DEVAPP_CLIENT_ID: Client ID for an existing OSF user's Developer App. The client ID is generated by OSF
## when a user creates a Developer App from his/her User Settings page in OSF. The client ID will usually
## be unique for each test environment. Used for CAS oauth testing.
## DEVAPP_CLIENT_SECRET: Client Secret that accompanies the above Client ID for an existing OSF user's Developer
## App. This client secret is also generated by OSF and will also typically be unique in each test environment.
## IMAP_EMAIL: Email address for an IMAP enabled email account - Also an OSF user account
## IMAP_EMAIL_PASSWORD: Password for the IMAP enabled email account. NOT the OSF account password. - With Yahoo
## email it is an app password generated for the account.
## IMAP_HOST: Host email server where the IMAP enabled email account resides.
## A11Y_REGISTRATIONS_USER: Email address for a user that has already created draft registrations in OSF. Used for
## testing the accessibility of various draft registration pages.
## A11Y_REGISTRATIONS_PASSWORD: Password of user that has draft registrations.
# USER_ONE=<foo@example.com>
# USER_ONE_PASSWORD=<i_fear_penguins>
# USER_TWO=<bar@example.com>
# USER_TWO_PASSWORD=<i_fear_polar_beards>
# NEW_USER_EMAIL=<baz+{}@example.com>
# DEACTIVATED_USER=<what@example.com>
# DEACTIVATED_USER_PASSWORD=<who_cares>
# UNCONFIRMED_USER=<ever@example.com>
# UNCONFIRMED_USER_PASSWORD=<why_bother>
# CAS_2FA_USER=<2fa@example.com>
# CAS_2FA_USER_PASSWORD=<extra_step>
# CAS_TOS_USER=<terms_not_germs@example.com>
# CAS_TOS_USER_PASSWORD=<no_terms_no_service>
# DEVAPP_CLIENT_ID=<long_string_of_gibberish>
# DEVAPP_CLIENT_SECRET=<another_long_string_of_gibberish>
# IMAP_EMAIL=<imapexample@yahoo.com>
# IMAP_EMAIL_PASSWORD=<an_app_password_generated_by_yahoo>
# IMAP_HOST=<imap.mail.yahoo.com>
# A11Y_REGISTRATIONS_USER=<registrations@example.com>
# A11Y_REGISTRATIONS_PASSWORD=<i_got_drafts>