Skip to content

Update TestDrivenDevelopment.rst #29

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Sep 12, 2020
Merged

Update TestDrivenDevelopment.rst #29

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
2d38a6b
Update TestDrivenDevelopment.rst
cohensauw Aug 3, 2020
e8e4a69
Merge branch 'master' into cohensauw-patch-1
PythonCHB Sep 12, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 5 additions & 4 deletions source/modules/TestDrivenDevelopment.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,20 +7,21 @@ FIXME: change the path from my personal to something generic
Test Driven Development
#######################

"Testing" is any strategy for making sure your code behaves as expected. "Unit Testing" is a particular strategy, that:
"Testing" is any strategy for making sure your code behaves as expected. "Unit testing" is a particular strategy, that:

* is easy to run in an automated fashion.
* utilizes isolated tests for each individual function.


"Test Driven Development" (TDD) is a development strategy that integrates the development of unit tests with the code itself. In particular, you write the tests *before* you write the code, which seems pretty backward, but it has some real strengths.

We'll demonstrate this technique with an example.

The Following is adapted from Mark Pilgrim's excellent "Dive into Python":
The following is adapted from Mark Pilgrim's excellent "Dive into Python":

https://diveintopython3.problemsolving.io/

The primary difference is that this version uses the simpler pytest testing framework, rather than `unittest`, which is discussed in:
The primary difference is that this version uses the simpler pytest testing framework, rather than `unittest`, which is discussed in
:ref:`unit_testing`

Unit Testing
Expand Down Expand Up @@ -108,7 +109,7 @@ conversion functions — ``to_roman()``, and later ``from_roman()`` — can
be written and tested as a unit, separate from any larger program that
uses them.

Technically, you can write unit tests with plain Python -- recall the ``assert`` statement that you have already used to write simple tests. But it is very helpful to use a framework to make it easier to write and run your tests. In this program, we use the `pytest` package: it is both very easy to get started with, and provides a lot of powerful features to aide in testing complex systems.
Technically, you can write unit tests with plain Python -- recall the ``assert`` statement that you have already used to write simple tests. But it is very helpful to use a framework to make it easier to write and run your tests. In this program, we use the `pytest` package: it is both very easy to get started with, and provides a lot of powerful features to aid in testing complex systems.

.. note:: ``pytest`` does not come with Python out of the box. But it is easily installable via `pip` (or conda, if you are using conda)::

Expand Down