WO2013139081A1 - Method for managing test cases - Google Patents

Method for managing test cases Download PDF

Info

Publication number
WO2013139081A1
WO2013139081A1 PCT/CN2012/075800 CN2012075800W WO2013139081A1 WO 2013139081 A1 WO2013139081 A1 WO 2013139081A1 CN 2012075800 W CN2012075800 W CN 2012075800W WO 2013139081 A1 WO2013139081 A1 WO 2013139081A1
Authority
WO
WIPO (PCT)
Prior art keywords
test case
test
defect
defects
bni
Prior art date
Application number
PCT/CN2012/075800
Other languages
French (fr)
Chinese (zh)
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 WO2013139081A1 publication Critical patent/WO2013139081A1/en

Links

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/3692—Test management for test results analysis

Definitions

  • the invention relates to the field of software testing, and in particular to a method for managing measurement and deletion columns.
  • test cases Before testing soft ⁇ products, a large number of test cases need to be written, and a software product developed by a company will be continuously upgraded and revised, so that the test cases of the software products are very important for regression testing after the upgrade.
  • the product is fired, usually for a limited time, but the release time is not ffi 3 ⁇ 43 ⁇ 4. How to determine the importance and priority of the test case, and maximize the efficiency of the Xia in a limited time?
  • the existing methods are generally 3 ⁇ 4; the test manager's experience and the importance of the function are decided, but the disadvantages of this are: The human experience is sometimes one-sided, and ignores the important historical data of the defects found in previous tests. In fact, there are more defects in the operation, and the remaining defects can be minimized in the limited time before the release, which will improve the quality of the software products.
  • the common test procedures used today are: In the requirements analysis and the i ⁇ 3 ⁇ 4J phase, the 3 ⁇ 4A members participate in the review, write the test plan, clarify the scope of the test, measure the time of the test, the personnel, and the time point of the test line; During the encoding process, the 3 ⁇ 4 ⁇ 4 employee synchronization is measured.
  • Example design and writing When the software development is completed, the tester performs the test according to the completed test, reports the test results, and the discovered defects are found in the defect surface library; the test execution is periodic, the cycle test The focus of the cycle is different, but the basis of the cycle test is the test case, and with the deepening of the test, the lake case is continuously supplemented and perfected; after the test, according to the quality of the discovered defect analysis software, the review is released, according to the review conclusion, Defects in the continuation of the decision-making problem are still in the positive.
  • the test case design method generally includes fiber phens, boundary value, and gland method.
  • the lake case can also be classified according to the purpose: functional test and non-functional test (including performance test, stability test, usability test, compatibility). Testing, etc.) o Only after completing the 3 ⁇ 4 test, the quality of a software product can be guaranteed.
  • auxiliary testing tools including functional testing tools such as
  • test management tools can effectively manage the requirements, test cases, defects, and the corresponding wire between the builders, to facilitate the coverage of the test being tested, and to measure the rate of the pill, but the priority of the test is 3 ⁇ 4 ⁇ 4
  • the level needs to be manually set by the human, and there is no fi ⁇ ⁇ recognition.
  • the embodiment of the present invention withdraws a method for managing test cases, which can automatically identify Measure the priority level of the column.
  • a method for managing the deletion and deletion of the invention comprising:
  • test library attribute includes a test ID for uniquely marking the test case; the number of defects used to record the number of defects tested by the test case;
  • test case's ffifflfH ten test 3 ⁇ 43 ⁇ 4 case priority level According to the pre-defined algorithm, and the test case's ffifflfH ten test 3 ⁇ 43 ⁇ 4 case priority level.
  • the test in the test process of the prior software product, the test is repeatedly performed. If the defect is found in the test, the J is found to be associated with the defect and the number of defects is found. A large number of test cases, indicating that they have strong ability to find defects, should be focused on in future tests, so as long as the number of defects corresponding to the test case is recorded, according to the predefined algorithm, the priority of the test can be automatically calculated. Level, improve test efficiency.
  • FIG. 1 is a diagram showing an example of managing a beach in the case of a money in the present invention.
  • the test case library wherein, the test library attribute includes a test ID, for unique! 3 ⁇ 4 test 3 ⁇ 4 ⁇ 4 cases; the number of defects, used to record the number of defects tested by the test case; After performing the test, if a test fails, a defect record is automatically generated, and the number of defects corresponding to the test deletion column is increased; the algorithm according to the job definition, and the attribute of the example, the fiSft ten example Priority level.
  • the attribute of the test library includes a corresponding defect ID for recording the defect ID of the beach type.
  • the number of defect IDs can also be calculated as the value of the defect number attribute.
  • the number of defects attribute can also be used in this case, and the "defect ID" is another type of "number of defects" attribute.
  • the system builds a Bug library; the attributes of the defect library include: Defect ID, Depression, Measurement, ID, and Detecting the defect. ID, i3 ⁇ 4 students recorded the correlation between the defect and the test, as well as some attributes of the defect itself (such as testing environment, execution steps, defect performance, defect isolation, etc., the scope of these attribute defect records, ⁇ not - detailed) o
  • the step of measuring the attributes of the library includes: an execution status, a method for determining whether the ia is a row, and a result of the execution, usually including '3 ⁇ 4t',
  • Priority level used for 3 ⁇ 43 ⁇ 4 test 3 ⁇ 4 ⁇ 4 cases of priority level, usually can include 'high', 'medium', 'low', "not set” four states. Under the initial state, un-tree Pill line The test case, its execution status is "not executed", the defect ID of X inch should be empty, and the priority level is "not set”.
  • FIG. 1 is a flow chart showing a method for managing test cases according to an embodiment of the present invention.
  • the party ffife includes:
  • Step 101 Perform a beach ruin column
  • Step 102 Determine whether the test case is successfully executed; if the execution is successful, perform step 103; otherwise, perform step 104;
  • Step 103 The execution state of the test is set to "end.”
  • Step 104 The execution state of the test deletion column is set to "nen"
  • M 105 Automatically generate a defect record, assign a unique ID to the defect, fill the test case ID with the defect attribute, and fill the defect ID into the defect ID attribute of the test case.
  • the description information of the test is automatically converted into the execution step attribute of the defect, and at the time, the member may add other defect attributes to the cornerstone.
  • Step 106 Define the algorithm, as well as the view, the properties of the example, iim new refresh test, delete the special level.
  • the predefined algorithm can be:
  • the corresponding priority level is from high to low.
  • Ci 3 ⁇ 43 ⁇ 4 Assume that a 3 ⁇ 43 ⁇ 4 example ID is used in Ci 3 ⁇ 43 ⁇ 4 to defect in the BNi 3 ⁇ 4 « Ci" Defect ID" attribute Number

