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: CHANGELOG.md
+2
Original file line number
Diff line number
Diff line change
@@ -114,6 +114,8 @@ ___
114
114
- Allow Cloud Validator `options` to be async (dblythy) [#7155](https://github.com/parse-community/parse-server/pull/7155)
115
115
- Optimize queries on classes with pointer permissions (Pedro Diaz) [#7061](https://github.com/parse-community/parse-server/pull/7061)
116
116
- Test Parse Server continuously against all relevant Postgres versions (minor versions), added Postgres compatibility table to Parse Server docs (Corey Baker) [#7176](https://github.com/parse-community/parse-server/pull/7176)
117
+
- Randomize test suite (Diamond Lewis) [#7265](https://github.com/parse-community/parse-server/pull/7265)
118
+
- LDAP: Properly unbind client on group search error (Diamond Lewis) [#7265](https://github.com/parse-community/parse-server/pull/7265)
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+9
Original file line number
Diff line number
Diff line change
@@ -84,6 +84,14 @@ Once you have babel running in watch mode, you can start making changes to parse
84
84
* All the tests should point to sources in the `lib/` folder.
85
85
* The `lib/` folder is produced by `babel` using either the `npm run build`, `npm run watch`, or the `npm run prepare` step.
86
86
* The `npm run prepare` step is automatically invoked when your package depends on forked parse-server installed via git for example using `npm install --save git+https://github.com/[username]/parse-server#[branch/commit]`.
87
+
* The tests are run against a single server instance. You can change the server configurations using `await reconfigureServer({ ... some configuration })` found in `spec/helper.js`.
88
+
* The tests are ran at random.
89
+
* Caches and Configurations are reset after every test.
90
+
* Users are logged out after every test.
91
+
* Cloud Code hooks are removed after every test.
92
+
* Database is deleted after every test (indexes are not removed for speed)
93
+
* Tests are located in the `spec` folder
94
+
* For better test reporting enable `PARSE_SERVER_LOG_LEVEL=debug`
87
95
88
96
### Troubleshooting
89
97
@@ -108,6 +116,7 @@ Once you have babel running in watch mode, you can start making changes to parse
108
116
* Run the tests for the whole project to make sure the code passes all tests. This can be done by running the test command for a single file but removing the test file argument. The results can be seen at *<PROJECT_ROOT>/coverage/lcov-report/index.html*.
109
117
* Lint your code by running `npm run lint` to make sure the code is not going to be rejected by the CI.
110
118
***Do not** publish the *lib* folder.
119
+
* Mocks belong in the `spec/support` folder.
111
120
* Please consider if any changes to the [docs](http://docs.parseplatform.org) are needed or add additional sections in the case of an enhancement or feature.
0 commit comments