WO2013143392A1 - 测试用例筛选方法和系统 - Google Patents

测试用例筛选方法和系统 Download PDF

Info

Publication number
WO2013143392A1
WO2013143392A1 PCT/CN2013/072536 CN2013072536W WO2013143392A1 WO 2013143392 A1 WO2013143392 A1 WO 2013143392A1 CN 2013072536 W CN2013072536 W CN 2013072536W WO 2013143392 A1 WO2013143392 A1 WO 2013143392A1
Authority
WO
WIPO (PCT)
Prior art keywords
function node
function
weight
triggered
node
Prior art date
Application number
PCT/CN2013/072536
Other languages
English (en)
French (fr)
Inventor
王巨宏
袁琳
柯硕灏
黄昕
陈锦泽
韩亦纯
Original Assignee
腾讯科技（深圳）有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 腾讯科技（深圳）有限公司 filed Critical 腾讯科技（深圳）有限公司
Publication of WO2013143392A1 publication Critical patent/WO2013143392A1/zh
Priority to US14/154,600 priority Critical patent/US20140130017A1/en
Priority to US14/272,065 priority patent/US20140245267A1/en

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/36—Preventing errors by testing or debugging software
    • G06F11/3668—Software testing
    • G06F11/3672—Test management
    • G06F11/3684—Test management for test design, e.g. generating new test cases
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/36—Preventing errors by testing or debugging software
    • G06F11/3668—Software testing
    • G06F11/3672—Test management
    • G06F11/368—Test management for test version control, e.g. updating test cases to a new software version
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/36—Preventing errors by testing or debugging software
    • G06F11/3668—Software testing
    • G06F11/3672—Test management