Abstract

An embodiment of the present invention provides a method for managing test cases. The method for managing test cases comprises: establishing a test case library, attributes of the test case library comprising a test case ID used for uniquely identifying a test case and a defect number used for recording the number of defects tested by the test case; after executing the test case, if execution of the test case is failed, automatically generating a defect record and meanwhile adding the defect number corresponding to the test case; and re-computing, according to a predefined algorithm and an attribute value of the test case, a priority level of the test case. The priority level of the test case can be automatically identified.

Description

一禾 剛例白循  Yihe
本发明涉及软件测试领域， 特别一种管理测删列的方法。
Figure imgf000002_0001
The invention relates to the field of software testing, and in particular to a method for managing measurement and deletion columns.
Figure imgf000002_0001
进行软 ί牛产品测试前， 需要编写大量的测试用例， 而一个公司开发 的软件产品会不断的升级和改版， 这样该软件产品的测试用例对升级后 进行回归测试非常重要。 尤 产品发械， 通常时间有限， 但发布时 间无 ffi ¾¾， 如何确定测试用例的重要性和优先级别， 在有限的时间获 得最大化的霞效率？  Before testing soft 牛牛 products, a large number of test cases need to be written, and a software product developed by a company will be continuously upgraded and revised, so that the test cases of the software products are very important for regression testing after the upgrade. In particular, the product is fired, usually for a limited time, but the release time is not ffi 3⁄43⁄4. How to determine the importance and priority of the test case, and maximize the efficiency of the Xia in a limited time?
现有常用的方式一般 ¾ί；测试经理的经验以及功能的重要 来决 定， 但这样做的缺点是： 人的经验有时是片面的， 并且忽略了以往测试 发现的缺陷这一重要的历史数据， 一般而言， 出现错误比较多的功 ¾t 留的缺陷也比较多， 在发布前的有限时间里， 能够将遗留缺陷降低到最 小繊， 通会提高软件产品的质量。  The existing methods are generally 3⁄4; the test manager's experience and the importance of the function are decided, but the disadvantages of this are: The human experience is sometimes one-sided, and ignores the important historical data of the defects found in previous tests. In fact, there are more defects in the operation, and the remaining defects can be minimized in the limited time before the release, which will improve the quality of the software products.
现今常用的测试流程是： 在需求分析和 i†¾J阶段， 测 ¾A员参与评 审， 编写测试计划， 明确测试的范围、 测 i纖略、 mi rn, 人员和测 丸行的时间点； 在软件编码过程中， 测 ¾Α员同步的开¾¾行测 例的设计和编写； 当软件开发完成后駭测试， 测 ¾A员根据编写完成 的测删列执行测试， 报告测试结果， 发现的缺陷駭到缺陷麵库； 测试的执行是周期性的， 周期测试的侧重点不同， 但 周期测试 的依据就是测试用例， 并且随着测试的深入， 测湖例是不断补充完善 的； 测 成后， 根据发现的缺陷分析软件的质量， 发布评审， 根 据评审结论， 决定题续修翻 的缺陷还是正 布。 The common test procedures used today are: In the requirements analysis and the i†3⁄4J phase, the 3⁄4A members participate in the review, write the test plan, clarify the scope of the test, measure the time of the test, the personnel, and the time point of the test line; During the encoding process, the 3⁄4⁄4 employee synchronization is measured. Example design and writing; When the software development is completed, the tester performs the test according to the completed test, reports the test results, and the discovered defects are found in the defect surface library; the test execution is periodic, the cycle test The focus of the cycle is different, but the basis of the cycle test is the test case, and with the deepening of the test, the lake case is continuously supplemented and perfected; after the test, according to the quality of the discovered defect analysis software, the review is released, according to the review conclusion, Defects in the continuation of the decision-making problem are still in the positive.
测试用例的设计方法一般包括 纖吩、 边界值、 腺撒则法， 测湖例一般还可以按照用途分类： 功能测试和非功能测试 （包括性能 测试、 稳定性测试、 易用性测试、 兼容性测试等） o 只有完成 ¾测试 后， 一个软件产品的质財能得到保证。  The test case design method generally includes fiber phens, boundary value, and gland method. The lake case can also be classified according to the purpose: functional test and non-functional test (including performance test, stability test, usability test, compatibility). Testing, etc.) o Only after completing the 3⁄4 test, the quality of a software product can be guaranteed.
当前市面上包含有各种辅助的测试工具， 包括功能测试工具如 The market currently includes a variety of auxiliary testing tools, including functional testing tools such as
QTP、 Winrunner, 性能测 ¾ 具如 Loadmnner、 Robot等， 还有测 ¾¾¾ 工具如 Testdirector, 该工具可以进行测试 i ¾J管理、 测 例管理、 缺 陷的管理。 现存的测试管理工具可以有效的管理需求、 测试用例、 缺 陷， 并可以建 者之间的对应絲， 方便得到需求被测试的覆盖率、 测¾¾例«丸行的 率， 但测¾¾例的优先级别是需要人为手工设置 的， 并没有 fi^咱动识别。 鰂内容 QTP, Winrunner, performance measurements such as Loadmnner, Robot, etc., as well as tools such as Testdirector, which can be used to test i 3⁄4J management, test management, and defect management. The existing test management tools can effectively manage the requirements, test cases, defects, and the corresponding wire between the builders, to facilitate the coverage of the test being tested, and to measure the rate of the pill, but the priority of the test is 3⁄4⁄4 The level needs to be manually set by the human, and there is no fi^ 咱 recognition.鲗Content
为此， 本发明实施例撤了一种管理测试用例的方法， 能自动识别 测删列优先级别。 To this end, the embodiment of the present invention withdraws a method for managing test cases, which can automatically identify Measure the priority level of the column.
本发明撤的一种管理测删列方法， 包括： A method for managing the deletion and deletion of the invention, comprising:
ma m 其中， 测¾¾例库属性包括测 ¾¾例 ID， 用于唯 一标示测试用例； 缺陷数目， 用于记录由该测试用例测试出的缺陷数 目；  Ma m , where the test library attribute includes a test ID for uniquely marking the test case; the number of defects used to record the number of defects tested by the test case;
在执行测湖例后， 如果测 i烟例执行失败， 自动产生一条缺陷记 录， 同时增加该测删列对应的缺陷数目；  After the execution of the lake measurement example, if the execution of the test sample fails, a defect record is automatically generated, and the number of defects corresponding to the test deletion column is increased;
根据预先定义的算法， 以及测试用例的属 ffifflfH十算测¾¾例的 优先级别。  According to the pre-defined algorithm, and the test case's ffifflfH ten test 3⁄43⁄4 case priority level.
利用本发明实施例 ¾ί共的技术方案， 在以往软件产品测试过程中， 测¾¾例反复执行， 如果该测 ¾¾例发现了缺陷， 贝 J在测¾¾例和缺陷 之间建立关联， 发现缺陷数量多的测试用例， 说明其发现缺陷的能力 强， 在以后的测试中应重点关注， 所以， 只要记录了测试用例对应的缺 陷数目， 根据预定义的算法， 就可以自动计算出测 ¾¾例的优先级别， 提高测试效率。
Figure imgf000004_0001
According to the technical solution of the embodiment of the present invention, in the test process of the prior software product, the test is repeatedly performed. If the defect is found in the test, the J is found to be associated with the defect and the number of defects is found. A large number of test cases, indicating that they have strong ability to find defects, should be focused on in future tests, so as long as the number of defects corresponding to the test case is recorded, according to the predefined algorithm, the priority of the test can be automatically calculated. Level, improve test efficiency.
Figure imgf000004_0001
图 1为本发明一錢例中一种管理灘畑例 ή妨法 ¾3呈图。 TE将结合附图及 例对本发明的技术方鍵行更详细的说明。 在本发明实施例中， 测试用例库； 其中， 测 i畑例库属性包括 测¾¾例 ID， 用于唯一! ¾测¾¾例； 缺陷数目， 用于记录由该测 例测试出的缺陷数目； 在执行测 i畑例后， 如果测 i畑例执行失败， 自 动产生一条缺陷记录， 同时增加该测删列对应的缺陷数目； 根据職 定义的算法， 以及观,例的属性 fiSft十算 例的优先级别。 FIG. 1 is a diagram showing an example of managing a beach in the case of a money in the present invention. TE will explain the technical side of the present invention in more detail in conjunction with the accompanying drawings and examples. In the embodiment of the present invention, the test case library; wherein, the test library attribute includes a test ID, for unique! 3⁄4 test 3⁄4⁄4 cases; the number of defects, used to record the number of defects tested by the test case; After performing the test, if a test fails, a defect record is automatically generated, and the number of defects corresponding to the test deletion column is increased; the algorithm according to the job definition, and the attribute of the example, the fiSft ten example Priority level.
在本发明另一实施例中， 测¾¾例库的属性包括对应的缺陷 ID， 用 于记录由该灘畑例灘式出的缺陷 ID。 謝缺陷 ID的数目也可以计算中 缺陷数目属性的值。 本领域技术人员可以理解， 此时缺陷数目属性也可 以^?在， "缺陷 ID"为'缺陷数目"属性的另一种 ¾¾方式。  In another embodiment of the present invention, the attribute of the test library includes a corresponding defect ID for recording the defect ID of the beach type. The number of defect IDs can also be calculated as the value of the defect number attribute. Those skilled in the art will appreciate that the number of defects attribute can also be used in this case, and the "defect ID" is another type of "number of defects" attribute.
此时， 系¾¾构建了一^ ¾陷 （Bug )库； 其中， 该缺陷库的属性包 括： 缺陷 ID, 唯 ^夬陷， 测¾¾例 ID， 用^ i己录发现该缺陷的 测¾¾例 ID， i¾ 生记录了缺陷与测 例相关性， 以及缺陷本身的一 些属性 （例如测浙境、 执行步骤、 缺陷表现、 缺陷隔离等， 这些属性 缺陷记录范围， 匕不——详述） o  At this time, the system builds a Bug library; the attributes of the defect library include: Defect ID, Depression, Measurement, ID, and Detecting the defect. ID, i3⁄4 students recorded the correlation between the defect and the test, as well as some attributes of the defect itself (such as testing environment, execution steps, defect performance, defect isolation, etc., the scope of these attribute defect records, 匕 not - detailed) o
在本发明另一实施例中， 测¾¾例库的属性 一步包括： 执行状 态， 用于 亥测 例是否 ia丸行以及执行的结果， 通常包括' ¾t'、  In another embodiment of the present invention, the step of measuring the attributes of the library includes: an execution status, a method for determining whether the ia is a row, and a result of the execution, usually including '3⁄4t',
"未执行'三个状态； 优先级别， 用于 ¾¾测¾¾例的优先级别， 通常可包括'高"、 "中"、 "低'、 "未设置"四个状态。 初始优态下， 未樹丸行 的测 例， 其执行状态为 "未执行'， X寸应的缺陷 ID 为空， 优先级别为 "未设置 "。 "Not executed" three states; Priority level, used for 3⁄43⁄4 test 3⁄4⁄4 cases of priority level, usually can include 'high', 'medium', 'low', "not set" four states. Under the initial state, un-tree Pill line The test case, its execution status is "not executed", the defect ID of X inch should be empty, and the priority level is "not set".
图 1 所示为本发明实施例所提供的一种管理测试用例的方法流程 图。 如图 1戶¾， 该方 ffife括：  FIG. 1 is a flow chart showing a method for managing test cases according to an embodiment of the present invention. As shown in Figure 1 household 3⁄4, the party ffife includes:
步骤 101 : 执行灘爛列；  Step 101: Perform a beach ruin column;
步骤 102 : 判断测试用例是否执行成功； 如果执行成功， 执行步骤 103 ; 否则执行步骤 104 ;  Step 102: Determine whether the test case is successfully executed; if the execution is successful, perform step 103; otherwise, perform step 104;
步骤 103 : 该测 例的执行状态置为" 呈结束。  Step 103: The execution state of the test is set to "end."
步骤 104： 该测删列的执行状态置为"嫩'；  Step 104: The execution state of the test deletion column is set to "nen";
M 105 : 自动产生一条缺陷记录， 为该缺陷分配唯一 ID， 将测试 用例 ID填入缺陷属性， 同时将该缺陷 ID填入到该测试用例的缺陷 ID属 性中。 在本发明一实施例中， 自动将该测 例的描述信息转换为缺陷 的执行步骤属性， 当时， 员可 匕基石 添加其他缺陷属性。  M 105 : Automatically generate a defect record, assign a unique ID to the defect, fill the test case ID with the defect attribute, and fill the defect ID into the defect ID attribute of the test case. In an embodiment of the invention, the description information of the test is automatically converted into the execution step attribute of the defect, and at the time, the member may add other defect attributes to the cornerstone.
步骤 106 : 定义的算法， 以及观,例的属性 iim新刷新测 删扁尤先级别。  Step 106: Define the algorithm, as well as the view, the properties of the example, iim new refresh test, delete the special level.
在本发明一 列中， 预定义的算法可以是：  In a column of the invention, the predefined algorithm can be:
根据测 i烟例对应的缺陷数目降溯咧以对应优先级别从高到低。 具体的算法描述如下：  According to the number of defects corresponding to the smoke test, the corresponding priority level is from high to low. The specific algorithm is described as follows:
假设测 ¾¾例 ID用 Ci ¾¾ 以 BNi ¾« Ci"缺陷 ID"属性中的缺陷 个数； Assume that a 3⁄43⁄4 example ID is used in Ci 3⁄43⁄4 to defect in the BNi 3⁄4 « Ci" Defect ID" attribute Number
计算所有 BNi > 0时， 平均的缺陷个数 E， E= (BN1 + BN2 + …… +BNn ) In , n为 BNi大于 0的测 例的个数；  When calculating all BNi > 0, the average number of defects E, E = (BN1 + BN2 + ...... + BNn ) In , n is the number of samples with BNi greater than 0;
首先棚画由高到纖测删列排序；  First, the shed paintings are sorted from high to fiber count;
将 BNi>= E S勺测 例的优先级设置为"高"；  Set the priority of the BNi>= E S spoon test to "High";
将 0<BNi<E的测 M 列的优先级设置为"中"；  Set the priority of the M column of 0<BNi<E to "Medium";
将 BNi = 0的测湖例的优先级设置为"低'。  Set the priority of the lake survey with BNi = 0 to "Low".
当然， 本领域技术人员可以理解， 还可以根据实际 f青况来为优先级 "高'、 "中"、 "低 '设置不同的界线。  Of course, those skilled in the art can understand that different boundaries can be set for the priorities "high", "medium", and "low" according to the actual f green condition.
利用本发明实施例 共的技术方案， 进行测试 i ¾j时， 即可根据测 删扁尤先级别 呲次誦尤先执行哪些灘纖列。  By using the common technical solution of the embodiment of the present invention, when testing i 3⁄4j, it is possible to execute which beach fiber columns are executed according to the test.

