From: Jim Harris <jim.harris@samsung.com>
To: Alison Schofield <alison.schofield@intel.com>
Cc: Dan Williams <dan.j.williams@intel.com>,
"linux-cxl@vger.kernel.org" <linux-cxl@vger.kernel.org>
Subject: Re: [PATCH RFC] Add "uunit" unit testing framework for CXL code
Date: Thu, 4 Jan 2024 18:43:32 +0000 [thread overview]
Message-ID: <ZZb8U/FgJ2t1IqBT@ubuntu> (raw)
In-Reply-To: <ZZbsgXH8n7HgJ23N@aschofie-mobl2>
On Thu, Jan 04, 2024 at 09:36:01AM -0800, Alison Schofield wrote:
> On Thu, Jan 04, 2024 at 04:44:57PM +0000, Jim Harris wrote:
>
> Hi Jim,
>
> Looks really useful, cutting to the part about the individual unit tests....
>
>
> > > > 4) Improve cxl_region tests to cover error conditions and add extensive
> > > > comments explaining how the topology is being built. This overlaps with #3.
> > >
> > > Some comments on the simple tests would help too just to get folks
> > > ramped about what's going on.
> >
> > Ack. The comments are absolutely critical and I should have added them in the
> > v1. They'll be in the v2.
>
> As you might imagine, the first thing I'd like to do with this is try
> to spin up a simple unit test that matches something I do with cxl_test,
> then grow from there.
>
> Coming to this with cxl_test experience, it would be helpful if you
> can draw, comment on some parallels - even to the point of showing,
> here' what cxl/test: cxl-topology.sh (or similar) looks like in CUunit.
>
> It would be helpful to separate into multiple patches showing what needed
> to be done to add a specific unit test. I'm assuming to add core_region_ut.c
> support was added elsewhere in cxl/uunit/*. Separate patches would make
> that dependeny clear and help in mimicing the process of adding a new
> test.
>
> I'll try it out on next posting!
> Thanks,
> Alison
Good idea Alison. I'll take a look at this before I send out the next rev.
-Jim
prev parent reply other threads:[~2024-01-04 18:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20231204193337uscas1p24b1959cf528b02b8172736a61807fff1@uscas1p2.samsung.com>
2023-12-04 19:33 ` [PATCH RFC] Add "uunit" unit testing framework for CXL code Jim Harris
2023-12-05 18:51 ` Davidlohr Bueso
2024-01-04 6:37 ` Dan Williams
2024-01-04 16:44 ` Jim Harris
2024-01-04 17:36 ` Alison Schofield
2024-01-04 18:43 ` Jim Harris [this message]
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=ZZb8U/FgJ2t1IqBT@ubuntu \
--to=jim.harris@samsung.com \
--cc=alison.schofield@intel.com \
--cc=dan.j.williams@intel.com \
--cc=linux-cxl@vger.kernel.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