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 AB6114366A; Mon, 4 Dec 2023 11:24:55 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id D0E4E40EDB; Mon, 4 Dec 2023 11:24:36 +0100 (CET) Received: from mail-wm1-f53.google.com (mail-wm1-f53.google.com [209.85.128.53]) by mails.dpdk.org (Postfix) with ESMTP id 031A640DFD for ; Mon, 4 Dec 2023 11:24:34 +0100 (CET) Received: by mail-wm1-f53.google.com with SMTP id 5b1f17b1804b1-40c09f5a7cfso11129755e9.0 for ; Mon, 04 Dec 2023 02:24:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pantheon.tech; s=google; t=1701685473; x=1702290273; 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=ZYiXW2Z88ESYnyFNqmTUgTLHumo8eKturZmLII8hMZI=; b=eNfjMMfB5HTPkS89EsXPMYZEn0EMkLhxjz8ppcgTfCu2eBmjOcA7uTRmZ3ZsmIyoLt mM385Rs9qymuwTilo7PcMyyjeHdcNGN8aIaas5EW09gHYmYIm1XTU6Eu05/vGwe5PUUJ oNNcYothAqgXpPPXiW8A0/YA7RUAvr9fxGheFnQH06Uev2zR4P63pkPCL+LUala5f88P bCqkJnYyyHc+Hddn2cGIxR1weaGF6KTUy6nFwKQI9HdJ8MDgkctZM/5fVBSc10O4cNY/ 0PpXv4NQ6xGjTSOLTPJ9c7kjs3G1iYKdbpI4drJlr4FHC+gVN+JzgwUGQWbw/zpSKyEU KAlA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1701685473; x=1702290273; 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=ZYiXW2Z88ESYnyFNqmTUgTLHumo8eKturZmLII8hMZI=; b=EW4KdTR8pnbOXiG4upq/zDRGhIu7KJrQ7oWQDWAruudTe/Y8x/SVUVTPS3FtrF+E/T 7at3ufOevPhyVn0KQ8p1i/vaFr1Xa0/XPLNblRQXA1bGkQW+ED5MpkhLm6cR1CI71pNE +GMvHCzcDeNqdUL1y94G7saVgzPvmScg5sYWh07uRVLhpxExDYz7G5IKh2ZEh9CEEED4 Fcw+ON5JRU/vZbFoNC6s1RiTtm4tn/AII31bqoE7KaLsFnVrK3FH2vKWB6BPsvytbBf3 5goHipm2r7/+76rgPVUdgBMl7bm0phonGNymMqKRx392pffPkNYaiXJcDcXmZYv/NmNk t7zA== X-Gm-Message-State: AOJu0Yz1OhLMIAhnUk77olD0PbtR9mYR0X+HD61gBULwvS3qaY8lHLNo u55Os9QGAOQX95QWa554NAoeHXQ/XNqu8U8xiAPzxQ== X-Google-Smtp-Source: AGHT+IGgjtgagnPp0taT88/COgyUFNq9wHVVFcUXkW6c7nmCnMswgp8L4vb0MhUhEMX65voqKn7hnQ== X-Received: by 2002:a05:600c:3647:b0:40b:5e59:e9fe with SMTP id y7-20020a05600c364700b0040b5e59e9femr2587244wmq.157.1701685473725; Mon, 04 Dec 2023 02:24:33 -0800 (PST) Received: from jlinkes-PT-Latitude-5530.pantheon.local ([81.89.53.154]) by smtp.gmail.com with ESMTPSA id m28-20020a05600c3b1c00b0040b2b38a1fasm14255415wms.4.2023.12.04.02.24.32 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 04 Dec 2023 02:24:33 -0800 (PST) From: =?UTF-8?q?Juraj=20Linke=C5=A1?= To: thomas@monjalon.net, Honnappa.Nagarahalli@arm.com, jspewock@iol.unh.edu, probb@iol.unh.edu, paul.szczepanek@arm.com, yoan.picchi@foss.arm.com, Luca.Vizzarro@arm.com Cc: dev@dpdk.org, =?UTF-8?q?Juraj=20Linke=C5=A1?= Subject: [PATCH v9 03/21] dts: add basic developer docs Date: Mon, 4 Dec 2023 11:24:11 +0100 Message-Id: <20231204102429.106709-4-juraj.linkes@pantheon.tech> X-Mailer: git-send-email 2.34.1 In-Reply-To: <20231204102429.106709-1-juraj.linkes@pantheon.tech> References: <20231123151344.162812-1-juraj.linkes@pantheon.tech> <20231204102429.106709-1-juraj.linkes@pantheon.tech> 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 Expand the framework contribution guidelines and add how to document the code with Python docstrings. Signed-off-by: Juraj Linkeš --- doc/guides/tools/dts.rst | 73 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 73 insertions(+) diff --git a/doc/guides/tools/dts.rst b/doc/guides/tools/dts.rst index 32c18ee472..cd771a428c 100644 --- a/doc/guides/tools/dts.rst +++ b/doc/guides/tools/dts.rst @@ -264,6 +264,65 @@ which be changed with the ``--output-dir`` command line argument. The results contain basic statistics of passed/failed test cases and DPDK version. +Contributing to DTS +------------------- + +There are two areas of contribution: The DTS framework and DTS test suites. + +The framework contains the logic needed to run test cases, such as connecting to nodes, +running DPDK apps and collecting results. + +The test cases call APIs from the framework to test their scenarios. 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. + +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 docstrigs 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, 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 docs contain 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. + + How To Write a Test Suite ------------------------- @@ -293,6 +352,18 @@ There are four types of methods that comprise a test suite: | 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're is executed. +#. **Configuration, traffic and other logic** + + 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. + + The test suites also frequently use a DPDK app, such as testpmd, in interactive mode + and use the interactive shell instances directly. + + 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. + #. **Test case verification** Test case verification should be done with the ``verify`` method, which records the result. @@ -308,6 +379,8 @@ There are four types of methods that comprise a test suite: and used by the test suite via the ``sut_node`` field. +.. _dts_dev_tools: + DTS Developer Tools ------------------- -- 2.34.1