isphinx.addnodesdocument)}( rawsourcechildren]( translations LanguagesNode)}(hhh](h pending_xref)}(hhh]docutils.nodesTextChinese (Simplified)}parenthsba attributes}(ids]classes]names]dupnames]backrefs] refdomainstdreftypedoc reftarget'/translations/zh_CN/dev-tools/kunit/faqmodnameN classnameN refexplicitutagnamehhh ubh)}(hhh]hChinese (Traditional)}hh2sbah}(h]h ]h"]h$]h&] refdomainh)reftypeh+ reftarget'/translations/zh_TW/dev-tools/kunit/faqmodnameN classnameN refexplicituh1hhh ubh)}(hhh]hItalian}hhFsbah}(h]h ]h"]h$]h&] refdomainh)reftypeh+ reftarget'/translations/it_IT/dev-tools/kunit/faqmodnameN classnameN refexplicituh1hhh ubh)}(hhh]hJapanese}hhZsbah}(h]h ]h"]h$]h&] refdomainh)reftypeh+ reftarget'/translations/ja_JP/dev-tools/kunit/faqmodnameN classnameN refexplicituh1hhh ubh)}(hhh]hKorean}hhnsbah}(h]h ]h"]h$]h&] refdomainh)reftypeh+ reftarget'/translations/ko_KR/dev-tools/kunit/faqmodnameN classnameN refexplicituh1hhh ubh)}(hhh]hSpanish}hhsbah}(h]h ]h"]h$]h&] refdomainh)reftypeh+ reftarget'/translations/sp_SP/dev-tools/kunit/faqmodnameN classnameN refexplicituh1hhh ubeh}(h]h ]h"]h$]h&]current_languageEnglishuh1h hh _documenthsourceNlineNubhcomment)}(h SPDX-License-Identifier: GPL-2.0h]h SPDX-License-Identifier: GPL-2.0}hhsbah}(h]h ]h"]h$]h&] xml:spacepreserveuh1hhhhhhA/var/lib/git/docbuild/linux/Documentation/dev-tools/kunit/faq.rsthKubhsection)}(hhh](htitle)}(hFrequently Asked Questionsh]hFrequently Asked Questions}(hhhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhhhhhKubh)}(hhh](h)}(h:How is this different from Autotest, kselftest, and so on?h]h:How is this different from Autotest, kselftest, and so on?}(hhhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhhhhhKubh paragraph)}(hQKUnit is a unit testing framework. Autotest, kselftest (and some others) are not.h]hQKUnit is a unit testing framework. Autotest, kselftest (and some others) are not.}(hhhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhK hhhhubh)}(hXA `unit test `_ is supposed to test a single unit of code in isolation and hence the name *unit test*. A unit test should be the finest granularity of testing and should allow all possible code paths to be tested in the code under test. This is only possible if the code under test is small and does not have any external dependencies outside of the test's control like hardware.h](hA }(hhhhhNhNubh reference)}(h;`unit test `_h]h unit test}(hhhhhNhNubah}(h]h ]h"]h$]h&]name unit testrefuri,https://martinfowler.com/bliki/UnitTest.htmluh1hhhubhtarget)}(h/ h]h}(h] unit-testah ]h"] unit testah$]h&]refurijuh1j referencedKhhubhK is supposed to test a single unit of code in isolation and hence the name }(hhhhhNhNubhemphasis)}(h *unit test*h]h unit test}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1jhhubhX. A unit test should be the finest granularity of testing and should allow all possible code paths to be tested in the code under test. This is only possible if the code under test is small and does not have any external dependencies outside of the test’s control like hardware.}(hhhhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhK hhhhubh)}(hXyThere are no testing frameworks currently available for the kernel that do not require installing the kernel on a test machine or in a virtual machine. All testing frameworks require tests to be written in userspace and run on the kernel under test. This is true for Autotest, kselftest, and some others, disqualifying any of them from being considered unit testing frameworks.h]hXyThere are no testing frameworks currently available for the kernel that do not require installing the kernel on a test machine or in a virtual machine. All testing frameworks require tests to be written in userspace and run on the kernel under test. This is true for Autotest, kselftest, and some others, disqualifying any of them from being considered unit testing frameworks.}(hj4hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhhhhubeh}(h]7how-is-this-different-from-autotest-kselftest-and-so-onah ]h"]:how is this different from autotest, kselftest, and so on?ah$]h&]uh1hhhhhhhhKubh)}(hhh](h)}(h;Does KUnit support running on architectures other than UML?h]h;Does KUnit support running on architectures other than UML?}(hjMhhhNhNubah}(h]h ]h"]h$]h&]uh1hhjJhhhhhKubh)}(h Yes, mostly.h]h Yes, mostly.}(hj[hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjJhhubh)}(hXFor the most part, the KUnit core framework (what we use to write the tests) can compile to any architecture. It compiles like just another part of the kernel and runs when the kernel boots, or when built as a module, when the module is loaded. However, there is infrastructure, like the KUnit Wrapper (``tools/testing/kunit/kunit.py``) that might not support some architectures (see :ref:`kunit-on-qemu`).h](hX0For the most part, the KUnit core framework (what we use to write the tests) can compile to any architecture. It compiles like just another part of the kernel and runs when the kernel boots, or when built as a module, when the module is loaded. However, there is infrastructure, like the KUnit Wrapper (}(hjihhhNhNubhliteral)}(h ``tools/testing/kunit/kunit.py``h]htools/testing/kunit/kunit.py}(hjshhhNhNubah}(h]h ]h"]h$]h&]uh1jqhjiubh1) that might not support some architectures (see }(hjihhhNhNubh)}(h:ref:`kunit-on-qemu`h]hinline)}(hjh]h kunit-on-qemu}(hjhhhNhNubah}(h]h ](xrefstdstd-refeh"]h$]h&]uh1jhjubah}(h]h ]h"]h$]h&]refdocdev-tools/kunit/faq refdomainjreftyperef refexplicitrefwarn reftarget kunit-on-qemuuh1hhhhKhjiubh).}(hjihhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhKhjJhhubh)}(hpIn short, yes, you can run KUnit on other architectures, but it might require more work than using KUnit on UML.h]hpIn short, yes, you can run KUnit on other architectures, but it might require more work than using KUnit on UML.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhK%hjJhhubh)}(h2For more information, see :ref:`kunit-on-non-uml`.h](hFor more information, see }(hjhhhNhNubh)}(h:ref:`kunit-on-non-uml`h]j)}(hjh]hkunit-on-non-uml}(hjhhhNhNubah}(h]h ](jstdstd-refeh"]h$]h&]uh1jhjubah}(h]h ]h"]h$]h&]refdocj refdomainjreftyperef refexplicitrefwarnjkunit-on-non-umluh1hhhhK(hjubh.}(hjhhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhK(hjJhhubj)}(h.. _kinds-of-tests:h]h}(h]h ]h"]h$]h&]refidkinds-of-testsuh1jhK*hjJhhhhubeh}(h]:does-kunit-support-running-on-architectures-other-than-umlah ]h"];does kunit support running on architectures other than uml?ah$]h&]uh1hhhhhhhhKubh)}(hhh](h)}(hDWhat is the difference between a unit test and other kinds of tests?h]hDWhat is the difference between a unit test and other kinds of tests?}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhjhhhhhK-ubh)}(hlMost existing tests for the Linux kernel would be categorized as an integration test, or an end-to-end test.h]hlMost existing tests for the Linux kernel would be categorized as an integration test, or an end-to-end test.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhK.hjhhubh bullet_list)}(hhh](h list_item)}(hX\A unit test is supposed to test a single unit of code in isolation. A unit test should be the finest granularity of testing and, as such, allows all possible code paths to be tested in the code under test. This is only possible if the code under test is small and does not have any external dependencies outside of the test's control like hardware.h]h)}(hX\A unit test is supposed to test a single unit of code in isolation. A unit test should be the finest granularity of testing and, as such, allows all possible code paths to be tested in the code under test. This is only possible if the code under test is small and does not have any external dependencies outside of the test's control like hardware.h]hX^A unit test is supposed to test a single unit of code in isolation. A unit test should be the finest granularity of testing and, as such, allows all possible code paths to be tested in the code under test. This is only possible if the code under test is small and does not have any external dependencies outside of the test’s control like hardware.}(hj2hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhK1hj.ubah}(h]h ]h"]h$]h&]uh1j,hj)hhhhhNubj-)}(hXAn integration test tests the interaction between a minimal set of components, usually just two or three. For example, someone might write an integration test to test the interaction between a driver and a piece of hardware, or to test the interaction between the userspace libraries the kernel provides and the kernel itself. However, one of these tests would probably not test the entire kernel along with hardware interactions and interactions with the userspace.h]h)}(hXAn integration test tests the interaction between a minimal set of components, usually just two or three. For example, someone might write an integration test to test the interaction between a driver and a piece of hardware, or to test the interaction between the userspace libraries the kernel provides and the kernel itself. However, one of these tests would probably not test the entire kernel along with hardware interactions and interactions with the userspace.h]hXAn integration test tests the interaction between a minimal set of components, usually just two or three. For example, someone might write an integration test to test the interaction between a driver and a piece of hardware, or to test the interaction between the userspace libraries the kernel provides and the kernel itself. However, one of these tests would probably not test the entire kernel along with hardware interactions and interactions with the userspace.}(hjJhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhK6hjFubah}(h]h ]h"]h$]h&]uh1j,hj)hhhhhNubj-)}(hXAn end-to-end test usually tests the entire system from the perspective of the code under test. For example, someone might write an end-to-end test for the kernel by installing a production configuration of the kernel on production hardware with a production userspace and then trying to exercise some behavior that depends on interactions between the hardware, the kernel, and userspace. h]h)}(hXAn end-to-end test usually tests the entire system from the perspective of the code under test. For example, someone might write an end-to-end test for the kernel by installing a production configuration of the kernel on production hardware with a production userspace and then trying to exercise some behavior that depends on interactions between the hardware, the kernel, and userspace.h]hXAn end-to-end test usually tests the entire system from the perspective of the code under test. For example, someone might write an end-to-end test for the kernel by installing a production configuration of the kernel on production hardware with a production userspace and then trying to exercise some behavior that depends on interactions between the hardware, the kernel, and userspace.}(hjbhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhK=hj^ubah}(h]h ]h"]h$]h&]uh1j,hj)hhhhhNubeh}(h]h ]h"]h$]h&]bullet-uh1j'hhhK1hjhhubeh}(h](Cwhat-is-the-difference-between-a-unit-test-and-other-kinds-of-testsjeh ]h"](Dwhat is the difference between a unit test and other kinds of tests?kinds-of-testseh$]h&]uh1hhhhhhhhK-expect_referenced_by_name}jjsexpect_referenced_by_id}jjsubh)}(hhh](h)}(h'KUnit is not working, what should I do?h]h'KUnit is not working, what should I do?}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhjhhhhhKDubh)}(h]Unfortunately, there are a number of things which can break, but here are some things to try.h]h]Unfortunately, there are a number of things which can break, but here are some things to try.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKFhjhhubhenumerated_list)}(hhh](j-)}(hRun ``./tools/testing/kunit/kunit.py run`` with the ``--raw_output`` parameter. This might show details or error messages hidden by the kunit_tool parser.h]h)}(hRun ``./tools/testing/kunit/kunit.py run`` with the ``--raw_output`` parameter. This might show details or error messages hidden by the kunit_tool parser.h](hRun }(hjhhhNhNubjr)}(h&``./tools/testing/kunit/kunit.py run``h]h"./tools/testing/kunit/kunit.py run}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1jqhjubh with the }(hjhhhNhNubjr)}(h``--raw_output``h]h --raw_output}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1jqhjubhV parameter. This might show details or error messages hidden by the kunit_tool parser.}(hjhhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhKIhjubah}(h]h ]h"]h$]h&]uh1j,hjhhhhhNubj-)}(hX(Instead of running ``kunit.py run``, try running ``kunit.py config``, ``kunit.py build``, and ``kunit.py exec`` independently. This can help track down where an issue is occurring. (If you think the parser is at fault, you can run it manually against ``stdin`` or a file with ``kunit.py parse``.)h]h)}(hX(Instead of running ``kunit.py run``, try running ``kunit.py config``, ``kunit.py build``, and ``kunit.py exec`` independently. This can help track down where an issue is occurring. (If you think the parser is at fault, you can run it manually against ``stdin`` or a file with ``kunit.py parse``.)h](hInstead of running }(hjhhhNhNubjr)}(h``kunit.py run``h]h kunit.py run}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1jqhjubh, try running }(hjhhhNhNubjr)}(h``kunit.py config``h]hkunit.py config}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1jqhjubh, }(hjhhhNhNubjr)}(h``kunit.py build``h]hkunit.py build}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1jqhjubh, and }(hjhhhNhNubjr)}(h``kunit.py exec``h]h kunit.py exec}(hj-hhhNhNubah}(h]h ]h"]h$]h&]uh1jqhjubh independently. This can help track down where an issue is occurring. (If you think the parser is at fault, you can run it manually against }(hjhhhNhNubjr)}(h ``stdin``h]hstdin}(hj?hhhNhNubah}(h]h ]h"]h$]h&]uh1jqhjubh or a file with }(hjhhhNhNubjr)}(h``kunit.py parse``h]hkunit.py parse}(hjQhhhNhNubah}(h]h ]h"]h$]h&]uh1jqhjubh.)}(hjhhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhKLhjubah}(h]h ]h"]h$]h&]uh1j,hjhhhhhNubj-)}(hXRunning the UML kernel directly can often reveal issues or error messages, ``kunit_tool`` ignores. This should be as simple as running ``./vmlinux`` after building the UML kernel (for example, by using ``kunit.py build``). Note that UML has some unusual requirements (such as the host having a tmpfs filesystem mounted), and has had issues in the past when built statically and the host has KASLR enabled. (On older host kernels, you may need to run ``setarch `uname -m` -R ./vmlinux`` to disable KASLR.)h]h)}(hXRunning the UML kernel directly can often reveal issues or error messages, ``kunit_tool`` ignores. This should be as simple as running ``./vmlinux`` after building the UML kernel (for example, by using ``kunit.py build``). Note that UML has some unusual requirements (such as the host having a tmpfs filesystem mounted), and has had issues in the past when built statically and the host has KASLR enabled. (On older host kernels, you may need to run ``setarch `uname -m` -R ./vmlinux`` to disable KASLR.)h](hKRunning the UML kernel directly can often reveal issues or error messages, }(hjshhhNhNubjr)}(h``kunit_tool``h]h kunit_tool}(hj{hhhNhNubah}(h]h ]h"]h$]h&]uh1jqhjsubh. ignores. This should be as simple as running }(hjshhhNhNubjr)}(h ``./vmlinux``h]h ./vmlinux}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1jqhjsubh6 after building the UML kernel (for example, by using }(hjshhhNhNubjr)}(h``kunit.py build``h]hkunit.py build}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1jqhjsubh). Note that UML has some unusual requirements (such as the host having a tmpfs filesystem mounted), and has had issues in the past when built statically and the host has KASLR enabled. (On older host kernels, you may need to run }(hjshhhNhNubjr)}(h#``setarch `uname -m` -R ./vmlinux``h]hsetarch `uname -m` -R ./vmlinux}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1jqhjsubh to disable KASLR.)}(hjshhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhKPhjoubah}(h]h ]h"]h$]h&]uh1j,hjhhhhhNubj-)}(hX}Make sure the kernel .config has ``CONFIG_KUNIT=y`` and at least one test (e.g. ``CONFIG_KUNIT_EXAMPLE_TEST=y``). kunit_tool will keep its .config around, so you can see what config was used after running ``kunit.py run``. It also preserves any config changes you might make, so you can enable/disable things with ``make ARCH=um menuconfig`` or similar, and then re-run kunit_tool.h]h)}(hX}Make sure the kernel .config has ``CONFIG_KUNIT=y`` and at least one test (e.g. ``CONFIG_KUNIT_EXAMPLE_TEST=y``). kunit_tool will keep its .config around, so you can see what config was used after running ``kunit.py run``. It also preserves any config changes you might make, so you can enable/disable things with ``make ARCH=um menuconfig`` or similar, and then re-run kunit_tool.h](h!Make sure the kernel .config has }(hjhhhNhNubjr)}(h``CONFIG_KUNIT=y``h]hCONFIG_KUNIT=y}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1jqhjubh and at least one test (e.g. }(hjhhhNhNubjr)}(h``CONFIG_KUNIT_EXAMPLE_TEST=y``h]hCONFIG_KUNIT_EXAMPLE_TEST=y}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1jqhjubh^). kunit_tool will keep its .config around, so you can see what config was used after running }(hjhhhNhNubjr)}(h``kunit.py run``h]h kunit.py run}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1jqhjubh]. It also preserves any config changes you might make, so you can enable/disable things with }(hjhhhNhNubjr)}(h``make ARCH=um menuconfig``h]hmake ARCH=um menuconfig}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1jqhjubh( or similar, and then re-run kunit_tool.}(hjhhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhKWhjubah}(h]h ]h"]h$]h&]uh1j,hjhhhhhNubj-)}(hTry to run ``make ARCH=um defconfig`` before running ``kunit.py run``. This may help clean up any residual config items which could be causing problems.h]h)}(hTry to run ``make ARCH=um defconfig`` before running ``kunit.py run``. This may help clean up any residual config items which could be causing problems.h](h Try to run }(hj3hhhNhNubjr)}(h``make ARCH=um defconfig``h]hmake ARCH=um defconfig}(hj;hhhNhNubah}(h]h ]h"]h$]h&]uh1jqhj3ubh before running }(hj3hhhNhNubjr)}(h``kunit.py run``h]h kunit.py run}(hjMhhhNhNubah}(h]h ]h"]h$]h&]uh1jqhj3ubhS. This may help clean up any residual config items which could be causing problems.}(hj3hhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhK]hj/ubah}(h]h ]h"]h$]h&]uh1j,hjhhhhhNubj-)}(hXFinally, try running KUnit outside UML. KUnit and KUnit tests can be built into any kernel, or can be built as a module and loaded at runtime. Doing so should allow you to determine if UML is causing the issue you're seeing. When tests are built-in, they will execute when the kernel boots, and modules will automatically execute associated tests when loaded. Test results can be collected from ``/sys/kernel/debug/kunit//results``, and can be parsed with ``kunit.py parse``. For more details, see :ref:`kunit-on-qemu`. h]h)}(hXFinally, try running KUnit outside UML. KUnit and KUnit tests can be built into any kernel, or can be built as a module and loaded at runtime. Doing so should allow you to determine if UML is causing the issue you're seeing. When tests are built-in, they will execute when the kernel boots, and modules will automatically execute associated tests when loaded. Test results can be collected from ``/sys/kernel/debug/kunit//results``, and can be parsed with ``kunit.py parse``. For more details, see :ref:`kunit-on-qemu`.h](hXFinally, try running KUnit outside UML. KUnit and KUnit tests can be built into any kernel, or can be built as a module and loaded at runtime. Doing so should allow you to determine if UML is causing the issue you’re seeing. When tests are built-in, they will execute when the kernel boots, and modules will automatically execute associated tests when loaded. Test results can be collected from }(hjohhhNhNubjr)}(h0``/sys/kernel/debug/kunit//results``h]h,/sys/kernel/debug/kunit//results}(hjwhhhNhNubah}(h]h ]h"]h$]h&]uh1jqhjoubh, and can be parsed with }(hjohhhNhNubjr)}(h``kunit.py parse``h]hkunit.py parse}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1jqhjoubh. For more details, see }(hjohhhNhNubh)}(h:ref:`kunit-on-qemu`h]j)}(hjh]h kunit-on-qemu}(hjhhhNhNubah}(h]h ](jstdstd-refeh"]h$]h&]uh1jhjubah}(h]h ]h"]h$]h&]refdocj refdomainjreftyperef refexplicitrefwarnj kunit-on-qemuuh1hhhhK_hjoubh.}(hjohhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhK_hjkubah}(h]h ]h"]h$]h&]uh1j,hjhhhhhNubeh}(h]h ]h"]h$]h&]enumtypearabicprefixhsuffix.uh1jhjhhhhhKIubh)}(hkIf none of the above tricks help, you are always welcome to email any issues to kunit-dev@googlegroups.com.h](hPIf none of the above tricks help, you are always welcome to email any issues to }(hjhhhNhNubh)}(hkunit-dev@googlegroups.comh]hkunit-dev@googlegroups.com}(hjhhhNhNubah}(h]h ]h"]h$]h&]refuri!mailto:kunit-dev@googlegroups.comuh1hhjubh.}(hjhhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhKghjhhubeh}(h]%kunit-is-not-working-what-should-i-doah ]h"]'kunit is not working, what should i do?ah$]h&]uh1hhhhhhhhKDubeh}(h]frequently-asked-questionsah ]h"]frequently asked questionsah$]h&]uh1hhhhhhhhKubeh}(h]h ]h"]h$]h&]sourcehuh1hcurrent_sourceN current_lineNsettingsdocutils.frontendValues)}(hN generatorN datestampN source_linkN source_urlN toc_backlinksentryfootnote_backlinksK sectnum_xformKstrip_commentsNstrip_elements_with_classesN strip_classesN report_levelK halt_levelKexit_status_levelKdebugNwarning_streamN tracebackinput_encoding utf-8-siginput_encoding_error_handlerstrictoutput_encodingutf-8output_encoding_error_handlerj+error_encodingutf-8error_encoding_error_handlerbackslashreplace language_codeenrecord_dependenciesNconfigN id_prefixhauto_id_prefixid dump_settingsNdump_internalsNdump_transformsNdump_pseudo_xmlNexpose_internalsNstrict_visitorN_disable_configN_sourceh _destinationN _config_files]7/var/lib/git/docbuild/linux/Documentation/docutils.confafile_insertion_enabled raw_enabledKline_length_limitM'pep_referencesN pep_base_urlhttps://peps.python.org/pep_file_url_templatepep-%04drfc_referencesN rfc_base_url&https://datatracker.ietf.org/doc/html/ tab_widthKtrim_footnote_reference_spacesyntax_highlightlong smart_quotessmartquotes_locales]character_level_inline_markupdoctitle_xform docinfo_xformKsectsubtitle_xform image_loadinglinkembed_stylesheetcloak_email_addressessection_self_linkenvNubreporterNindirect_targets]substitution_defs}substitution_names}refnames}refids}j]jasnameids}(jjjGjDjjjjjjjjjju nametypes}(jjGjjjjjuh}(jhjDhjjjjJjjjjjju footnote_refs} citation_refs} autofootnotes]autofootnote_refs]symbol_footnotes]symbol_footnote_refs] footnotes] citations]autofootnote_startKsymbol_footnote_startK id_counter collectionsCounter}Rparse_messages]transform_messages]hsystem_message)}(hhh]h)}(hhh]h4Hyperlink target "kinds-of-tests" is not referenced.}hjsbah}(h]h ]h"]h$]h&]uh1hhjubah}(h]h ]h"]h$]h&]levelKtypeINFOsourcehlineK*uh1juba transformerN include_log] decorationNhhub.