From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 3F9DB46B90; Wed, 16 Jul 2025 20:26:05 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 446FC40655; Wed, 16 Jul 2025 20:25:54 +0200 (CEST) Received: from mail-qv1-f49.google.com (mail-qv1-f49.google.com [209.85.219.49]) by mails.dpdk.org (Postfix) with ESMTP id 1D62640657 for ; Wed, 16 Jul 2025 20:25:53 +0200 (CEST) Received: by mail-qv1-f49.google.com with SMTP id 6a1803df08f44-6fafdd322d3so2701356d6.3 for ; Wed, 16 Jul 2025 11:25:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iol.unh.edu; s=unh-iol; t=1752690352; x=1753295152; darn=dpdk.org; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:date:subject:cc:to:from:from:to:cc:subject:date :message-id:reply-to; bh=BM/UYEIDW/dzawxO1rlWiBAzJe8Tk9EtPBh7NaihAoo=; b=ahKmlEiua6W5mS8iEqX0XKO4+aMFxuBerL+KfdhbsJGudLhCcN3Xxcs0R+xOOnj5bN veeLQ8mBnIPjB5hxxpuN3bDZcvBHhpflWT2CXXKPgGpE2odffu+r06kuW0PclZtyb+iH eNSutpsm8+slufLrlLXSH5DNupQNOgAZoPqcM= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1752690352; x=1753295152; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:date:subject:cc:to:from:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=BM/UYEIDW/dzawxO1rlWiBAzJe8Tk9EtPBh7NaihAoo=; b=DUcohOrO7gihVst/e49UYL2J9uUji+0+PozMNKeCZfCqo73/CBlpdOVIJeeRCZQWgP vGty+sJWc4YRZQyys4d084JbM+ow16YMBB80e76gwj+dH8yXXG9/fzY7LVxFp9jCb0rF 23dBq7pLo3GZMdbI65nAVZy73GkRI/oPRsdDx9s5tqfpMsKmVFhRItZORvFizXSVFNLL Okyhv7KVMFs56HK5+gPMG1M7866jV4B9LkRY4WODIX+rMiQ53GWWCWUsMSq5qnpYbR5F gyNf8Xu9l08F1Vlcy74Y+U+0wXw60fikbv+2Ij0mEJbjV+GVktqrGEbz66o9xrakZQV5 9Klg== X-Gm-Message-State: AOJu0YzOQ0dSmSNjS8qUjtWKoJEl0ExZ3dXT0Dg7wqPlGwCMBXBdgDXl j2+rT1C2T9QOguriS0sGRwY7JVcXFtvXt+IP0QUmCQgwT6SzYyu+aajX5IlUpapDx3jjdkvgSl4 UztkH X-Gm-Gg: ASbGnctX06dQXJEaYgMAiRpRdtetxP/M7IWm3bAeCyDV31JuttFKWhntiNszBOhK75n /Uc+D8IREs/MLcGXo+zXGA1aD5AJRflliQQYbkQ9mxzfdncb8z2l9FS7w7P65rDAPIiF46s+dMV fkJvjQRyIXAVxtqD/RJ6g7y+ciA4ffR5J8InpTwWQDl/AkhVSG6ytRXrOuSWFuUoavz6tyENA4u GKKnql8n7pr5x2si7vENquSklrQv5RF3vWPIWzwAym7ou/NwCMDfVvlxCZVkjF1YF7OeuQvlYx/ vOKeemXe46Y2ZUeD3Pih+hjeCcgET4fhDR6nYFPV1txDnInWI7cVlD2rZ0EWA8wMvNIbqxxImPO 8y4xqvPqUvtvbopVc623ibXs3r8wIyQqL7/iq1pVHZRw9yC5138jV X-Google-Smtp-Source: AGHT+IFJAQImYkkhx0hUrmFUt8SrJrutbQpcxR8T+qFeeHMurXdL9XYDWxYYjXki6AqtXJSdWnCddw== X-Received: by 2002:a05:6214:800e:b0:705:3a1:2c33 with SMTP id 6a1803df08f44-70503a13362mr13823686d6.31.1752690351947; Wed, 16 Jul 2025 11:25:51 -0700 (PDT) Received: from fedora.iol.unh.edu ([132.177.125.216]) by smtp.gmail.com with ESMTPSA id d75a77b69052e-4ab70bc9e76sm33495321cf.64.2025.07.16.11.25.51 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 16 Jul 2025 11:25:51 -0700 (PDT) From: Dean Marx To: probb@iol.unh.edu, luca.vizzarro@arm.com, yoan.picchi@foss.arm.com, Honnappa.Nagarahalli@arm.com, paul.szczepanek@arm.com Cc: dev@dpdk.org, Dean Marx Subject: [PATCH v6 3/3] doc: revise coding guidelines section Date: Wed, 16 Jul 2025 14:25:46 -0400 Message-ID: <20250716182546.58567-3-dmarx@iol.unh.edu> X-Mailer: git-send-email 2.50.1 In-Reply-To: <20250716182546.58567-1-dmarx@iol.unh.edu> References: <20250716135708.49233-1-dmarx@iol.unh.edu> <20250716182546.58567-1-dmarx@iol.unh.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org The Framework Coding Guidelines section includes outdated information about DTS and how to write a test suite. Updated these points to include the new test case decorators and setup/teardown hooks. Signed-off-by: Dean Marx Reviewed-by: Patrick Robb --- doc/guides/tools/dts.rst | 201 +++++++++++++++++++-------------------- 1 file changed, 97 insertions(+), 104 deletions(-) diff --git a/doc/guides/tools/dts.rst b/doc/guides/tools/dts.rst index 8ba855c6fc..dab0d02a0a 100644 --- a/doc/guides/tools/dts.rst +++ b/doc/guides/tools/dts.rst @@ -78,15 +78,15 @@ Setting up DTS environment To install Poetry, visit their `doc pages `_. The recommended Poetry version is at least 1.8.2. -#. **Getting a Poetry shell** +#. **Running DTS with Poetry** Once you have Poetry along with the proper Python version all set up, it's just a matter - of installing dependencies via Poetry and using the virtual environment Poetry provides: + of installing dependencies via Poetry and running main.py: .. code-block:: console poetry install - poetry shell + poetry run ./main.py #. **SSH Connection** @@ -263,7 +263,7 @@ which don't require password authentication. DTS Execution ~~~~~~~~~~~~~ -DTS is run with ``main.py`` located in the ``dts`` directory after entering Poetry shell: +DTS is run with ``main.py`` located in the ``dts`` directory using the ``poetry run`` command: .. code-block:: console @@ -348,122 +348,118 @@ Adding test cases may require adding code to the framework as well. Framework Coding Guidelines ~~~~~~~~~~~~~~~~~~~~~~~~~~~ -When adding code to the DTS framework, pay attention to the rest of the code -and try not to divert much from it. -The :ref:`DTS developer tools ` will issue warnings -when some of the basics are not met. -You should also build the :ref:`API documentation ` -to address any issues found during the build. - -The API documentation, which is a helpful reference when developing, may be accessed -in the code directly or generated with the :ref:`API docs build steps `. -When adding new files or modifying the directory structure, -the corresponding changes must be made to DTS API doc sources in ``doc/api/dts``. - -Speaking of which, the code must be properly documented with docstrings. -The style must conform to the `Google style -`_. -See an example of the style `here -`_. -For cases which are not covered by the Google style, refer to `PEP 257 -`_. -There are some cases which are not covered by the two style guides, -where we deviate or where some additional clarification is helpful: - - * The ``__init__()`` methods of classes are documented separately - from the docstring of the class itself. - * The docstrings of implemented abstract methods should refer to the superclass's definition - if there's no deviation. - * Instance variables/attributes should be documented in the docstring of the class - in the ``Attributes:`` section. - * The ``dataclass.dataclass`` decorator changes how the attributes are processed. - The dataclass attributes which result in instance variables/attributes - should also be recorded in the ``Attributes:`` section. - * Class variables/attributes and Pydantic model fields, on the other hand, - should be documented with ``#:`` above the type annotated line. - The description may be omitted if the meaning is obvious. - * The ``Enum`` and ``TypedDict`` also process the attributes in particular ways - and should be documented with ``#:`` as well. - This is mainly so that the autogenerated documentation contains the assigned value. - * When referencing a parameter of a function or a method in their docstring, - don't use any articles and put the parameter into single backticks. - This mimics the style of `Python's documentation `_. - * When specifying a value, use double backticks:: - - def foo(greet: bool) -> None: - """Demonstration of single and double backticks. - - `greet` controls whether ``Hello World`` is printed. - - Args: - greet: Whether to print the ``Hello World`` message. - """ - if greet: - print(f"Hello World") - - * The docstring maximum line length is the same as the code maximum line length. +When contributing code to the DTS framework, follow existing conventions to ensure consistency. +The :ref:`DTS developer tools ` will flag basic issues. +Also, be sure to :ref:`build the API documentation ` to catch any problems during the build. + +The API documentation is a helpful reference during development. +It can be viewed in the code directly or generated using the :ref:`API docs build steps `. +If you add new files or change the directory structure, update the corresponding sources in ``doc/api/dts``. + +Code must be documented with docstrings that follow the +`Google style `_. +Additional references: + +* `Sphinx Google style example `_ +* `PEP 257 `_ + +Docstring and Attribute Guidelines + +* Document ``__init__()`` separately from the class docstring. +* If an abstract method simply implements a superclass definition without changes, refer to that superclass in the docstring. +* Document instance variables in the class docstring under an ``Attributes:`` section. +* For ``@dataclass`` classes, document instance-level attributes in ``Attributes:``, as they are generated from the class fields. +* Document class variables and Pydantic fields using ``#:``, + placed above the type-annotated line. Descriptions may be omitted if the meaning is clear. +* Apply ``#:`` to ``Enum`` and ``TypedDict`` fields as well, so that autogenerated documentation includes their values. +* When referring to a parameter in a docstring, omit articles and enclose the parameter in single backticks, + consistent with the `Python documentation style `_. +* Use double backticks for literal values. + +Example:: + + def foo(greet: bool) -> None: + """Demonstrates single and double backticks. + + `greet` controls whether ``Hello World`` is printed. + + Args: + greet: Whether to print the ``Hello World`` message. + """ + if greet: + print("Hello World") + +The maximum line length for docstrings must match that of the code. How To Write a Test Suite ------------------------- -All test suites inherit from ``TestSuite`` defined in ``dts/framework/test_suite.py``. -There are four types of methods that comprise a test suite: +All test suites are classes that inherit from TestSuite, defined in dts/framework/test_suite.py. A typical suite contains: + +Test Cases + + Test cases are defined as methods and must be decorated appropriately. + Use the @func_test and/or @perf_test decorators from TestSuite above each test case method. + For example: + + @func_test + def test_basic_link(self): + """your testcase docstring here""" + #your testcase code here -#. **Test cases** + Functional test cases should use the @func_test decorator, and performance test cases should use @perf_test. + A test suite may include any number of functional and/or performance test cases. + Each suite should focus on testing a single feature (one feature = one test suite). - | Test cases are methods that start with a particular prefix. - | Functional test cases start with ``test_``, e.g. ``test_hello_world_single_core``. - | Performance test cases start with ``test_perf_``, e.g. ``test_perf_nic_single_core``. - | A test suite may have any number of functional and/or performance test cases. - However, these test cases must test the same feature, - following the rule of one feature = one test suite. - Test cases for one feature don't need to be grouped in just one test suite, though. - If the feature requires many testing scenarios to cover, - the test cases would be better off spread over multiple test suites - so that each test suite doesn't take too long to execute. +Setup and Teardown Hooks -#. **Setup and Teardown methods** + Setup and teardown methods can be defined at both the suite and test case levels. - | There are setup and teardown methods for the whole test suite and each individual test case. - | Methods ``set_up_suite`` and ``tear_down_suite`` will be executed - before any and after all test cases have been executed, respectively. - | Methods ``set_up_test_case`` and ``tear_down_test_case`` will be executed - before and after each test case, respectively. - | These methods don't need to be implemented if there's no need for them in a test suite. - In that case, nothing will happen when they are executed. + Suite-level: -#. **Configuration, traffic and other logic** + * set_up_suite() — runs once before any test cases in the suite - The ``TestSuite`` class contains a variety of methods for anything that - a test suite setup, a teardown, or a test case may need to do. + * tear_down_suite() — runs once after all test cases have completed - The test suites also frequently use a DPDK app, such as testpmd, in interactive mode - and use the interactive shell instances directly. + Case-level: - These are the two main ways to call the framework logic in test suites. - If there's any functionality or logic missing from the framework, - it should be implemented so that the test suites can use one of these two ways. + * set_up_test_case() — runs before each individual test case - Test suites may also be configured individually using a file provided at the command line. - The file is a simple mapping of test suite names to their corresponding configurations. + * tear_down_test_case() — runs after each individual test case - Any test suite can be designed to require custom configuration attributes or optional ones. - Any optional attributes should supply a default value for the test suite to use. + These methods are optional. If not implemented, the framework will simply skip them. -#. **Test case verification** + The TestSuite class provides a variety of methods for setup, teardown, and test logic. + Test suites often use DPDK applications (e.g., testpmd) in interactive mode and interact with them via shell instances. - Test case verification should be done with the ``verify`` method, which records the result. - The method should be called at the end of each test case. +Leveraging the DTS framework in writing testsuites: -#. **Other methods** + One should avoid directly importing DTS framework code to their + testsuites where possible. Instead, for performing common processes + required in testsuites, one should use (or add to) the list of methods + provided in the Testsuite class (the base class of all testsuites). For + instance, for sending a list of packets, one should work through the packet + transmitting function already made available in the TestSuite class, + instead of directly importing the DTS traffic generator class and using + that class in one's testsuite implementation. It is also acceptable to + import and instantiate classes for various DPDK applications. For instance, + writing a testsuite for a simple packet forwarding operation would involve + importing the DTS TestPmdShell class, instantiating TestPmdShell, calling + TestPmdShell's start() method, and then sending traffic via one of the + traffic transmitting functions exposed in the Testsuite class. - Of course, all test suite code should adhere to coding standards. - Only the above methods will be treated specially and any other methods may be defined - (which should be mostly private methods needed by each particular test suite). - Any specific features (such as NIC configuration) required by a test suite - should be implemented in the ``SutNode`` class (and the underlying classes that ``SutNode`` uses) - and used by the test suite via the ``sut_node`` field. +Test Case Verification + + Use the verify method to assert conditions and record test results. + This should typically be called at the end of each test case. + Example: self.verify(link_up, "Link should be up after configuration.") + +Other Methods + + All test suite code should follow the project's coding standards. + Only test cases, setup/teardown hooks, and verification methods are treated specially by the framework. + Additional private methods may be added as needed in your testsuite implementation. .. _dts_dev_tools: @@ -493,13 +489,10 @@ Building DTS API docs The documentation is built using the standard DPDK build system. See :doc:`../linux_gsg/build_dpdk` for more details on compiling DPDK with meson. -The :ref:`doc build dependencies ` may be installed with Poetry: - .. code-block:: console poetry install --only docs poetry install --with docs # an alternative that will also install DTS dependencies - poetry shell After executing the meson command, build the documentation with: -- 2.50.1