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 B565E43881; Wed, 10 Jan 2024 11:58:20 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 432E340298; Wed, 10 Jan 2024 11:58:20 +0100 (CET) Received: from inbox.dpdk.org (inbox.dpdk.org [95.142.172.178]) by mails.dpdk.org (Postfix) with ESMTP id 28A4B40269 for ; Wed, 10 Jan 2024 11:58:19 +0100 (CET) Received: by inbox.dpdk.org (Postfix, from userid 33) id 07FA343882; Wed, 10 Jan 2024 11:58:18 +0100 (CET) From: bugzilla@dpdk.org To: dev@dpdk.org Subject: [Bug 1357] Test/test suite pattern Date: Wed, 10 Jan 2024 10:58:19 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: DPDK X-Bugzilla-Component: dts X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: juraj.linkes@pantheon.tech X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: dev@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 cc target_milestone Message-ID: Content-Type: multipart/alternative; boundary=17048842980.7BC975D.2487117 Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://bugs.dpdk.org/ Auto-Submitted: auto-generated X-Auto-Response-Suppress: All MIME-Version: 1.0 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 --17048842980.7BC975D.2487117 Date: Wed, 10 Jan 2024 11:58:18 +0100 MIME-Version: 1.0 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 https://bugs.dpdk.org/show_bug.cgi?id=3D1357 Bug ID: 1357 Summary: Test/test suite pattern Product: DPDK Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: Normal Component: dts Assignee: dev@dpdk.org Reporter: juraj.linkes@pantheon.tech CC: juraj.linkes@pantheon.tech, probb@iol.unh.edu Target Milestone: --- A test defines a testing procedure without any particular values to test. A test case is a particular instance of a test with all the values defined. A usual pattern of test case development is a test method implementing the = test procedure and a number of test cases calling the procedure with different values. If there are multiple variables with different values, the number of (possi= ble) test cases could be very high, which would be tedious and error-prone to implement and maintain. This could be alleviated with scripts, but at that point, we could have a more centrallized solution where the definition of t= est cases could be just a matrix/dictionary of all the vectors of values to tes= t. The question is whether this is worth implementing (Are there going to be t= hat many test cases? Do we want that many?)? The solution needs to be cognisant of how the test cases are going to be executed and recorded and most importantly, how are they going to be record= ed in case they're blocked or skipped (i.e. when not executed). --=20 You are receiving this mail because: You are the assignee for the bug.= --17048842980.7BC975D.2487117 Date: Wed, 10 Jan 2024 11:58:18 +0100 MIME-Version: 1.0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.dpdk.org/ Auto-Submitted: auto-generated X-Auto-Response-Suppress: All
Bug ID 1357
Summary Test/test suite pattern
Product DPDK
Version unspecified
Hardware All
OS All
Status UNCONFIRMED
Severity normal
Priority Normal
Component dts
Assignee dev@dpdk.org
Reporter juraj.linkes@pantheon.tech
CC juraj.linkes@pantheon.tech, probb@iol.unh.edu
Target Milestone --- 

A test defines a testing procedure=
 without any particular values to test. A
test case is a particular instance of a test with all the values defined.

A usual pattern of test case development is a test method implementing the =
test
procedure and a number of test cases calling the procedure with different
values.

If there are multiple variables with different values, the number of (possi=
ble)
test cases could be very high, which would be tedious and error-prone to
implement and maintain. This could be alleviated with scripts, but at that
point, we could have a more centrallized solution where the definition of t=
est
cases could be just a matrix/dictionary of all the vectors of values to tes=
t.

The question is whether this is worth implementing (Are there going to be t=
hat
many test cases? Do we want that many?)?

The solution needs to be cognisant of how the test cases are going to be
executed and recorded and most importantly, how are they going to be record=
ed
in case they're blocked or skipped (i.e. when not executed).

You are receiving this mail because:
  • You are the assignee for the bug.
=20=20=20=20=20=20=20=20=20=20
= --17048842980.7BC975D.2487117--