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 752ABA04FF; Tue, 22 Mar 2022 13:45:58 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 6EC8D40E64; Tue, 22 Mar 2022 13:45:58 +0100 (CET) Received: from inbox.dpdk.org (inbox.dpdk.org [95.142.172.178]) by mails.dpdk.org (Postfix) with ESMTP id 6E84E40694 for ; Tue, 22 Mar 2022 13:45:56 +0100 (CET) Received: by inbox.dpdk.org (Postfix, from userid 33) id 66B17A0503; Tue, 22 Mar 2022 13:45:56 +0100 (CET) From: bugzilla@dpdk.org To: dts@dpdk.org Subject: [Bug 965] Create DTS test dev document Date: Tue, 22 Mar 2022 12:45:56 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: DTS X-Bugzilla-Component: framework X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: major X-Bugzilla-Who: juraj.linkes@pantheon.tech X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: dts@dpdk.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.dpdk.org/ Auto-Submitted: auto-generated X-Auto-Response-Suppress: All MIME-Version: 1.0 X-BeenThere: dts@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: test suite reviews and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dts-bounces@dpdk.org https://bugs.dpdk.org/show_bug.cgi?id=3D965 Bug ID: 965 Summary: Create DTS test dev document Product: DTS Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: major Priority: Normal Component: framework Assignee: dts@dpdk.org Reporter: juraj.linkes@pantheon.tech Target Milestone: --- The audience for this document are the engineers who are writing the test cases. 1) Document a process to start writing a test case. It can start with copyi= ng a template from the repo. Add some simple test case examples. Output examples= for testpmd functions could be helpful. 2) Highlight the existence of configuration clean up functions that need to= be called after every test case and test suite. Python meta classes feature ca= n be used here to enforce the use of cleanup functions. The base class would be replaced with a meta class. The existing test cases might need to be change= d to conform to this meta class (it might mean adding nops to several functional= ity the meta class requires). 3) Make it clear that the test cases have to be based off of testpmd. If testpmd is lacking features, they need to be added/requested. 4) Document coding and contributor guidelines. 5) Document the allowed cases for using =E2=80=9Ceval=E2=80=9D within the c= ode, which should be avoided, along with reflection and type modification. 6) Document how to handle breaking changes (i.e. changes to configuration f= iles or json output or other interfaces intended for machine interactions [don= =E2=80=99t break the robots]). 7) Capture the procedure to move to latest versions of the dependencies --=20 You are receiving this mail because: You are the assignee for the bug.=