wordsmithing
This commit is contained in:
@@ -5,7 +5,7 @@ Code Coverage
|
||||
We measure which lines of our codebase are covered by unit tests using
|
||||
`coverage.py`_ for Python and `JSCover`_ for Javascript.
|
||||
|
||||
Our codebase is far from perfect, but the goal is to slowly improve our coverage
|
||||
Our codebase is far from perfect, but the goal is to steadily improve our coverage
|
||||
over time. To do this, we wrote a tool called `diff-cover`_ that will
|
||||
report which lines in your branch are not covered by tests, while ignoring
|
||||
other lines in the project that may not be covered. Using this tool,
|
||||
|
||||
@@ -2,13 +2,13 @@
|
||||
Code Quality
|
||||
************
|
||||
|
||||
In order to keep our codebase as clear and readable as possible, we use various
|
||||
In order to keep our code as clear and readable as possible, we use various
|
||||
tools to assess the quality of pull requests:
|
||||
|
||||
* We use the `pep8`_ tool to follow `PEP-8`_ guidelines
|
||||
* We use `pylint`_ for static analysis and uncovering trouble spots in our code
|
||||
|
||||
Our codebase is far from perfect, but the goal is to slowly improve our quality
|
||||
Our codebase is far from perfect, but the goal is to steadily improve our quality
|
||||
over time. To do this, we wrote a tool called `diff-quality`_ that will
|
||||
only report on the quality violations on lines that have changed in a
|
||||
pull request. Using this tool, we can ensure that pull requests do not introduce
|
||||
|
||||
Reference in New Issue
Block a user