You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: TESTING.md
+12-12Lines changed: 12 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,23 +3,23 @@
3
3
We use [Spek](https://github.com/spekframework/spek) to run unit tests. You must add Maven Central to the gradle repositories
4
4
in order to pull Spek.
5
5
6
-
To run **only** public endpoint tests, run
6
+
To run any test, you must have two environment variables, `SPOTIFY_CLIENT_ID` and `SPOTIFY_CLIENT_SECRET` set to a Spotify application in your current shell.
7
7
8
-
`gradle test -PclientId=YOUR_CLIENT_ID -PclientSecret=YOUR_CLIENT_SECRET`
8
+
To run **only** public endpoint and utility tests, run `gradle check`
9
9
10
-
To run **all** tests, you need a valid Spotify application, redirect uri, and token string. use:
10
+
To run **all** tests, you need a valid Spotify redirect uri, and token (string). These are `SPOTIFY_REDIRECT_URI` and `SPOTIFY_TOKEN_STRING` respectively.
11
11
12
-
`gradle test -PclientId=YOUR_CLIENT_ID -PclientSecret=YOUR_CLIENT_SECRET -PspotifyRedirectUri=SPOTIFY_REDIRECT_URI -PspotifyTokenString=SPOTIFY_TOKEN`
12
+
Then: `gradle check`
13
13
14
14
Some tests may fail if you do not allow access to all required scopes. To mitigate this, you can individually grant
15
15
each scope or use the following code snippet to print out the Spotify token string (given a generated authorization code)
0 commit comments