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
@@ -190,19 +200,39 @@ Then install relevant development requirements:
190
200
#. pip install -r requirements.txt
191
201
#. pip install -r tests/requirements.txt
192
202
203
+
Once you have finished your changes, please provide test case(s), relevant documentation
204
+
and update CHANGELOG.rst.
205
+
206
+
.. note::
207
+
208
+
As to rnd_requirements.txt, usually, it is created when a dependent
209
+
library is not released. Once the dependecy is installed
210
+
(will be released), the future
211
+
version of the dependency in the requirements.txt will be valid.
212
+
213
+
214
+
How to test your contribution
215
+
------------------------------
216
+
217
+
Although `nose` and `doctest` are both used in code testing, it is adviable that unit tests are put in tests. `doctest` is incorporated only to make sure the code examples in documentation remain valid across different development releases.
218
+
219
+
On Linux/Unix systems, please launch your tests like this::
220
+
221
+
$ make
222
+
223
+
On Windows systems, please issue this command::
224
+
225
+
> test.bat
226
+
227
+
How to update test environment and update documentation
#. make your changes in `.moban.d` directory, then issue command `moban`
200
235
201
-
What is rnd_requirements.txt
202
-
-------------------------------
203
-
204
-
Usually, it is created when a dependent library is not released. Once the dependecy is installed(will be released), the future version of the dependency in the requirements.txt will be valid.
205
-
206
236
What is pyexcel-commons
207
237
---------------------------------
208
238
@@ -213,18 +243,16 @@ What is .moban.d
213
243
214
244
`.moban.d` stores the specific meta data for the library.
215
245
216
-
How to test your contribution
217
-
------------------------------
246
+
Acceptance criteria
247
+
-------------------
218
248
219
-
Although `nose` and `doctest` are both used in code testing, it is adviable that unit tests are put in tests. `doctest` is incorporated only to make sure the code examples in documentation remain valid across different development releases.
220
-
221
-
On Linux/Unix systems, please launch your tests like this::
249
+
#. Has Test cases written
250
+
#. Has all code lines tested
251
+
#. Passes all Travis CI builds
252
+
#. Has fair amount of documentation if your change is complex
0 commit comments