Claims

权利要求 Rights request
1、 一种管理测试用例的方法， 其特征在于， 包括： A method for managing a test case, comprising:
建立测试用例库； 其中， 测试用例库属性包括测试用例 ID, 用于唯 —标示测试用例； 缺陷数目， 用于记录由该测试用例测试出的缺陷数目； 在执行测试用例后，如果测试用例执行失败， 自动产生一条缺陷记录， 同时增加该测试用例对应的缺陷数目；  Establish a test case library; wherein, the test case library attribute includes a test case ID, which is used to uniquely mark the test case; the number of defects is used to record the number of defects tested by the test case; after executing the test case, if the test case is executed Failure, automatically generate a defect record, and increase the number of defects corresponding to the test case;
根据预先定义的算法， 以及测试用例的属性值重新计算测试用例的优 先级别。  The priority level of the test case is recalculated based on the predefined algorithm and the attribute values of the test case.
2、 如权利要求 1所述的方法， 其特征在于， 进一步包括： 构建了一个缺陷 （Bug) 库； 其中， 该缺陷库的属性包括： 缺陷 ID, 唯一标示每个缺陷； 测试用例 ID, 用于记录发现该缺陷的测试用例 ID, 该属性记录了缺陷与测试用例相关性。  2. The method of claim 1, further comprising: constructing a defect library; wherein the attributes of the defect library include: a defect ID, uniquely indicating each defect; and a test case ID, The test case ID that identifies the defect is recorded, and this attribute records the defect and test case relevance.
3、 如权利要求 1所述方法， 其特征在于， 进一步包括： 执行状态， 用于标示该测试用例是否被执行以及执行的结果； 优先级别， 用于标示测 试用例的优先级别。  3. The method of claim 1, further comprising: an execution state for indicating whether the test case is executed and a result of the execution; a priority level for indicating a priority level of the test case.
4、 如权利要求 1所述的方法， 其特征在于， 所述预先定义的算法 为： 根据测试用例对应的缺陷数目降序排列以对应优先级别从高到低。  The method according to claim 1, wherein the predefined algorithm is: sorting in descending order according to the number of defects corresponding to the test case to correspond to a priority level from high to low.
5、 如权利要求 4所述的方法， 其特征在于， 所述预先定义的算法为： 假设测试用例 ID用 Ci代表， 以 BNi代表 Ci "缺陷数目"属性中的 缺陷个数；  5. The method according to claim 4, wherein the predefined algorithm is: assuming that the test case ID is represented by Ci, and BNi represents the number of defects in the Ci "number of defects" attribute;
计算所有 BNi > 0时， 平均的缺陷个数 E， E = (BNI + BN2 + …… + BNn) /n， n为 BNi大于 0的测试用例的个数； 根据 BNi由高到低将测试用例排序； 以 E为界， BNi > E的测试用例设为高优先级测试用例。 When calculating all BNi > 0, the average number of defects E, E = (BNI + BN2 + ...... + BNn) / n, n is the number of test cases with BNi greater than 0; Test cases are ordered according to BNi from high to low; with E as the boundary, BNi > E test cases are set as high priority test cases.
PCT/CN2012/075800 2012-03-21 2012-05-21 Method for managing test cases WO2013139081A1 (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201210075982.1A CN102662833B (en) 2012-03-21 2012-03-21 Method for managing test cases
CN201210075982.1 2012-03-21

Publications (1)

Publication Number Publication Date
WO2013139081A1 true WO2013139081A1 (en) 2013-09-26

Family

ID=46772330

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2012/075800 WO2013139081A1 (en) 2012-03-21 2012-05-21 Method for managing test cases

Country Status (2)

Country Link
CN (1) CN102662833B (en)
WO (1) WO2013139081A1 (en)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9740590B2 (en) 2015-03-27 2017-08-22 International Business Machines Corporation Determining importance of an artifact in a software development environment
CN109189672A (en) * 2018-08-13 2019-01-11 中国平安人寿保险股份有限公司 Automatic test approach, server and the computer readable storage medium of micro services
CN111444101A (en) * 2020-03-27 2020-07-24 成都嗨学梅里教育科技有限公司 Method and device for automatically creating product test defects

Families Citing this family (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103902429B (en) * 2012-12-26 2016-08-31 北京新媒传信科技有限公司 The method of early warning, server and system is carried out in automatic test
CN104063307B (en) * 2013-03-19 2016-05-04 腾讯科技（深圳）有限公司 A kind of method for testing software and system
CN103473178B (en) * 2013-09-24 2017-08-04 上海斐讯数据通信技术有限公司 The method and system that a kind of optimal inspection flow is performed
CN103617118B (en) * 2013-11-28 2016-06-29 北京奇虎科技有限公司 The method that is uniformly processed of test result, Apparatus and system
CN107346283A (en) * 2016-05-05 2017-11-14 中兴通讯股份有限公司 Script processing method and device
CN106843947B (en) * 2017-01-04 2020-01-24 腾讯科技（深圳）有限公司 Method and device for processing code defects
CN107066391A (en) * 2017-05-09 2017-08-18 武汉联影医疗科技有限公司 The processing method and system of test case
CN107861876A (en) * 2017-11-16 2018-03-30 平安科技（深圳）有限公司 Method of testing, device, computer equipment and readable storage medium storing program for executing
CN109933509A (en) * 2017-12-15 2019-06-25 北京京东尚科信息技术有限公司 A kind of method and apparatus for realizing automatic test defect management
CN108073518A (en) * 2018-01-24 2018-05-25 广东睿江云计算股份有限公司 A kind of testing case management and device
CN110262956A (en) * 2018-03-12 2019-09-20 中移(苏州)软件技术有限公司 A kind of test cases selection method and device
CN109446061B (en) * 2018-09-17 2022-06-10 平安科技（深圳）有限公司 Page detection method, computer readable storage medium and terminal device
CN109271318A (en) * 2018-09-17 2019-01-25 郑州云海信息技术有限公司 A kind of method and device for the execution failure cause that test case is presented
CN109101431A (en) * 2018-09-26 2018-12-28 深圳壹账通智能科技有限公司 A kind of testing case management, computer readable storage medium and terminal device
CN109947656A (en) * 2019-03-29 2019-06-28 北京奇艺世纪科技有限公司 A kind of testing case management and device
CN110134594B (en) * 2019-04-19 2023-08-22 平安科技（深圳）有限公司 Function test method and device for application comprising account name and computer equipment

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101908017A (en) * 2010-06-01 2010-12-08 南京大学 Regression test case screening method based on partial multi-coverage
CN102063379A (en) * 2010-12-28 2011-05-18 天津市亚安科技电子有限公司 Data storage method of FLASH memory

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040154001A1 (en) * 2003-02-05 2004-08-05 Haghighat Mohammad R. Profile-guided regression testing
CN102063376B (en) * 2011-02-16 2013-01-16 哈尔滨工程大学 Test case selection method
CN102253889B (en) * 2011-08-07 2014-02-26 南京大学 Method for dividing priorities of test cases in regression test based on distribution

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101908017A (en) * 2010-06-01 2010-12-08 南京大学 Regression test case screening method based on partial multi-coverage
CN102063379A (en) * 2010-12-28 2011-05-18 天津市亚安科技电子有限公司 Data storage method of FLASH memory

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9740590B2 (en) 2015-03-27 2017-08-22 International Business Machines Corporation Determining importance of an artifact in a software development environment
US9747188B2 (en) 2015-03-27 2017-08-29 International Business Machines Corporation Determining importance of an artifact in a software development environment
CN109189672A (en) * 2018-08-13 2019-01-11 中国平安人寿保险股份有限公司 Automatic test approach, server and the computer readable storage medium of micro services
CN109189672B (en) * 2018-08-13 2024-03-29 中国平安人寿保险股份有限公司 Automatic testing method for micro-service, server and computer readable storage medium
CN111444101A (en) * 2020-03-27 2020-07-24 成都嗨学梅里教育科技有限公司 Method and device for automatically creating product test defects

Also Published As

Publication number Publication date
CN102662833A (en) 2012-09-12
CN102662833B (en) 2014-12-03

Similar Documents

Publication Publication Date Title
WO2013139081A1 (en) Method for managing test cases
EP2815319B1 (en) Code coverage rate determination method and system
US9442832B2 (en) User workflow replication for execution error analysis
CN107480039B (en) Small file read-write performance test method and device for distributed storage system
US8381184B2 (en) Dynamic test coverage
US11327742B2 (en) Affinity recommendation in software lifecycle management
WO2015022890A1 (en) Software aging test system, software agint test method, and program for software aging test
WO2011079685A1 (en) Method and device for magaging regression test
CN102568522A (en) Hardware performance test method and device
CN105389250A (en) Method and system for tracking software quality
CN108170366A (en) Storage medium management method, device and storage device in storage device
US9842044B2 (en) Commit sensitive tests
US8219858B2 (en) Method for testing hard disks under an extensible firmware interface
CN105630653A (en) CPU vacancy rate determination method and device for Docker container
JP2010003224A (en) Test information management server, test information management method and program
JP2015111326A (en) Electric power estimation method, electric power estimation device, and program
TW202125241A (en) Multi-instrument behavior synchronization using jobs and milestones
KR102103590B1 (en) Method for automatic test of program compatibility and apparatus using the same
CN113282482A (en) Compatibility test method and system for software package
CN107885640B (en) Hard disk management method and device
TWI424175B (en) System and method for formatting test data and machine-readable media
CN112667597B (en) Algorithm model full life cycle management tool system and implementation method thereof
CN105701002A (en) Test based execution path recording method and apparatus
CN112256578B (en) Management method and system for test cases, electronic equipment and storage medium
US11823011B2 (en) Analyzing execution of quantum services using quantum computing devices and quantum simulators

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: 12871630

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 12871630

Country of ref document: EP

Kind code of ref document: A1