test suite reviews and discussions
 help / color / mirror / Atom feed
From: Yong Liu <yong.liu@intel.com>
To: dts@dpdk.org
Subject: [dts] [PATCH 3/3] Framework: enable test case support check
Date: Wed, 23 Sep 2015 14:40:34 +0800	[thread overview]
Message-ID: <1442990434-17295-3-git-send-email-yong.liu@intel.com> (raw)
In-Reply-To: <1442990434-17295-1-git-send-email-yong.liu@intel.com>

From: Marvin Liu <yong.liu@intel.com>

Before running each case, need to check whether this case should be skippped.
Then check whether testing enviornment support this case. Otherwise should be skipped.

Signed-off-by: Marvin Liu <yong.liu@intel.com>

diff --git a/framework/dts.py b/framework/dts.py
index d2ee015..30c39ab 100644
--- a/framework/dts.py
+++ b/framework/dts.py
@@ -291,8 +291,6 @@ def dts_run_target(crbInst, targets, test_suites, nic, scenario):
     """
     Run each target in execution targets.
     """
-    global skip_case_mode
-    skip_case_mode = check_case_skip(dut)
     if scenario != '':
         scene = VirtScene(dut, tester, scenario)
     else:
@@ -405,11 +403,13 @@ def run_all(config_file, pkgName, git, patch, skip_setup,
     global Patches
     global scenario
     global check_case_inst
+    global support_case_inst
     # save global variable
     Package = pkgName
     Patches = patch
     check_case = parse_file()
     check_case.set_filter_case()
+    check_case.set_support_case()
     # prepare the output folder
     if output_dir == '':
         output_dir = FOLDERS['Output']
@@ -487,6 +487,8 @@ def run_all(config_file, pkgName, git, patch, skip_setup,
         dts_crbs_init(crbInst, skip_setup, read_cache, project, base_dir, nics, virttype)
 
         check_case_inst = check_case_skip(dut)
+        support_case_inst = check_case_support(dut)
+
         # Run DUT prerequisites
         if dts_run_prerequisties(pkgName, patch) is False:
             dts_crbs_exit()
@@ -601,11 +603,18 @@ def execute_test_case(test_suite, test_case):
     result.test_case = test_case.__name__
     rst.write_title("Test Case: " + test_case.__name__)
     if check_case_inst.case_skip(test_case.__name__[len("test_"):]):
-       log_handler.info('Test Case %s Result SKIPED:' % test_case.__name__)
-       rst.write_result("N/A")
-       result.test_case_skip(skip_case_mode.comments)
-       save_all_results()
-       return
+        log_handler.info('Test Case %s Result SKIPED:' % test_case.__name__)
+        rst.write_result("N/A")
+        result.test_case_skip(check_case_inst.comments)
+        save_all_results()
+        return
+
+    if not support_case_inst.case_support(test_case.__name__[len("test_"):]):
+        log_handler.info('Test Case %s Result SKIPED:' % test_case.__name__)
+        rst.write_result("N/A")
+        result.test_case_skip(support_case_inst.comments)
+        save_all_results()
+        return
 
     if performance_only:
         rst.write_annex_title("Annex: " + test_case.__name__)
-- 
1.9.3

      parent reply	other threads:[~2015-09-23  6:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-23  6:40 [dts] [PATCH 1/3] Support check testing environment for test case Yong Liu
2015-09-23  6:40 ` [dts] [PATCH 2/3] Add dpdk support case list execl file Yong Liu
2015-09-23  6:40 ` Yong Liu [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=1442990434-17295-3-git-send-email-yong.liu@intel.com \
    --to=yong.liu@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).