Skip to content

Commit 2ee1dff

Browse files
committed
DOC: Add reference to crash diagnostics in service testing doc
skipci
1 parent cbc3301 commit 2ee1dff

File tree

2 files changed

+5
-1
lines changed

2 files changed

+5
-1
lines changed

docs/source/testing_services.rst

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -212,7 +212,8 @@ change correspondingly (or at all). So, it's up to you to define a set of realis
212212
the child's twine - this is because the twine is only available to the real child. This is ok - you're testing your
213213
service, not the child.
214214

215-
You can create test fixtures manually or by using the `Child.received_messages` property after questioning a real child.
215+
You can create test fixtures manually or by using the ``Child.received_messages`` property after questioning a real
216+
child.
216217

217218
.. code-block:: python
218219
@@ -260,3 +261,5 @@ You can then feed these into a child emulator to emulate one possible response o
260261
261262
child_emulator.ask(input_values=[1, 2, 3, 4])
262263
>>> {"some": "results"}
264+
265+
You can also create test fixtures from :ref:`downloaded service crash diagnostics <test_fixtures_from_crash_diagnostics>`.

docs/source/troubleshooting_services.rst

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -51,6 +51,7 @@ More information on the command:
5151
manifests to the new local paths.
5252
-h, --help Show this message and exit.
5353
54+
.. _test_fixtures_from_crash_diagnostics:
5455

5556
Creating test fixtures from crash diagnostics
5657
=============================================

0 commit comments

Comments
 (0)