test suite reviews and discussions
 help / color / mirror / Atom feed
From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "Sun, QinX" <qinx.sun@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "Fu, Qi" <qi.fu@intel.com>, "Sun, QinX" <qinx.sun@intel.com>
Subject: RE: [dts] [PATCH V1] tests/cvl_pps: add 4 new cases
Date: Tue, 18 Jan 2022 02:54:18 +0000	[thread overview]
Message-ID: <0cbdb49e8e1e4a6da76dc9b53ebaaba8@intel.com> (raw)
In-Reply-To: <20211217110746.14318-1-qinx.sun@intel.com>

> -----Original Message-----
> From: Qin Sun <qinx.sun@intel.com>
> Sent: 2021年12月17日 19:08
> To: dts@dpdk.org
> Cc: Fu, Qi <qi.fu@intel.com>; Sun, QinX <qinx.sun@intel.com>
> Subject: [dts] [PATCH V1] tests/cvl_pps: add 4 new cases
> 
> add 4 new cases for pps according to test plan
> 
> Signed-off-by: Qin Sun <qinx.sun@intel.com>

Could you add some description for your core functions: check_register and check_value.

All registers are hard code, so how to compatible to following :

when test the onboard NIC of HCC/SNR platform, the timer = 1, so all the register need to add 4 except GLGEN_GPIO_CTL.

> +# Copyright(c) 2010-2021 Intel Corporation. All rights reserved.

It's the year of 2022, and we don't have copyright of PAST.

> +                self.verify(actual_value != 0,
> +                            'check register failed, expected value is non-zero, actual value is:{}'.format(actual_value))

The verify failure message is valueless, definitely  the actual value is zero, because it is checkout non-zero.

> +            self.logger.info('check register pass')

Also, it is valueless, if target to get stage info, better to use something like: 

Check register <address>: pass

> +    def tear_down(self):
> +        self.dut.kill_all()

Please use "quit()" in testpmd at first, kill_all should be used as a last resort.



      parent reply	other threads:[~2022-01-18  2:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-17 11:07 Qin Sun
2021-12-17  2:44 ` Sun, QinX
2022-01-18  2:54 ` Tu, Lijuan [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=0cbdb49e8e1e4a6da76dc9b53ebaaba8@intel.com \
    --to=lijuan.tu@intel.com \
    --cc=dts@dpdk.org \
    --cc=qi.fu@intel.com \
    --cc=qinx.sun@intel.com \
    /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).