test suite reviews and discussions
 help / color / mirror / Atom feed
From: "huilong,xu" <huilongx.xu@intel.com>
To: dts@dpdk.org
Subject: [dts] [PATCH V1 3/5] add case skip result when case running
Date: Fri,  7 Aug 2015 14:03:08 +0800	[thread overview]
Message-ID: <1438927390-855-4-git-send-email-huilongx.xu@intel.com> (raw)
In-Reply-To: <1438927390-855-1-git-send-email-huilongx.xu@intel.com>

From: huilong xu <huilongx.xu@intel.com>


Signed-off-by: huilong xu <huilongx.xu@intel.com>
---
 framework/test_result.py |    5 +++++
 1 files changed, 5 insertions(+), 0 deletions(-)

diff --git a/framework/test_result.py b/framework/test_result.py
index 79faee1..2e62d9e 100644
--- a/framework/test_result.py
+++ b/framework/test_result.py
@@ -157,6 +157,11 @@ class Result(object):
         """
         self.__set_test_case_result(result='PASSED', message='')
 
+    def test_case_skip(self,message):
+        """
+        set last test case add as N/A
+        """
+        self.__set_test_case_result(result='N/A', message=message)
     def test_case_failed(self, message):
         """
         Set last test case added as FAILED
-- 
1.7.4.4

  parent reply	other threads:[~2015-08-07  6:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-07  6:03 [dts] [PATCH V1 0/5] add check case list for skip the case, when the case can't test huilong,xu
2015-08-07  6:03 ` [dts] [PATCH V1 1/5] add check case list huilong,xu
2015-08-07  6:03 ` [dts] [PATCH V1 2/5] add N/A result in test report huilong,xu
2015-08-07  6:03 ` huilong,xu [this message]
2015-08-07  6:05   ` [dts] [PATCH V1 3/5] add case skip result when case running Liu, Yong
2015-08-07  6:29     ` Xu, HuilongX
2015-08-07  6:03 ` [dts] [PATCH V1 4/5] add checkCase module huilong,xu
2015-08-07  6:03 ` [dts] [PATCH V1 5/5] add check case function in run case module huilong,xu
2015-08-07  6:52   ` Liu, Yong
2015-08-07  6:06 ` [dts] [PATCH V1 0/5] add check case list for skip the case, when the case can't test Liu, Yong

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=1438927390-855-4-git-send-email-huilongx.xu@intel.com \
    --to=huilongx.xu@intel.com \
    --cc=dts@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).