Definitions

  • the present invention relates to computer technology, and in particular to a test case screening method and system.
  • Test cases generally include test objectives, test environment, input data, test steps, and expected results. During the test, build a test environment based on test cases, and input preset input data according to preset test steps, and check the output and expectations. Whether the results match. For each pass of the software system, test cases covering all functional nodes in the software system requirements analysis are generally used.
  • each test case must be used to test the software system multiple times after each modification or upgrade.
  • the above methods do not filter the test cases, and the test cases are not targeted. Therefore, it is possible to cause repeated redundant work during the test, which makes the test inefficient.
  • a test case screening method includes the following steps:
  • Filter test cases related to function nodes based on the weights of the function nodes.
  • test case screening system comprising:
  • the trigger number acquisition module is configured to acquire the number of times the function node is triggered
  • a weight calculation module configured to calculate a weight of the function node according to the number of times the function node is triggered
  • a use case screening module is used to filter test cases related to function nodes according to the weights of the function nodes.
  • One or more computer storage media containing computer executable instructions for performing a test case screening method comprising the steps of:
  • Filter test cases related to function nodes based on the weights of the function nodes.
  • the above test case screening method and system can obtain the number of times the function node is triggered after the software system runs for a period of time, calculate the weight of the function node according to the number of times the function node is triggered, and filter the function node according to the weight of the function node.
  • Test case The above method can filter out the test cases related to the function nodes that are triggered in the actual operation. The function nodes are triggered many times, indicating that the function nodes are used frequently, and the function nodes with high frequency of use are also of high importance. Therefore, the above method can screen out test cases related to functional nodes with high importance in actual operation, and the selected test cases are highly targeted, and testing according to the selected test cases can improve the testing efficiency of the software system.
  • FIG. 1 is a schematic flow chart of a test user screening method in an embodiment
  • FIG. 2 is a block diagram showing the structure of a test user screening system in one embodiment.
  • a test case screening method includes the following steps:
  • Step S101 obtaining the number of times the function node is triggered.
  • the statistical code may be added in advance in the program code associated with the function node.
  • the statistical code in the program code related to the function node is also executed, and the statistical code may trigger the function node.
  • the log is written to the specified file or database. Further, after the system runs stably for a preset time, the number of times the function node is triggered may be obtained in the specified file or database.
  • Step S102 calculating the weight of the function node according to the number of times the function node is triggered.
  • the weight of the computeable functional node is the ratio of the number of times the functional node is triggered to the total number of times the functional node is triggered.
  • the weight of the function node calculated according to the above formula is correspondingly higher.
  • Step S103 screening test cases related to the function nodes according to the weights of the function nodes.
  • a predetermined number of function nodes ranked according to weights may be acquired, and test cases related to the acquired function nodes are selected.
  • the function nodes may be sorted according to the weights from large to small, and the pre-preset function nodes are selected, and the test cases related to the previous preset function nodes are further selected in the use case library.
  • the function node with the weight ranking is the important function node.
  • the test cases related to the function nodes with the weight ranking are selected, and the test cases with important importance and specificity are selected.
  • step S103 the specific process of step S103 is: calculating the average weight of the function node, acquiring the function node whose weight is greater than the average weight, and selecting the test case related to the acquired function node.
  • the average weight of the computeable function nodes is the sum of the weights of all functional nodes and the total number of functional nodes. specific The sum of the weights of all function nodes can be 1. Further, the function node having the weight greater than the average weight is selected, and the test case related to the acquired function node is selected in the use case library.
  • Functional nodes with weights higher than the average weight are also important functional nodes. Therefore, this embodiment can also filter out test cases with strong importance.
  • step S103 may select a test case related to the function node according to the weight of the function node, so that the test case-related test case occupies the weight of the selected total test case equal to the weight of the function node.
  • the weights of the function node 1, the function node 2, and the function node 3 are respectively: 5/10, 3/10, and 2/10, and then some or all of the test cases related to the function node 1 may be first found in the use case library. It is assumed that 500 test cases related to the function node 1 are obtained from the use case library. Since the weight ratio of the function node 1, the function node 2, and the function node 3 is 5:3:2, the selected function node 1, the function node 2, and the function are selected. The number of test cases of node 3 should also be 5:3:2, then 300 test cases related to function node 2 can be further selected from the use case library, and 200 test cases related to function node 3 are selected.
  • the number of test cases of the selected function nodes is allocated according to the weight of the function node, so that the test cases of the function nodes with the selected weights are also many, and the test cases of the function nodes with small weights are few, and the selection is small.
  • the number of test cases reasonably reflects the importance of the functional nodes associated with them. Therefore, the above method can select test cases covering a wide range of function nodes, and select more test cases for high-priority function nodes. Therefore, the number of the above methods can be appropriately allocated according to the importance of the function nodes.
  • the test cases are tested according to the test cases selected in the above manner, which can improve the test efficiency.
  • test case screening method further includes the step of obtaining the number of times the user interface component associated with the function node is accessed.
  • step S102 the specific process of step S102 is: calculating the weight of the function node according to the number of times the function node is triggered and the number of times the user interface component associated with the function node is accessed.
  • the user interface component includes a page, button, etc. that interacts with the user at the front end, the user interface component that accesses the front end can trigger a functional node of the back end associated with the user interface component, the user interface component of the front end and the functional node of the back end
  • the correspondence is a one-to-many relationship or a many-to-many relationship.
  • the statistical code can be added to the program code of the user interface component associated with the function node.
  • the program code of the user interface component is executed, and the statistical code in the program code is also executed.
  • the statistical code can write the log accessed by the user interface component to the specified file or database. After the system runs stably for a preset time, the number of times the user interface component is accessed can be obtained in the specified file or database.
  • step S102 may calculate a first ratio of the number of times the function node is triggered to the total number of times the function node is triggered, and calculate the number of times the user interface component associated with the function node is accessed and the total number of times the user interface component is accessed.
  • the second ratio, the weight of the computing function node is the average of the first ratio and the second ratio.
  • the weight of a function node in the system is equal to the average of the first ratio and the second ratio, wherein the first ratio is a ratio of the number of times the function node is triggered to the total number of times all functional nodes in the system are triggered, and second The ratio is the ratio of the number of times the user interface component associated with the function node is accessed to the total number of times all user interface components in the system are accessed.
  • the specific process of calculating the average weight of the function node in step S103 is: calculating a third ratio of the sum of the weights of all the function nodes and the total number of all the function nodes, and then calculating the average number of times all the user interface components are accessed.
  • the proportion of the total number of times the function node is triggered and the total number of times the user interface component associated with the function node is accessed accounts for the total number of times the user interface component is accessed.
  • the weight of the function node is calculated. When the number of times the function node is triggered or the number of times the user interface component associated with the function node is accessed is large, the weight of the function node is also large. In the actual operation of the software system, the number of times the function node is triggered or the number of user interface components associated with the function node are accessed is large, indicating that the function node is of high importance.
  • the weight of the functional node with high importance is also high, and the test case of the functional node with high importance can be selected according to the weight of the function node, so that the selected test case has strong pertinence, according to the selected test.
  • Test cases with use cases can improve test efficiency.
  • the above method further comprises the step of: testing according to the selected test case.
  • the input data of the test case can be input into the software system according to the test step according to the traditional automated test method, and the output result of the software system is compared with the expected output data in the test case, and if the two match, the test case is used. Pass, otherwise, an error report can be output.
  • test cases of the functional nodes with high importance are selected, and the test cases are tested according to the selected test cases, thereby improving the testing efficiency of the software system.
  • a test case screening system includes a trigger number acquisition module 201, a weight calculation module 202, and a use case screening module 203, wherein:
  • the trigger number acquisition module 201 is configured to acquire the number of times the function node is triggered.
  • the statistical code may be added in advance in the program code associated with the function node.
  • the statistical code in the program code related to the function node is also executed, and the statistical code may trigger the function node.
  • the log is written to the specified file or database. Further, after the system runs stably for a preset time, the trigger number acquisition module 201 may acquire the number of times the function node is triggered in the specified file or database.
  • the weight calculation module 202 is configured to calculate the weight of the function node according to the number of times the function node is triggered.
  • the weight calculation module 202 can calculate the weight of the functional node as a ratio of the number of times the functional node is triggered to the total number of times the functional node is triggered.
  • the weight of the function node calculated according to the above formula is correspondingly higher.
  • the use case screening module 203 is configured to filter test cases related to the function nodes according to the weights of the function nodes.
  • the use case screening module 203 can obtain a preset number of function nodes ranked by weight, and select test cases related to the acquired function nodes.
  • the use case screening module 203 may sort the function nodes according to the weights from large to small, and select the pre-preset function nodes, and further select test cases related to the previous preset function nodes in the use case library.
  • the function node with the weight ranking is the important function node.
  • the test cases related to the function nodes with the weight ranking are selected, and the test cases with important importance and specificity are selected.
  • the weight calculation module 202 is further configured to calculate an average weight of the function node
  • the use case screening module 203 is configured to acquire a function node whose weight is greater than the average weight, and select a test case related to the acquired function node.
  • the weight calculation module 202 can calculate the average weight of the function nodes as the sum of the weights of all the function nodes and the total number of the function nodes. Further, the use case screening module 203 can obtain a function node whose weight is greater than the average weight, and select a test case related to the acquired function node in the use case library.
  • the functional nodes whose weight is greater than the average weight are also important functional nodes. Therefore, this embodiment can also filter out test cases with strong importance.
  • the use case screening module 203 can select the test case related to the function node according to the weight of the function node, so that the test case related test case occupies the weight of the selected total test case equal to the weight of the function node.
  • the weights of the function node 1, the function node 2, and the function node 3 are respectively: 5/10, 3/10, and 2/10, and then some or all of the test cases related to the function node 1 may be first found in the use case library. It is assumed that 500 test cases related to the function node 1 are obtained from the use case library. Since the weight ratio of the function node 1, the function node 2, and the function node 3 is 5:3:2, the selected function node 1, the function node 2, and the function are selected. The number of test cases of node 3 should also be 5:3:2, then 300 test cases related to function node 2 can be further selected from the use case library, and 200 test cases related to function node 3 are selected.
  • the number of test cases of the selected function nodes is allocated according to the weight of the function node, so that the test cases of the function nodes with the selected weights are also many, and the test cases of the function nodes with small weights are few, and the selection is small.
  • the number of test cases reasonably reflects the importance of the functional nodes associated with them. Therefore, the above method can select test cases covering a wide range of function nodes, and select more test cases for high-priority function nodes. Therefore, the number of the above methods can be appropriately allocated according to the importance of the function nodes.
  • the test cases are tested according to the test cases selected in the above manner, which can improve the test efficiency.
  • the trigger number acquisition module 201 is further configured to acquire the number of times the user interface component associated with the function node is accessed.
  • the weight calculation module 202 is configured to calculate the weight of the function node according to the number of times the function node is triggered and the number of times the user interface component associated with the function node is accessed.
  • the user interface component includes a page, button, etc. that interacts with the user at the front end, the user interface component that accesses the front end can trigger a functional node of the back end associated with the user interface component, the user interface component of the front end and the functional node of the back end
  • the correspondence is a one-to-many relationship or a many-to-many relationship.
  • the statistical code can be added to the program code of the user interface component associated with the function node.
  • the program code of the user interface component is executed, and the statistical code in the program code is also executed.
  • the statistical code can write the log accessed by the user interface component to the specified file or database.
  • the weight calculation module 202 can obtain the number of times the user interface component is accessed in the specified file or database.
  • the weight calculation module 202 may calculate a first ratio of the number of times the function node is triggered to the total number of times the function node is triggered, calculate the number of times the user interface component associated with the function node is accessed, and the user interface component is The second ratio of the total number of accesses, the weight of the computing function node is the average of the first ratio and the second ratio.
  • the weight of a function node in the system is equal to the average of the first ratio and the second ratio, wherein the first ratio is a ratio of the number of times the function node is triggered to the total number of times all functional nodes in the system are triggered, and second The ratio is the ratio of the number of times the user interface component associated with the function node is accessed to the total number of times all user interface components in the system are accessed.
  • the weight calculation module 202 can calculate a third ratio of the sum of the weights of all the functional nodes to the total number of all the functional nodes, and then calculate the average number of times all the user interface components are accessed and the total number of times all the user interface components are accessed.
  • the fourth ratio is calculated, and the average weight of the function node is calculated as the average of the third ratio and the fourth ratio.
  • the proportion of the total number of times the function node is triggered and the total number of times the user interface component associated with the function node is accessed accounts for the total number of times the user interface component is accessed.
  • the weight of the function node is calculated. When the number of times the function node is triggered or the number of times the user interface component associated with the function node is accessed is large, the weight of the function node is also large. In the actual operation of the software system, the number of times the function node is triggered or the number of user interface components associated with the function node are accessed is large, indicating that the function node is of high importance.
  • the weight of the functional node with high importance is also high, and the test case of the functional node with high importance can be selected according to the weight of the function node, so that the selected test case has strong pertinence, according to the selected test.
  • Test cases with use cases can improve test efficiency.
  • the test case screening system further includes a test module (not shown) for testing based on the selected test cases.
  • the test module can input the input data of the test case into the software system according to the test step according to the traditional automated test method, and compare the output of the software system with the expected output data in the test case, if the two match, The test case passes, otherwise an error report can be output.
  • test cases of the functional nodes with high importance are selected, and the test cases are tested according to the selected test cases, thereby improving the testing efficiency of the software system.
  • the above test case screening method and system can obtain the number of times the function node is triggered after the software system runs for a period of time, calculate the weight of the function node according to the number of times the function node is triggered, and filter the function node according to the weight of the function node.
  • Test case The above method can filter out the test cases related to the function nodes that are triggered in the actual operation. The function nodes are triggered many times, indicating that the function nodes are used frequently, and the function nodes with high frequency of use are also of high importance. Therefore, the above method can screen out test cases related to functional nodes with high importance in actual operation, and the selected test cases are highly targeted, and testing according to the selected test cases can improve the testing efficiency of the software system.
  • the storage medium may be a magnetic disk, an optical disk, or a read-only storage memory ( Read-Only Memory (ROM) or Random Access Memory (RAM).
  • ROM Read-Only Memory
  • RAM Random Access Memory

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Hardware Design (AREA)
  • Quality & Reliability (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Debugging And Monitoring (AREA)

Abstract

一种测试用例筛选方法，包括以下步骤：获取功能节点被触发的次数；根据功能节点被触发的次数计算功能节点的权重；根据功能节点的权重筛选与功能节点相关的测试用例。上述方式可筛选出在实际运行中被触发次数多的功能节点相关的测试用例，功能节点被触发次数多，说明功能节点被使用的频率高，被使用频率高的功能节点的重要性也高，因此上述方式可筛选出实际运行中重要性高的功能节点相关的测试用例，筛选出的测试用例针对性强，根据筛选出的测试用例进行测试可提高软件系统的测试效率。此外，还提供一种测试用例筛选系统以及一种计算机存储介质。

Description

测试用例筛选方法和系统
【技术领域】
本发明涉及计算机技术，特别的涉及一种测试用例筛选方法和系统。
【背景技术】
软件测试是软件生命周期的一个非常重要的环节，在软件系统进行验收和运行前，软件系统都需要经过反复多遍的测试。对软件系统的测试通过执行测试用例来进行实施。测试用例一般包括测试目标、测试环境、输入数据、测试步骤、预期结果，测试过程中，根据测试用例搭建测试环境，并按照预设的测试步骤输入预设的输入数据，并核对输出结果与预期结果是否匹配。对软件系统的每一遍测试，一般都要用到覆盖软件系统需求分析中所有功能节点的测试用例。
由于软件系统有可能经历多次修改或升级，每次修改或升级后，都要用到所有测试用例对软件系统进行多遍测试，上述方式没有对测试用例进行筛选，测试用例的针对性不强，从而有可能导致在测试过程中进行重复冗余的工作，而使得测试效率不高。
【发明内容】
基于此，有必要提供一种能提高测试效率的测试用例筛选方法。
一种测试用例筛选方法，包括以下步骤：
获取功能节点被触发的次数；
根据功能节点被触发的次数计算功能节点的权重；
根据功能节点的权重筛选与功能节点相关的测试用例。
基于此，还有必要提供一种能提高测试效率的测试用例筛选系统。
一种测试用例筛选系统，包括：
触发次数获取模块，用于获取功能节点被触发的次数；
权重计算模块，用于根据功能节点被触发的次数计算功能节点的权重；
用例筛选模块，用于根据功能节点的权重筛选与功能节点相关的测试用例。
此外，还有必要提供一种计算机存储介质，该计算机存储介质包含用于执行提高测试效率的测试用例筛选方法的计算机可执行指令。
一个或多个包含计算机可执行指令的计算机存储介质，所述计算机可执行指令用于执行一种测试用例筛选方法，其特征在于，所述方法包括以下步骤：
获取功能节点被触发的次数；
根据功能节点被触发的次数计算功能节点的权重；
根据功能节点的权重筛选与功能节点相关的测试用例。
上述测试用例筛选方法和系统，可在软件系统运行一段时间后，获取功能节点被触发的次数，根据功能节点被触发的次数计算功能节点的权重，并根据功能节点的权重筛选与功能节点相关的测试用例。上述方式可筛选出在实际运行中被触发次数多的功能节点相关的测试用例，功能节点被触发次数多，说明功能节点被使用的频率高，被使用频率高的功能节点的重要性也高，因此上述方式可筛选出实际运行中重要性高的功能节点相关的测试用例，筛选出的测试用例针对性强，根据筛选出的测试用例进行测试可提高软件系统的测试效率。
【附图说明】
图1为一个实施例中的测试用户筛选方法的流程示意图；
图2为一个实施例中的测试用户筛选系统的结构示意图。
【具体实施方式】
如图1所示，在一个实施例中，一种测试用例筛选方法，包括以下步骤：
步骤S101，获取功能节点被触发的次数。
在一个实施例中，可预先在功能节点相关的程序代码中添加统计代码，当功能节点被触发时，功能节点相关的程序代码中的统计代码也被执行，统计代码可将功能节点被触发的日志写入指定的文件或数据库中。进一步的，当系统稳定运行预设时间后，可在该指定的文件或数据库中获取功能节点被触发的次数。
步骤S102，根据功能节点被触发的次数计算功能节点的权重。
在一个实施例中，可计算功能节点的权重为功能节点被触发的次数与功能节点被触发的总次数的比值。
具体的，可根据以下公式计算功能节点的权重：功能节点的权重=该功能节点被触发的次数/所有功能节点被触发的总次数。即系统中某一功能节点的权重等于该功能节点被触发的次数与系统中所有功能节点被触发的总次数的比值。
功能节点被触发的次数多，则根据上述公式计算出的该功能节点的权重也相应的越高。
步骤S103，根据功能节点的权重筛选与功能节点相关的测试用例。
在一个实施例中，可获取按照权重排序靠前的预设数量个功能节点，选取与获取的功能节点相关的测试用例。
具体的，可将功能节点按照权重由大到小进行排序，并选取其中前预设个功能节点，进一步在用例库中选取与前预设个功能节点相关的测试用例。
权重排序靠前的功能节点为重要的功能节点，本实施例中，选取权重排序靠前的功能节点相关的测试用例，筛选出了重要性及针对性强的测试用例。
在另一个实施例中，步骤S103的具体过程为：计算功能节点的平均权重，获取权重大于平均权重的功能节点，选取与获取的功能节点相关的测试用例。
具体的，可计算功能节点的平均权重为所有功能节点的权重的和与功能节点的总数。具体的 ，所有功能节点的权重的和可为1。进一步的，获取权重大于平均权重的功能节点，在用例库中选取与获取的功能节点相关的测试用例。
权重高于平均权重的功能节点也为重要的功能节点，因此，本实施例也可筛选出重要性强的测试用例。
在又一个实施例中，步骤S103可根据功能节点的权重选取功能节点相关的测试用例，使得功能节点相关的测试用例占选取的总的测试用例的比重等于功能节点的权重。例如功能节点1、功能节点2、功能节点3的权重分别为：5/10、3/10、2/10，则可首先在用例库中查找出功能节点1相关的部分或所有的测试用例，设从用例库中获取功能节点1相关的测试用例500个，由于功能节点1、功能节点2、功能节点3的权重比为5:3:2，所以选取的功能节点1、功能节点2、功能节点3的测试用例的个数比也应该是5:3:2，则可进一步从用例库中选取300个与功能节点2相关的测试用例，并选取200个与功能节点3相关的测试用例。
本实施例中，按照功能节点的权重来分配选取的各功能节点的测试用例的数量，使得选取的权重大的功能节点的测试用例也多，而权重小的功能节点的测试用例也少，选取的测试用例的数量合理的反映了与之相关的功能节点的重要性。因此，上述方式既能选取覆盖较广范围的功能节点的测试用例，又能为重要性高的功能节点选取较多的测试用例，因此上述方式可筛选出数量根据功能节点的重要性进行合理分配的测试用例，根据上述方式选取出的测试用例进行测试，可提高测试效率。
在一个实施例中，上述测试用例筛选方法还包括步骤：获取与功能节点关联的用户界面组件被访问的次数。
本实施例中，步骤S102的具体过程为：根据功能节点被触发的次数以及与功能节点关联的用户界面组件被访问的次数计算功能节点的权重。
在一个实施例中，用户界面组件包括在前端与用户交互的页面、按钮等，访问前端的用户界面组件可触发与用户界面组件关联的后端的功能节点，前端的用户界面组件与后端的功能节点的对应关系为一对多的关系或多对多的关系。
具体的，在一个实施例中，可在与功能节点关联的用户界面组件的程序代码中添加统计代码。当用户访问用户界面组件时，用户界面组件的程序代码即被执行，程序代码中的统计代码也被执行，统计代码可将用户界面组件被访问的日志写入指定的文件或数据库。在系统稳定运行预设时间后，可在该指定的文件或数据库中获取用户界面组件被访问的次数。
进一步的，步骤S102可计算功能节点被触发的次数与功能节点被触发的总次数的第一比值，计算与功能节点关联的用户界面组件被访问的次数与用户界面组件被访问的总次数的第二比值，计算功能节点的权重为第一比值与第二比值的平均值。
具体的，步骤S102可根据以下公式计算功能节点的权重：功能节点的权重=（该功能节点被触发的次数/所有功能节点被触发的总次数+与该功能节点关联的用户界面组件被访问的次数/所有用户界面组件被访问的总次数）/2。即系统中某一功能节点的权重等于第一比值与第二比值的平均值，其中，第一比值为该功能节点被触发的次数与系统中所有功能节点被触发的总次数的比值，第二比值为与该功能节点关联的用户界面组件被访问的次数与系统中所有用户界面组件被访问的总次数的比值。
本实施例中，步骤S103中计算功能节点的平均权重的具体过程为：计算所有功能节点的权重的和与所有功能节点的总数的第三比值，再计算所有用户界面组件被访问的平均次数与所有用户界面组件被访问的总次数的第四比值，并计算功能节点的平均权重为该第三比值与第四比值的平均值。
本实施例中，根据功能节点被触发的次数占所有功能节点被触发的总次数的比重以及与该功能节点关联的用户界面组件被访问的次数占所有用户界面组件被访问的总次数的比重来计算该功能节点的权重，当功能节点被触发的次数多或功能节点关联的用户界面组件被访问的次数多时，该功能节点的权重也大。软件系统实际运行中，功能节点被触发的次数多或功能节点关联的用户界面组件被访问的次数多，说明该功能节点的重要性高。本实施例中，重要性高的功能节点的权重也高，可根据功能节点的权重选择出重要性高的功能节点的测试用例，从而选取的测试用例有较强的针对性，根据选取的测试用例进行测试，可提高测试效率。
在一个实施例中，上述方法还包括步骤：根据筛选出的测试用例进行测试。
具体的，可根据传统的自动化测试方法将测试用例的输入数据按照测试步骤输入软件系统，并将软件系统输出的结果与测试用例中的预期的输出数据进行比较，如二者匹配，则测试用例通过，否则，可输出错误报告。
本实施例中，筛选出重要性高的功能节点的测试用例，并根据筛选出的测试用例进行测试，可提高软件系统的测试效率。
如图2所示，在一个实施例中，一种测试用例筛选系统，包括触发次数获取模块201、权重计算模块202、用例筛选模块203，其中：
触发次数获取模块201用于获取功能节点被触发的次数。
在一个实施例中，可预先在功能节点相关的程序代码中添加统计代码，当功能节点被触发时，功能节点相关的程序代码中的统计代码也被执行，统计代码可将功能节点被触发的日志写入指定的文件或数据库中。进一步的，当系统稳定运行预设时间后，触发次数获取模块201可在该指定的文件或数据库中获取功能节点被触发的次数。
权重计算模块202用于根据功能节点被触发的次数计算功能节点的权重。
在一个实施例中，权重计算模块202可计算功能节点的权重为功能节点被触发的次数与功能节点被触发的总次数的比值。
具体的，权重计算模块202可根据以下公式计算功能节点的权重：功能节点的权重=该功能节点被触发的次数/所有功能节点被触发的总次数。即系统中某一功能节点的权重等于该功能节点被触发的次数与系统中所有功能节点被触发的总次数的比值。
功能节点被触发的次数多，则根据上述公式计算出的该功能节点的权重也相应的越高。
用例筛选模块203用于根据功能节点的权重筛选与功能节点相关的测试用例。
在一个实施例中，用例筛选模块203可获取按照权重排序靠前的预设数量个功能节点，选取与获取的功能节点相关的测试用例。
具体的，用例筛选模块203可将功能节点按照权重由大到小进行排序，并选取其中前预设个功能节点，进一步在用例库中选取与前预设个功能节点相关的测试用例。
权重排序靠前的功能节点为重要的功能节点，本实施例中，选取权重排序靠前的功能节点相关的测试用例，筛选出了重要性及针对性强的测试用例。
在另一个实施例中，权重计算模块202还用于计算功能节点的平均权重，用例筛选模块203用于获取权重大于平均权重的功能节点，选取与获取的功能节点相关的测试用例。
具体的，权重计算模块202可计算功能节点的平均权重为所有功能节点的权重的和与功能节点的总数。进一步的，用例筛选模块203可获取权重大于平均权重的功能节点，在用例库中选取与获取的功能节点相关的测试用例。
权重大于平均权重的功能节点也为重要的功能节点，因此，本实施例也可筛选出重要性强的测试用例。
在又一个实施例中，用例筛选模块203可根据功能节点的权重选取功能节点相关的测试用例，使得功能节点相关的测试用例占选取的总的测试用例的比重等于功能节点的权重。例如功能节点1、功能节点2、功能节点3的权重分别为：5/10、3/10、2/10，则可首先在用例库中查找出功能节点1相关的部分或所有的测试用例，设从用例库中获取功能节点1相关的测试用例500个，由于功能节点1、功能节点2、功能节点3的权重比为5:3:2，所以选取的功能节点1、功能节点2、功能节点3的测试用例的个数比也应该是5:3:2，则可进一步从用例库中选取300个与功能节点2相关的测试用例，并选取200个与功能节点3相关的测试用例。
本实施例中，按照功能节点的权重来分配选取的各功能节点的测试用例的数量，使得选取的权重大的功能节点的测试用例也多，而权重小的功能节点的测试用例也少，选取的测试用例的数量合理的反映了与之相关的功能节点的重要性。因此，上述方式既能选取覆盖较广范围的功能节点的测试用例，又能为重要性高的功能节点选取较多的测试用例，因此上述方式可筛选出数量根据功能节点的重要性进行合理分配的测试用例，根据上述方式选取出的测试用例进行测试，可提高测试效率。
在一个实施例中，触发次数获取模块201还用于获取与功能节点关联的用户界面组件被访问的次数。
本实施例中，权重计算模块202用于根据功能节点被触发的次数以及与功能节点关联的用户界面组件被访问的次数计算功能节点的权重。
在一个实施例中，用户界面组件包括在前端与用户交互的页面、按钮等，访问前端的用户界面组件可触发与用户界面组件关联的后端的功能节点，前端的用户界面组件与后端的功能节点的对应关系为一对多的关系或多对多的关系。
具体的，在一个实施例中，可在与功能节点关联的用户界面组件的程序代码中添加统计代码。当用户访问用户界面组件时，用户界面组件的程序代码即被执行，程序代码中的统计代码也被执行，统计代码可将用户界面组件被访问的日志写入指定的文件或数据库。在系统稳定运行预设时间后，权重计算模块202可在该指定的文件或数据库中获取用户界面组件被访问的次数。
进一步的，权重计算模块202可计算所述功能节点被触发的次数与功能节点被触发的总次数的第一比值，计算与所述功能节点关联的用户界面组件被访问的次数与用户界面组件被访问的总次数的第二比值，计算功能节点的权重为第一比值与第二比值的平均值。
具体的，权重计算模块202可根据以下公式计算功能节点的权重：功能节点的权重=（该功能节点被触发的次数/所有功能节点被触发的总次数+与该功能节点关联的用户界面组件被访问的次数/所有用户界面组件被访问的总次数）/2。即系统中某一功能节点的权重等于第一比值与第二比值的平均值，其中，第一比值为该功能节点被触发的次数与系统中所有功能节点被触发的总次数的比值，第二比值为与该功能节点关联的用户界面组件被访问的次数与系统中所有用户界面组件被访问的总次数的比值。
本实施例中，权重计算模块202可计算所有功能节点的权重的和与所有功能节点的总数的第三比值，再计算所有用户界面组件被访问的平均次数与所有用户界面组件被访问的总次数的第四比值，并计算功能节点的平均权重为该第三比值与第四比值的平均值。
本实施例中，根据功能节点被触发的次数占所有功能节点被触发的总次数的比重以及与该功能节点关联的用户界面组件被访问的次数占所有用户界面组件被访问的总次数的比重来计算该功能节点的权重，当功能节点被触发的次数多或功能节点关联的用户界面组件被访问的次数多时，该功能节点的权重也大。软件系统实际运行中，功能节点被触发的次数多或功能节点关联的用户界面组件被访问的次数多，说明该功能节点的重要性高。本实施例中，重要性高的功能节点的权重也高，可根据功能节点的权重选择出重要性高的功能节点的测试用例，从而选取的测试用例有较强的针对性，根据选取的测试用例进行测试，可提高测试效率。
在一个实施例中，上述测试用例筛选系统还包括测试模块（图中未示出），用于根据筛选出的测试用例进行测试。
具体的，测试模块可根据传统的自动化测试方法将测试用例的输入数据按照测试步骤输入软件系统，并将软件系统输出的结果与测试用例中的预期的输出数据进行比较，如二者匹配，则测试用例通过，否则，可输出错误报告。
本实施例中，筛选出重要性高的功能节点的测试用例，并根据筛选出的测试用例进行测试，可提高软件系统的测试效率。
上述测试用例筛选方法和系统，可在软件系统运行一段时间后，获取功能节点被触发的次数，根据功能节点被触发的次数计算功能节点的权重，并根据功能节点的权重筛选与功能节点相关的测试用例。上述方式可筛选出在实际运行中被触发次数多的功能节点相关的测试用例，功能节点被触发次数多，说明功能节点被使用的频率高，被使用频率高的功能节点的重要性也高，因此上述方式可筛选出实际运行中重要性高的功能节点相关的测试用例，筛选出的测试用例针对性强，根据筛选出的测试用例进行测试可提高软件系统的测试效率。
本领域普通技术人员可以理解实现上述实施例方法中的全部或部分流程，是可以通过计算机程序控制相关的硬件来完成的，所述的程序可存储于一计算机可读取存储介质中，该程序在执行时，可包括如上述各方法的实施例的流程。其中，所述的存储介质可为磁碟、光盘、只读存储记忆体（ Read-Only Memory ， ROM ）或随机存储记忆体（ Random Access Memory ， RAM ）等。
以上所述实施例仅表达了本发明的几种实施方式，其描述较为具体和详细，但并不能因此而理解为对本发明专利范围的限制。应当指出的是，对于本领域的普通技术人员来说，在不脱离本发明构思的前提下，还可以做出若干变形和改进，这些都属于本发明的保护范围。因此，本发明专利的保护范围应以所附权利要求为准。

Claims (18)

  1. 一种测试用例筛选方法，包括以下步骤：
    获取功能节点被触发的次数；
    根据功能节点被触发的次数计算功能节点的权重；
    根据功能节点的权重筛选与功能节点相关的测试用例。
  2. 根据权利要求1所述的测试用例筛选方法，其特征在于，所述根据功能节点被触发的次数计算功能节点的权重的步骤为：
    计算功能节点的权重为所述功能节点被触发的次数与功能节点被触发的总次数的比值。
  3. 根据权利要求1所述的测试用例筛选方法，其特征在于，所述方法还包括：
    获取与所述功能节点关联的用户界面组件被访问的次数；
    所述根据功能节点被触发的次数计算功能节点的权重的步骤为：根据所述功能节点被触发的次数以及与所述功能节点关联的用户界面组件被访问的次数计算所述功能节点的权重。
  4. 根据权利要求3所述的测试用例筛选方法，其特征在于，所述根据所述功能节点被触发的次数以及与所述功能节点关联的用户界面组件被访问的次数计算所述功能节点的权重的步骤为：
    计算所述功能节点被触发的次数与功能节点被触发的总次数的第一比值，计算与所述功能节点关联的用户界面组件被访问的次数与用户界面组件被访问的总次数的第二比值，并计算所述功能节点的权重为第一比值与第二比值的平均值。
  5. 根据权利要求1-4任一所述的测试用例筛选方法，其特征在于，所述根据功能节点的权重筛选与功能节点相关的测试用例的步骤为：
    获取按照所述权重排序靠前的预设数量个功能节点，选取与所述获取的功能节点相关的测试用例。
  6. 根据权利要求1-4任一所述的测试用例筛选方法，其特征在于，所述根据功能节点的权重筛选与功能节点相关的测试用例的步骤为：
    计算功能节点的平均权重，获取权重大于平均权重的功能节点，选取与所述获取的功能节点相关的测试用例。
  7. 一种测试用例筛选系统，其特征在于，包括：
    触发次数获取模块，用于获取功能节点被触发的次数；
    权重计算模块，用于根据功能节点被触发的次数计算功能节点的权重；
    用例筛选模块，用于根据功能节点的权重筛选与功能节点相关的测试用例。
  8. 根据权利要求7所述的测试用例筛选系统，其特征在于，所述权重计算模块用于计算功能节点的权重为所述功能节点被触发的次数与功能节点被触发的总次数的比值。
  9. 根据权利要求7所述的测试用例筛选系统，其特征在于，所述触发次数获取模块还用于获取与所述功能节点关联的用户界面组件被访问的次数；
    所述权重计算模块用于根据所述功能节点被触发的次数以及与所述功能节点关联的用户界面组件被访问的次数计算所述功能节点的权重。
  10. 根据权利要求9所述的测试用例筛选系统，其特征在于，所述权重计算模块用于计算所述功能节点被触发的次数与功能节点被触发的总次数的第一比值，计算与所述功能节点关联的用户界面组件被访问的次数与用户界面组件被访问的总次数的第二比值，并计算所述功能节点的权重为第一比值与第二比值的平均值。
  11. 根据权利要求7-10任一所述的测试用例筛选系统，其特征在于，所述用例筛选模块用于获取按照所述权重排序靠前的预设数量个功能节点，选取与所述获取的功能节点相关的测试用例。
  12. 根据权利要求7-10任一所述的测试用例筛选系统，其特征在于，所述用例筛选模块用于计算功能节点的平均权重，获取权重大于平均权重的功能节点，选取与所述获取的功能节点相关的测试用例。
  13. 一个或多个包含计算机可执行指令的计算机存储介质，所述计算机可执行指令用于执行一种测试用例筛选方法，其特征在于，所述方法包括以下步骤：
    获取功能节点被触发的次数；
    根据功能节点被触发的次数计算功能节点的权重；
    根据功能节点的权重筛选与功能节点相关的测试用例。
  14. 根据权利要求13所述的测试用例筛选方法，其特征在于，所述根据功能节点被触发的次数计算功能节点的权重的步骤为：
    计算功能节点的权重为所述功能节点被触发的次数与功能节点被触发的总次数的比值。
  15. 根据权利要求13所述的测试用例筛选方法，其特征在于，所述方法还包括：
    获取与所述功能节点关联的用户界面组件被访问的次数；
    所述根据功能节点被触发的次数计算功能节点的权重的步骤为：根据所述功能节点被触发的次数以及与所述功能节点关联的用户界面组件被访问的次数计算所述功能节点的权重。
  16. 根据权利要求15所述的测试用例筛选方法，其特征在于，所述根据所述功能节点被触发的次数以及与所述功能节点关联的用户界面组件被访问的次数计算所述功能节点的权重的步骤为：
    计算所述功能节点被触发的次数与功能节点被触发的总次数的第一比值，计算与所述功能节点关联的用户界面组件被访问的次数与用户界面组件被访问的总次数的第二比值，并计算所述功能节点的权重为第一比值与第二比值的平均值。
  17. 根据权利要求13-16任一所述的测试用例筛选方法，其特征在于，所述根据功能节点的权重筛选与功能节点相关的测试用例的步骤为：
    获取按照所述权重排序靠前的预设数量个功能节点，选取与所述获取的功能节点相关的测试用例。
  18. 根据权利要求13-16任一所述的测试用例筛选方法，其特征在于，所述根据功能节点的权重筛选与功能节点相关的测试用例的步骤为：
    计算功能节点的平均权重，获取权重大于平均权重的功能节点，选取与所述获取的功能节点相关的测试用例。
PCT/CN2013/072536 2012-03-28 2013-03-13 测试用例筛选方法和系统 WO2013143392A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US14/154,600 US20140130017A1 (en) 2012-03-28 2014-01-14 Test case screening method and system
US14/272,065 US20140245267A1 (en) 2012-03-28 2014-05-07 Test case screening method and system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201210086547.9 2012-03-28
CN201210086547.9A CN103365765B (zh) 2012-03-28 2012-03-28 测试用例筛选方法和系统

Related Child Applications (2)

Application Number Title Priority Date Filing Date
US14/154,600 Continuation US20140130017A1 (en) 2012-03-28 2014-01-14 Test case screening method and system
US14/272,065 Continuation US20140245267A1 (en) 2012-03-28 2014-05-07 Test case screening method and system

Publications (1)

Publication Number Publication Date
WO2013143392A1 true WO2013143392A1 (zh) 2013-10-03

Family

ID=49258192

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2013/072536 WO2013143392A1 (zh) 2012-03-28 2013-03-13 测试用例筛选方法和系统

Country Status (3)

Country Link
US (2) US20140130017A1 (zh)
CN (1) CN103365765B (zh)
WO (1) WO2013143392A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113515462A (zh) * 2021-08-24 2021-10-19 北京百度网讯科技有限公司 用于测试的方法、装置、设备以及存储介质

Families Citing this family (23)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9489290B1 (en) * 2005-12-30 2016-11-08 The Mathworks, Inc. Scheduling tests based on a valuation system
US9311223B2 (en) * 2013-05-21 2016-04-12 International Business Machines Corporation Prioritizing test cases using multiple variables
CN104360945B (zh) * 2014-11-18 2017-07-07 电信科学技术第十研究所 一种测试用例筛选的计算机实现的方法、计算机及系统
US9471468B2 (en) * 2014-12-02 2016-10-18 International Business Machines Corporation System, method, and computer program to improve the productivity of unit testing
CN106933728B (zh) * 2015-12-29 2020-12-01 中移信息技术有限公司 需求与用例关联度量的方法及装置
US10067861B2 (en) * 2016-02-19 2018-09-04 International Business Machines Corporation Efficient software testing
CN107622007A (zh) * 2016-07-14 2018-01-23 北京京东尚科信息技术有限公司 应用测试方法和装置
CN106201898B (zh) * 2016-07-26 2018-12-04 北京班墨科技有限责任公司 一种基于人工智能的测试软件的方法及装置
CN108153658A (zh) * 2016-12-02 2018-06-12 富士通株式会社 优先级模型训练方法及确定测试用例优先级的方法和装置
CN108268366B (zh) * 2016-12-30 2021-01-22 腾讯科技（深圳）有限公司 测试用例执行方法及装置
CN108255734A (zh) * 2018-02-01 2018-07-06 中国工商银行股份有限公司 测试覆盖分析方法及系统
CN108595326A (zh) * 2018-04-13 2018-09-28 捷德（中国）信息科技有限公司 基于单条指令的代码耗时统计方法、系统及存储介质
CN108845927B (zh) * 2018-05-04 2021-12-07 联动优势电子商务有限公司 一种测试用例的筛选方法及装置
CN108664405B (zh) * 2018-05-17 2021-11-09 福建天泉教育科技有限公司 一种基于漏斗模型的自动化监测方法及终端
CN109189673B (zh) * 2018-08-14 2021-08-27 联动优势电子商务有限公司 一种软件的测试方案、测试用例的确定方法及装置
CN109101431A (zh) * 2018-09-26 2018-12-28 深圳壹账通智能科技有限公司 一种测试用例管理方法、计算机可读存储介质及终端设备
CN109800169A (zh) * 2019-01-24 2019-05-24 拉扎斯网络科技（上海）有限公司 测试用例的获取方法、装置、可读存储介质和电子设备
US11263116B2 (en) * 2019-01-24 2022-03-01 International Business Machines Corporation Champion test case generation
CN110245848B (zh) * 2019-05-31 2021-08-06 口碑(上海)信息技术有限公司 程序代码的风险评估方法和装置
US11422924B2 (en) 2019-06-13 2022-08-23 International Business Machines Corporation Customizable test set selection using code flow trees
CN112084106B (zh) * 2019-06-14 2023-08-01 中国移动通信集团浙江有限公司 测试数据选取的方法、装置、计算设备及计算机存储介质
CN112559327B (zh) * 2020-12-02 2022-09-06 天津车之家数据信息技术有限公司 一种测试用例的生成方法、装置和计算设备
CN113590495A (zh) * 2021-08-31 2021-11-02 北京沃东天骏信息技术有限公司 一种测试覆盖率的确定方法、装置、设备及存储介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102004691A (zh) * 2010-11-12 2011-04-06 中兴通讯股份有限公司 执行测试用例的方法及系统
US20110083121A1 (en) * 2009-10-02 2011-04-07 Gm Global Technology Operations, Inc. Method and System for Automatic Test-Case Generation for Distributed Embedded Systems
CN102063374A (zh) * 2011-01-07 2011-05-18 南京大学 一种使用半监督信息进行聚类的回归测试用例选择方法

Family Cites Families (25)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6126329A (en) * 1993-06-08 2000-10-03 Rational Software Coporation Method and apparatus for accurate profiling of computer programs
US6026235A (en) * 1997-05-20 2000-02-15 Inprise Corporation System and methods for monitoring functions in natively compiled software programs
US7165074B2 (en) * 2002-05-08 2007-01-16 Sun Microsystems, Inc. Software development test case analyzer and optimizer
US7167870B2 (en) * 2002-05-08 2007-01-23 Sun Microsystems, Inc. Software development test case maintenance
US7299452B1 (en) * 2002-05-10 2007-11-20 Oracle International Corporation System and method for testing the compatibility of a computer application with a foreign character set
AU2003250422A1 (en) * 2002-08-26 2004-03-11 Koninklijke Philips Electronics N.V. Unit for and method of detection a content property in a sequence of video images
US20040073890A1 (en) * 2002-10-09 2004-04-15 Raul Johnson Method and system for test management
US7730461B2 (en) * 2002-12-30 2010-06-01 International Business Machines Corporation Software tool configured to generate test cases characterized by a linear range of integral values
US8214819B2 (en) * 2004-07-09 2012-07-03 Hewlett-Packard Development Company, L.P. Determining call counts in a program
US8402317B1 (en) * 2005-12-22 2013-03-19 The Math Works, Inc. Viewing multi-dimensional metric data from multiple test cases
US8561036B1 (en) * 2006-02-23 2013-10-15 Google Inc. Software test case management
US8739143B2 (en) * 2007-01-31 2014-05-27 Hewlett-Packard Development Company, L.P. Profiling metrics for computer programs
US7779374B1 (en) * 2006-09-29 2010-08-17 Breker Verification Systems, Inc. Generating self-checking test cases from reduced case analysis graphs
US8713513B2 (en) * 2006-12-13 2014-04-29 Infosys Limited Evaluating programmer efficiency in maintaining software systems
US7913230B2 (en) * 2007-01-31 2011-03-22 Oracle International Corporation Computer-implemented methods and systems for generating software testing documentation and test results management system using same
WO2009023901A1 (en) * 2007-08-17 2009-02-26 National Ict Australia Limited Automating dynamic programs
US8370821B2 (en) * 2007-08-21 2013-02-05 International Business Machines Corporation Method for enabling profile-based call site tailor-ing using profile gathering of cloned functions
US7506312B1 (en) * 2008-01-31 2009-03-17 International Business Machines Corporation Method and system for automatically determining risk areas to retest
CN101661425B (zh) * 2008-08-26 2012-03-21 国际商业机器公司 测试覆盖分析方法和装置
CN101666853B (zh) * 2008-09-03 2011-08-17 京元电子股份有限公司 测试排程系统与方法
US8150814B2 (en) * 2009-04-07 2012-04-03 Business Objects Software Ltd. System and method of data cleansing using rule based formatting
US8413117B1 (en) * 2009-08-07 2013-04-02 Symantec Corporation Systems and methods for focusing product testing based on areas of change within the product between product builds
CN102135979B (zh) * 2010-12-08 2013-10-09 华为技术有限公司 数据清洗方法及装置
CN102622294B (zh) * 2011-01-28 2014-12-10 国际商业机器公司 生成用于不同测试类型的测试用例的方法和装置
US10223246B2 (en) * 2012-07-30 2019-03-05 Infosys Limited System and method for functional test case generation of end-to-end business process models

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110083121A1 (en) * 2009-10-02 2011-04-07 Gm Global Technology Operations, Inc. Method and System for Automatic Test-Case Generation for Distributed Embedded Systems
CN102004691A (zh) * 2010-11-12 2011-04-06 中兴通讯股份有限公司 执行测试用例的方法及系统
CN102063374A (zh) * 2011-01-07 2011-05-18 南京大学 一种使用半监督信息进行聚类的回归测试用例选择方法

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113515462A (zh) * 2021-08-24 2021-10-19 北京百度网讯科技有限公司 用于测试的方法、装置、设备以及存储介质

Also Published As

Publication number Publication date
US20140130017A1 (en) 2014-05-08
US20140245267A1 (en) 2014-08-28
CN103365765B (zh) 2016-10-12
CN103365765A (zh) 2013-10-23

Similar Documents

Publication Publication Date Title
WO2013143392A1 (zh) 测试用例筛选方法和系统
Nagaraj et al. Structured comparative analysis of systems logs to diagnose performance problems
Tikir et al. PSINS: An open source event tracer and execution simulator for MPI applications
US7320090B2 (en) Methods, systems, and media for generating a regression suite database
WO2018014582A1 (zh) 保单数据处理方法、装置、服务器和存储介质
Shi et al. Evaluating scalability bottlenecks by workload extrapolation
WO2018120721A1 (zh) 用户界面的测试方法、系统、电子装置及计算机可读存储介质
US8005794B2 (en) Mechanism for data aggregation in a tracing framework
Hammond et al. WARPP: a toolkit for simulating high-performance parallel scientific codes
US20150169435A1 (en) Method and apparatus for mining test coverage data
JP2010524060A (ja) 分散コンピューティングにおけるデータマージング
Wan et al. Analysis and modeling of the end-to-end i/o performance on olcf's titan supercomputer
WO2020207014A1 (zh) 大数据自动回归测试方法、装置、测试中心服务器和存储介质
US7925489B2 (en) Defining and recording threshold-qualified count events of a simulation by testcases
Wu et al. Automatic generation of executable communication specifications from parallel applications
US8050902B2 (en) Reporting temporal information regarding count events of a simulation
Dietrich et al. Pika: Center-wide and job-aware cluster monitoring
May et al. BigBug: Practical concurrency analysis for SDN
CN107305524B (zh) 压力测试方法及系统
Showerman et al. Large scale system monitoring and analysis on blue waters using ovis
US20210286704A1 (en) Runtime metrics based test ordering
Sun et al. The study of data collecting based on kprobe
He et al. Design and implementation of automation testing framework based on keyword driven
Sheppard et al. First-year results from a research program on human factors in software engineering
CN111142854A (zh) 一种微处理器的信息模型建模及生成方法

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 13768421

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205N DATED 14/12/2014)

122 Ep: pct application non-entry in european phase

Ref document number: 13768421

Country of ref document: EP

Kind code of ref document: A1