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
@@ -136,19 +152,39 @@ Then install relevant development requirements:
136
152
#. pip install -r requirements.txt
137
153
#. pip install -r tests/requirements.txt
138
154
155
+
Once you have finished your changes, please provide test case(s), relevant documentation
156
+
and update CHANGELOG.rst.
157
+
158
+
.. note::
159
+
160
+
As to rnd_requirements.txt, usually, it is created when a dependent
161
+
library is not released. Once the dependecy is installed
162
+
(will be released), the future
163
+
version of the dependency in the requirements.txt will be valid.
139
164
140
-
In order to update test environment, and documentation, additional steps are
141
-
required:
165
+
166
+
How to test your contribution
167
+
------------------------------
168
+
169
+
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.
170
+
171
+
On Linux/Unix systems, please launch your tests like this::
172
+
173
+
$ make
174
+
175
+
On Windows systems, please issue this command::
176
+
177
+
> test.bat
178
+
179
+
How to update test environment and update documentation
#. make your changes in `.moban.d` directory, then issue command `moban`
146
187
147
-
What is rnd_requirements.txt
148
-
-------------------------------
149
-
150
-
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.
151
-
152
188
What is pyexcel-commons
153
189
---------------------------------
154
190
@@ -159,28 +195,18 @@ What is .moban.d
159
195
160
196
`.moban.d` stores the specific meta data for the library.
161
197
162
-
How to test your contribution
163
-
------------------------------
164
-
165
-
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.
166
-
167
-
On Linux/Unix systems, please launch your tests like this::
168
-
169
-
$ make
198
+
Acceptance criteria
199
+
-------------------
170
200
171
-
On Windows systems, please issue this command::
201
+
#. Has Test cases written
202
+
#. Has all code lines tested
203
+
#. Passes all Travis CI builds
204
+
#. Has fair amount of documentation if your change is complex
0 commit comments