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: .github/ISSUE_TEMPLATE/---report-an-issue.md
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -32,6 +32,10 @@ You may also search through existing issues before opening a new one: https://gi
32
32
33
33
<!--- What is happening instead. --->
34
34
35
+
### Test Case
36
+
37
+
To accurately reproduce your issue. Add your test cases [here](https://github.com/parse-community/Parse-SDK-JS/tree/master/integration/test) and read the [Contributing Guide](https://github.com/parse-community/Parse-SDK-JS/blob/master/CONTRIBUTING.md) to run the tests.
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+3-4Lines changed: 3 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -34,7 +34,7 @@ The Parse JS SDK is built for three platforms:
34
34
- nodejs
35
35
- react-native
36
36
37
-
When developing the SDK you can use `npm run watch` in order to rebuild your changes upon each saves.
37
+
When developing the SDK you can use `npm run watch` in order to rebuild your changes upon each save.
38
38
39
39
By default, the watch command will rebuild the SDK for the browser platform. The following commands will rebuild changes for a specific platform.
40
40
@@ -44,7 +44,7 @@ By default, the watch command will rebuild the SDK for the browser platform. The
44
44
45
45
### Testing the code
46
46
47
-
The SDK is tested through two lenses. unit tests are run with jest and integrationt tests with jasmine.
47
+
The SDK is tested through two lenses. unit tests are run with jest and integration tests with jasmine.
48
48
49
49
Two different frameworks are used as the integration tests leverage a stateful server, with the data saved into the database, and Jest is running many tests in parallel, which makes it incompatible with our integration tests.
50
50
@@ -54,12 +54,11 @@ Those tests are located in [/src/__tests__](/src/__tests__) and are responsible
54
54
55
55
To run unit tests, run `npm test`. If you have the vscode Jest plugin extension (as recommended), you can run your tests by clicking the *Debug* lens that appears near by the test.
56
56
57
-
58
57
#### Integration tests
59
58
60
59
Those tests are located in [/integration/test](/integration/test) and are responsible for ensuring a proper communication with parse-server. With the integration tests, we ensure all communications between the SDK and the server are behaving accordingly.
61
60
62
-
To run the integtation tests, you will need a valid mongodb running on your local machine. You can get easily mongodb running with `mongodb-runner` (see [Recommended setup](#recommended-setup)).
61
+
To run the integration tests, you will need a valid mongodb running on your local machine. You can get easily mongodb running with `mongodb-runner` (see [Recommended setup](#recommended-setup)).
63
62
64
63
Use `npm run integration` in order to run the integration tests. If you have the vscode Jasmine extension installed (as recommended), you can run your tests by clicking the *Run* or the *Debug* lens that appears near by the test.
0 commit comments