test suite reviews and discussions
 help / color / mirror / Atom feed
From: Yaqi Tang <yaqi.tang@intel.com>
To: ohilyard@iol.unh.edu
Cc: dts@dpdk.org, xueqin.lin@intel.com, Yaqi Tang <yaqi.tang@intel.com>
Subject: [dts][PATCH V1 1/2] test_plans/eeprom_dump: modify test plan for columbiaville nic
Date: Tue, 22 Mar 2022 23:05:22 +0800	[thread overview]
Message-ID: <20220322150523.845757-2-yaqi.tang@intel.com> (raw)
In-Reply-To: <20220322150523.845757-1-yaqi.tang@intel.com>

If nic is columbiaville, eeprom_dump compare the output of the first 1000 lines from testpmd and ethtool,
module_eeprom_dump compare the output of the first 16 lines from testpmd and ethtool.

Signed-off-by: Yaqi Tang <yaqi.tang@intel.com>
---
 test_plans/eeprom_dump_test_plan.rst | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/test_plans/eeprom_dump_test_plan.rst b/test_plans/eeprom_dump_test_plan.rst
index 3923f3fc..6470297a 100644
--- a/test_plans/eeprom_dump_test_plan.rst
+++ b/test_plans/eeprom_dump_test_plan.rst
@@ -68,8 +68,8 @@ Test Case : EEPROM Dump
 
     ethtool -e <interface_name> raw on length <length> >> <file_name>.txt
 
-3. Store the output from testpmd and ethtool into two files, then compare both files.
-   Verify they are the same.
+3. If nic is columbiaville, store the output of the first 1000 lines from testpmd and ethtool into two files,
+   else store the output from testpmd and ethtool into two files. Then compare both files, verify they are the same.
 
 4. Delete all the files created during testing.
 
@@ -86,7 +86,7 @@ Test Case : Module EEPROM Dump
 
     ethtool -m <interface_name> raw on length <length> >> <file_name>.txt
 
-3. Store the output from testpmd and ethtool into two files, then compare both files.
-   Verify they are the same.
+3. If nic is columbiaville, store the output of the first 16 lines from testpmd and ethtool into two files,
+   else store the output from testpmd and ethtool into two files. Then compare both files, verify they are the same.
 
 4. Delete all the files created during testing.
-- 
2.25.1


  reply	other threads:[~2022-03-22 15:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-22 15:05 [dts][PATCH V1 0/2] eeprom dump Yaqi Tang
2022-03-22 15:05 ` Yaqi Tang [this message]
2022-03-22 15:05 ` [dts][PATCH V1 2/2] tests/eeprom_dump: modify testsuite for columbiaville nic Yaqi Tang
2022-03-23  7:20   ` lijuan.tu

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=20220322150523.845757-2-yaqi.tang@intel.com \
    --to=yaqi.tang@intel.com \
    --cc=dts@dpdk.org \
    --cc=ohilyard@iol.unh.edu \
    --cc=xueqin.lin@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).