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
#. make your changes in `.moban.d` directory, then issue command `moban`
207
+
As to rnd_requirements.txt, usually, it is created when a dependent
208
+
library is not released. Once the dependecy is installed
209
+
(will be released), the future
210
+
version of the dependency in the requirements.txt will be valid.
172
211
173
-
What is rnd_requirements.txt
174
-
-------------------------------
175
212
176
-
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.
213
+
How to test your contribution
214
+
------------------------------
215
+
216
+
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.
217
+
218
+
On Linux/Unix systems, please launch your tests like this::
219
+
220
+
$ make
221
+
222
+
On Windows systems, please issue this command::
223
+
224
+
> test.bat
225
+
226
+
How to update test environment and update documentation
#. make your changes in `.moban.d` directory, then issue command `moban`
177
234
178
235
What is pyexcel-commons
179
236
---------------------------------
@@ -185,18 +242,16 @@ What is .moban.d
185
242
186
243
`.moban.d` stores the specific meta data for the library.
187
244
188
-
How to test your contribution
189
-
------------------------------
190
-
191
-
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.
245
+
Acceptance criteria
246
+
-------------------
192
247
193
-
On Linux/Unix systems, please launch your tests like this::
194
-
195
-
$ make test
248
+
#. Has Test cases written
249
+
#. Has all code lines tested
250
+
#. Passes all Travis CI builds
251
+
#. Has fair amount of documentation if your change is complex
0 commit comments