Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
77e9886
commit 0897516
Showing
5 changed files
with
61 additions
and
12 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,9 @@ | ||
Changelog | ||
========= | ||
|
||
0.1.0 | ||
----- | ||
|
||
- First version of the library | ||
- All methods from the SPTrans API implemented | ||
- Some documentation is still under development |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,40 @@ | ||
Contributing | ||
============ | ||
|
||
First of all, take a look at the repository `here <https://github.com/diogobaeder/sptrans>`_. | ||
|
||
You may have noticed that there are two images in the README: | ||
one that tells the status of the build (via Continuous Integration in `travis-ci <https://travis-ci.org/diogobaeder/sptrans>`_) | ||
and another that tells the code coverage in `coveralls <https://coveralls.io/r/diogobaeder/sptrans>`_. | ||
|
||
This is because I'm a bit obsessive with automated tests, and though I don't think 100% code coverage makes a program free of bugs, | ||
it does a great job getting as close as possible to this achievement. | ||
|
||
By the way, the build doesn't even pass if the production code is not fully covered, so if you want to contribute with it, please | ||
also add some tests. | ||
|
||
Setting up the environment | ||
-------------------------- | ||
|
||
1. Make sure you have pip, virtualenv and virtualenvwrapper installed. OK, all of these are optional, but it would be a nice moment | ||
for you to start using them if you haven't yet; | ||
|
||
2. Create a virtual environment for the project, and activate it; | ||
|
||
3. Install the requirements for running the tests: | ||
|
||
.. code-block:: bash | ||
$ pip install -r requirements.txt | ||
4. Run the tests: | ||
|
||
.. code-block:: bash | ||
$ tox | ||
Optionally, you can run the tests with an SPTrans API token, so that the functional tests are also run: | ||
|
||
.. code-block:: bash | ||
$ SPTRANS_TOKEN=this-is-my-token tox |
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters