test suite reviews and discussions
 help / color / mirror / Atom feed
From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "nareddy@marvell.com" <nareddy@marvell.com>,
	"dts@dpdk.org" <dts@dpdk.org>
Cc: "pvukkisala@marvell.com" <pvukkisala@marvell.com>
Subject: Re: [dts] [PATCH] TestSuite_shutdown_api.py: added new test case	test_check_rxtx_desc_status
Date: Fri, 20 Mar 2020 08:06:09 +0000	[thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BBEFA7F@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <1584332512-26301-1-git-send-email-nareddy@marvell.com>

Applied, thanks

> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of
> nareddy@marvell.com
> Sent: Monday, March 16, 2020 12:22 PM
> To: dts@dpdk.org
> Cc: pvukkisala@marvell.com; Praneeth Reddy <nareddy@marvell.com>
> Subject: [dts] [PATCH] TestSuite_shutdown_api.py: added new test case
> test_check_rxtx_desc_status
> 
> From: Praneeth Reddy <nareddy@marvell.com>
> 
> Added new test case to verify descriptor status for cavium_a063 and
> cavium_a064
> 
> Signed-off-by: Praneeth Reddy <nareddy@marvell.com>
> ---
>  conf/test_case_supportlist.json | 16 ++++++++++++++++
> tests/TestSuite_shutdown_api.py | 22 ++++++++++++++++++++++
>  2 files changed, 38 insertions(+)
> 
> diff --git a/conf/test_case_supportlist.json b/conf/test_case_supportlist.json
> index 8d30513..eba0840 100644
> --- a/conf/test_case_supportlist.json
> +++ b/conf/test_case_supportlist.json
> @@ -1766,5 +1766,21 @@
>              "Bug ID": "",
>              "Comments": "this case only support on fortville"
>          }
> +    ],
> +    "check_rxtx_desc_status": [
> +        {
> +            "OS": [
> +                "ALL"
> +            ],
> +            "NIC": [
> +                "cavium_a064",
> +                "cavium_a063"
> +            ],
> +            "Target": [
> +                "ALL"
> +            ],
> +            "Bug ID": "",
> +            "Comments": "This case currently support for cavium_a063 and
> cavium_a064 "
> +        }
>      ]
>  }
> diff --git a/tests/TestSuite_shutdown_api.py
> b/tests/TestSuite_shutdown_api.py index 11d451b..6393b1d 100644
> --- a/tests/TestSuite_shutdown_api.py
> +++ b/tests/TestSuite_shutdown_api.py
> @@ -40,12 +40,14 @@ import utils
>  import time
>  import re
>  import os
> +import random
>  from test_case import TestCase
>  from pmd_output import PmdOutput
>  from settings import HEADER_SIZE, PROTOCOL_PACKET_SIZE  from
> exception import VerifyFailure  from qemu_kvm import QEMUKvm  from
> settings import get_nic_name
> +from random import randint
> 
>  #
>  #
> @@ -744,6 +746,26 @@ class TestShutdownApi(TestCase):
>          self.check_ports(status=True)
>          self.check_forwarding()
> 
> +    def test_check_rxtx_desc_status(self):
> +        """
> +        Check tx and rx descriptors status.
> +        """
> +        self.pmdout.start_testpmd("Default", "--portmask=%s
> + --port-topology=loop" % utils.create_mask(self.ports),
> + socket=self.ports_socket)
> +
> +        for i in range(3):
> +            self.desc = randint(0, 4095)
> +            out = self.dut.send_expect("show port %s rxq 0 desc %s status" %
> (self.ports[0], self.desc), "testpmd> ")
> +            self.verify(
> +               "Desc status = AVAILABLE" in out, "RX descriptor status is improper")
> +            self.verify(
> +               "Bad arguments" not in out, "RX descriptor status is not supported")
> +            self.desc = randint(0, 511)
> +            out = self.dut.send_expect("show port %s txq 0 desc %s status" %
> (self.ports[0], self.desc), "testpmd> ")
> +            self.verify(
> +               "Desc status = FULL" in out, "TX descriptor status is improper")
> +            self.verify(
> +               "Bad arguments" not in out, "TX descriptor status is not
> + supported")
> +
>      def tear_down(self):
>          """
>          Run after each test case.
> --
> 1.8.3.1


      reply	other threads:[~2020-03-20  8:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-16  4:21 nareddy
2020-03-20  8:06 ` 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=8CE3E05A3F976642AAB0F4675D0AD20E0BBEFA7F@SHSMSX101.ccr.corp.intel.com \
    --to=lijuan.tu@intel.com \
    --cc=dts@dpdk.org \
    --cc=nareddy@marvell.com \
    --cc=pvukkisala@marvell.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).