From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/DTS Bug 1460] Decorate test cases
Date: Fri, 14 Jun 2024 13:23:58 +0000 [thread overview]
Message-ID: <bug-1460-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 1093 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1460
Bug ID: 1460
Summary: Decorate test cases
Product: DPDK
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: DTS
Assignee: dev@dpdk.org
Reporter: Luca.Vizzarro@arm.com
CC: juraj.linkes@pantheon.tech, probb@iol.unh.edu
Target Milestone: ---
Assigning attributes to test cases, which are functions, is easier done if the
test cases were to be decorated with e.g. @test. By doing so, the test cases
could also be represented by a metaclass to Mypy, enabling static type checking
and hinting on function attributes. Moreover this metaclass could implement
Protocols define some attributes that could be shares across several classes.
Attributes are also a way to configure the test case environment more easily,
reducing the boilerplate code.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 3017 bytes --]
reply other threads:[~2024-06-14 13:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-1460-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=dev@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).