Skip to content

Commit c4d6155

Browse files
committed
add new unit test resource
1 parent ed7b4f3 commit c4d6155

File tree

3 files changed

+9
-1
lines changed

3 files changed

+9
-1
lines changed

content/pages/04-web-development/35-testing.markdown

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -157,4 +157,3 @@ use mocks in your test cases.
157157
[Redis](/redis.html)-dependent code but prefer to mock it rather than
158158
ensure an installation and connection are present whenever you run
159159
your tests.
160-

content/pages/04-web-development/36-unit-testing.markdown

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -128,3 +128,12 @@ Python-specific applications.
128128
* [The business case for unit testing](https://www.typemock.com/business-case-unit-testing/)
129129
makes arguments for management should buy into unit testing,
130130
including risk management and faster development timelines.
131+
132+
* Unit testing often requires a bunch of fake data to use as inputs that
133+
otherwise are generated by users or oother parts of a system not
134+
under test. Fake data generation tools can help create data instead
135+
of having too write it all yourself. This post on
136+
[generating fake data with Faker](https://semaphoreci.com/community/tutorials/generating-fake-data-for-python-unit-tests-with-faker)
137+
shows how to use the Faker tool with various seeds and outputs into
138+
your tests.
139+
18.7 KB
Loading

0 commit comments

Comments
 (0)