CN107861873A - Priorities of test cases method of adjustment based on the adjustment of two attribute hierarchies - Google Patents
Priorities of test cases method of adjustment based on the adjustment of two attribute hierarchies Download PDFInfo
- Publication number
- CN107861873A CN107861873A CN201711071737.2A CN201711071737A CN107861873A CN 107861873 A CN107861873 A CN 107861873A CN 201711071737 A CN201711071737 A CN 201711071737A CN 107861873 A CN107861873 A CN 107861873A
- Authority
- CN
- China
- Prior art keywords
- case
- test
- adjustment
- test case
- failure
- Prior art date
- Legal status (The legal status 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 status listed.)
- Granted
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/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/3688—Test management for test execution, e.g. scheduling of test suites
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
The public priorities of test cases method of adjustment based on the adjustment of two attribute hierarchies of the present invention, comprises the following steps：Step 1, the division and extraction to test use cases；Step 2, the decoupling of test use cases division result；Step 3, priority dynamic adjusts.Priorities of test cases method of adjustment of the present invention establishes incidence relation by the use-case for concentrating test case and two attributes, by decoupling and dividing adjustment grade, enter Mobile state adjustment priority to use-case in measuring executing process, it the method increase the accuracy of test cases selection to be adjusted, the run time that mistake is found in test can be shortened, testing efficiency is improved, there is good practical value.
Description
Technical field
The invention belongs to Computetr Software Testing Method technical field, and in particular to it is a kind of based on two attribute hierarchies adjustment
Priorities of test cases method of adjustment.
Background technology
In recent years, people are being continuously increased to computer requirements, and software developer grinds to meet the needs of people
More life softwares are sent out so that the quantity of Mobile solution increases rapidly, and Mobile solution species becomes more varied.By
More and more in application software function, the service logic inside software module with intermodule also becomes increasingly complex, and causes software to go out
The probability of existing defect greatly increases.Therefore, test is carried out to it after the part of functions of software is completed to be very important.So
And because software development time is compact in actual test, it is very limited to leave the time of test process for, during to a software test
The time for finding mistake is virtually extended fully according to original sequence implementation of test cases, reduces testing efficiency.
Each test case is not isolated, there may be certain relation between them, can will according to this feature
Test case concentrates pending use-case to be contacted with finding that the use-case of defect is established, and adjusts holding for these use-cases in the process of implementation
Row order, it is therefore intended that find the defects of same or similar as soon as possible.Meanwhile the attribute of test case has a variety of, which selects
Attribute divides to test use cases, determines the tightness degree of the test case contact in same " domain ".And
Adjustment amplitude on use-case can influence to find the time of defect, only find suitable division attribute and Adjusted Option, can just have
Effect shortens the time for finding mistake.
The content of the invention
It is an object of the invention to provide a kind of priorities of test cases method of adjustment based on the adjustment of two attribute hierarchies, solve
Coupling, selection test case specific aim to be adjusted be strong between test case and its attribute existing for existing software and adjustment
The problem of dynamics is single.
The technical solution adopted in the present invention is the priorities of test cases method of adjustment adjusted based on two attribute hierarchies,
Comprise the following steps：
Step 1, the division and extraction to test use cases
According to design sense partition testing set of uses case, the test use cases for possessing shared function type are then extracted；
Step 2, the decoupling of test use cases division result
The thought of scene method is used for reference, " result scene " is supplemented after Action Events stream terminates：Because designer not only provides
The expected result that each test case runs succeeded, and the conventional scenario that pre- cicada its execution is unsuccessfully likely to occur, therefore draw
Enter " failure result scene can be predicted ", providing its for test case corresponding to each design sense exclusive " can predict failure
As a result scene "；By contrasting actual failure scene and " failure result scene can be predicted ", improve to causing test case to perform mistake
The accuracy that the design sense lost judges；
Step 3, priority dynamic adjusts
Use-case classifying and dividing will be not carried out first to lift use-case, two-stage hoisting use-case for one-level and use-case wouldn't be adjusted；
Initialization sequence is then carried out according to the history implementation status of each test case；Finally enter row major according to initialization ranking results
Level adjustment.
It is of the invention to be further characterized in that,
The specific gymnastics conduct of step 1：
Step 1.1, partition testing set of uses case should follow following principle：Test case concentrates multiple test cases can be from
Same design sense, test case concentrate a test case also can include or cover multiple design senses；
Step 1.2, extract and possess the test use cases of shared function type and should follow and ask following principle：It is different when belonging to
During the situation of functional module but test case comprising same operation function, multiple test cases can belong to same function class
Type, remaining test case can only cover One function type.
Step 2 concrete operations are：
If any design sense is d, " can predict failure result scene " is fau (d), " can predict failure result scene " collection
Fau (d) is combined into, then Fau (d)={ fau (d)1,fau(d)2,...,fau(d)m, wherein m >=1；
Element in failure scene set is obtained by enumerating mode, and its element number can be one or more；If certain
One test case performs failure, and this test case covers multiple design senses, then by the actual failure of the test case
Scene, matched one by one with the element in the failure scene set of its each design sense included, if actual failure scene
With wherein a certain Match of elemental composition success, then the set belonging to this element, as target design meaning " can predict failure result field
Scape " set Fau (d), and then determine target design meaning.
The specific operation process of step 3 is：
Step 3.1, it is not carried out use-case classifying and dividing：If in test process, a certain test case performs failure, then with this
Failure testing use-case had both belonged to same function type, and the test case comprising same design meaning is classified as one-level lifting use-case；
Same function type will be belonged to, or the test case comprising same design meaning is classified as two-stage hoisting use-case；Both the above it
Outer test case is classified as that use-case wouldn't be adjusted；
Step 3.2, according to the history implementation status of test case and functional module classification order, to each in step 3.1
Test case carries out initialization sequence；
Step 3.3, sorted according to initialization in step 3.2, the implementation of test cases since highest priority, if surveying
Certain use-case performs failure during examination, i.e. implementing result is different from expected results, then one-level in step 3.1 first is lifted into use-case
Priority lifting is to after currently performing use-case, if the test case only covers a design sense, directly by step 3.1
Middle two-stage hoisting use-case is calculated according to formula (1), and lifting amplitude is adjusted；If the test case covers multiple design meanings
Justice, then first pass through and determine target design meaning using step 2, then by two-stage hoisting use-case in step 3.1 according to formula (1), meter
Lifting amplitude is calculated to be adjusted；
Δ range=c (caseNum-exeNum-lv1Num) (1)
Wherein, Δ range is the number of degrees for needing to be lifted；CaseNum is that test case concentrates the total use-case number included；
ExeNum is the use-case number of executed；Lv1Num represents to have been determined as the number of one-level lifting use-case；C is grade lifting system
Number, for controlling the size of lifting grade, and c ∈ (0,1).
History implementation status is specially the error detection rate or errorlevel of test case in step 3.2.
The beneficial effects of the invention are as follows：A kind of priorities of test cases adjustment side based on the adjustment of two attribute hierarchies of the present invention
Method establishes incidence relation by the use-case for concentrating test case and two attributes, by decoupling and dividing adjustment grade, is surveying
Enter Mobile state adjustment priority in examination implementation procedure to use-case, the method increase the accuracy of test cases selection to be adjusted,
The run time that mistake is found in test can be shortened, testing efficiency is improved, there is good practical value.
Brief description of the drawings
Fig. 1 is the flow chart of priorities of test cases method of adjustment of the present invention based on the adjustment of two attribute hierarchies；
Fig. 2 is the flow chart of " result scene " in priorities of test cases method of adjustment of the present invention；
Fig. 3 is the graph of a relation of priorities of test cases adjustment of the present invention；
Fig. 4 is method of adjustment of the present invention and other each priority algorithm effect contrast figures；
Fig. 5 is average defect discovery rate (APFD) value comparison diagram of method of adjustment of the present invention and other each priority algorithms.
Embodiment
The present invention is described in detail with reference to the accompanying drawings and detailed description.
The present invention it is a kind of based on two attribute hierarchies adjustment priorities of test cases method of adjustment, as shown in figure 1, including with
Lower step：
Step 1, the division and extraction to test use cases
Step 1.1, partition testing set of uses case should follow following principle：
(1) test case concentrates multiple test cases can be from same design sense, such as conventional test side
Method --- equivalence class classifying method, can the test case in effective equivalence class all embodies test program realize the mesh of predetermined function
, can the test case in invalid equivalence class all embodies test program avoid invalid input from causing abnormal purpose；(2) one
Individual execution action there may be multiple operating results, and these operating results be all judge institute's One function it is whether perfect according to
According to, therefore test case concentrates a test case also can include or cover multiple design senses.Based on above principle, such as table 1
It is shown, provide following test case-design sense incidence matrix example：
1 use-case of table-design sense incidence matrix
Step 1.2, extract and possess the test use cases of shared function type and should follow and ask following principle：
When belonging to the situation of difference in functionality module but test case comprising same operation function, multiple test cases can
Belong to same function type, remaining test case can only cover One function type.
The function type for having at least two module all to contain is referred to as shared function type fc, extracts a shared function
Type set FC={ fc1,fc2,...,fck, wherein k >=0, shared function type set FC include the whole of use-case to be tested
Shared function type.Use-case in test use cases is farthest distributed to each element in FC, it is remaining unassigned
Test case, i.e., be no longer participate in being related to the judgement and adjustment of function type comprising the only functional of module.It is as shown in table 2
Test case-function type incidence matrix example：
2 use-cases of table-function type incidence matrix
Step 2, the decoupling of test use cases division result
As shown in Fig. 2 using for reference the thought of scene method, " result scene " is supplemented after Action Events stream terminates：Due to design
Person not only provides the expected result that each test case runs succeeded, and the conventional field that pre- cicada its execution is unsuccessfully likely to occur
Scape, therefore introduce " failure result scene can be predicted ", for test case corresponding to each design sense provide its it is exclusive " can
Predict failure result scene "；By contrasting actual failure scene and " failure result scene can be predicted ", improve to causing test to be used
Example performs the accuracy that the design sense of failure judges；
If any design sense is d, " can predict failure result scene " is fau (d), " can predict failure result scene " collection
Fau (d) is combined into, then Fau (d)={ fau (d)1,fau(d)2,...,fau(d)m, wherein m >=1；
Element in failure scene set is obtained by enumerating mode, and its element number can be one or more；If certain
One test case performs failure, and this test case covers multiple design senses, then by the actual failure of the test case
Scene, matched one by one with the element in the failure scene set of its each design sense included, if actual failure scene
With wherein a certain Match of elemental composition success, then the set belonging to this element, as target design meaning " can predict failure result field
Scape " set Fau (d), and then determine target design meaning.
Step 3, priority dynamic adjusts
Step 3.1, it is not carried out use-case classifying and dividing：If in test process, a certain test case performs failure, then with this
Failure testing use-case had both belonged to same function type, and the test case comprising same design meaning is classified as one-level lifting use-case；
Same function type will be belonged to, or the test case comprising same design meaning is classified as two-stage hoisting use-case；Both the above it
Outer test case is classified as that use-case wouldn't be adjusted, as shown in figure 3, representing that test case lifts hierarchical relationship with set relations；
Step 3.2, according to the history implementation status of test case, as error detection rate, errorlevel etc. determine each use-case
Initial priority, or first it can be sorted out with functional module, sequentially it is defined by the entirety of functional module, to each in step 3.1
Individual test case carries out initialization sequence；
Step 3.3, sorted according to initialization in step 3.2, the implementation of test cases since highest priority, if surveying
Certain use-case performs failure during examination, i.e. implementing result is different from expected results, then one-level in step 3.1 first is lifted into use-case
Priority lifting is to after currently performing use-case, if the test case only covers a design sense, directly by step 3.1
Middle two-stage hoisting use-case is calculated according to formula (1), and lifting amplitude is adjusted；If the test case covers multiple design meanings
Justice, then first pass through and determine target design meaning using step 2, then by two-stage hoisting use-case in step 3.1 according to formula (1), meter
Lifting amplitude is calculated to be adjusted；
Δ range=c (caseNum-exeNum-lv1Num) (1)
Wherein, Δ range is the number of degrees for needing to be lifted；CaseNum is that test case concentrates the total use-case number included；
ExeNum is the use-case number of executed；Lv1Num represents to have been determined as the number of one-level lifting use-case；C is grade lifting system
Number, for controlling the size of lifting grade, and c ∈ (0,1).The setting of c values follows following principle：C value sizes are by tester
Depending on specific software under testing, if contact is close between each functional module of software under testing or function is more similar, such as management system
In the service logic of each management module there is very big similitude, at this moment c can use higher value；If each functional module of software under testing it
Between without prominent similitude, such as neither one manifest function feature or the functional type that wherein includes it is various, now c can
Take a smaller value.
As shown in figure 4, present invention invention is not sorted based on two attribute hierarchies adjustment algorithms (TA＆HA) and whole process
(Unsorted) and with functional domain partitioning algorithm (FUDD) in testing, the relation pair ratio of test case implementation rate and error detection rate
Figure, as shown in Figure 4：When testing the software with identical defects count, TA＆HA algorithms can be than other two kinds of algorithms
In the case where performing identical quantity test case, the defects of more is found, is advanced by the time for finding mistake.
As shown in figure 5, the present invention based on two attribute hierarchies adjustment algorithms (TA＆HA) with it is whole do not sort (Unsorted) and
With the APFD value comparison diagrams of functional domain partitioning algorithm (FUDD), as shown in Figure 5：APDF of the TA＆HA algorithms than other two kinds of algorithms
Value is high, has higher regulated efficiency, can quickly find software defect.
The priority level adjustment method of the present invention positions in terms of two attributes of design sense and function type and selects to wait to adjust
Whole use-case, and the adjustment amplitude of test case is divided into two grades, it is classified adjust according to actual conditions in the process of implementation, tool
There are more fine selection and adjustable strategies, software defect can be made to be concentrated in the short period and exposed, can effectively reduce test
Cost, improve the execution efficiency of test case.
Claims (5)
1. the priorities of test cases method of adjustment based on the adjustment of two attribute hierarchies, it is characterised in that comprise the following steps：
Step 1, the division and extraction to test use cases
According to design sense partition testing set of uses case, the test use cases for possessing shared function type are then extracted；
Step 2, the decoupling of test use cases division result
The thought of scene method is used for reference, " result scene " is supplemented after Action Events stream terminates：Due to designer not only provide it is each
The expected result that test case runs succeeded, and pre- cicada its conventional scenario for unsuccessfully being likely to occur of execution, therefore introducing " can
Predict failure result scene ", providing its for test case corresponding to each design sense exclusive " can predict failure result field
Scape "；By contrasting actual failure scene and " failure result scene can be predicted ", improve and set to causing test case to perform failure
Count the accuracy that meaning judges；
Step 3, priority dynamic adjusts
Use-case classifying and dividing will be not carried out first to lift use-case, two-stage hoisting use-case for one-level and use-case wouldn't be adjusted；Then
Initialization sequence is carried out according to the history implementation status of each test case；Finally priority tune is carried out according to initialization ranking results
It is whole.
2. the priorities of test cases method of adjustment according to claim 1 based on the adjustment of two attribute hierarchies, its feature exist
In the specific gymnastics conduct of the step 1：
Step 1.1, partition testing set of uses case should follow following principle：Test case concentrates multiple test cases can be from same
Individual design sense, test case concentrate a test case also can include or cover multiple design senses；
Step 1.2, extract and possess the test use cases of shared function type and should follow and ask following principle：When belonging to difference in functionality
During the situation of module but test case comprising same operation function, multiple test cases can belong to same function type, its
A test case of remaininging can only cover One function type.
3. the priorities of test cases method of adjustment according to claim 1 based on the adjustment of two attribute hierarchies, its feature exist
In step 2 concrete operations are：
If any design sense is d, " can predict failure result scene " is fau (d), " can predict failure result scene " collection is combined into
Fau (d), then Fau (d)={ fau (d)1,fau(d)2,...,fau(d)m, wherein m >=1；
Element in failure scene set is obtained by enumerating mode, and its element number can be one or more；If a certain survey
Example on probation performs failure, and this test case covers multiple design senses, then by the actual failure scene of the test case,
The element in failure scene set with its each design sense included is matched one by one, if actual failure scene with wherein
A certain Match of elemental composition success, then " failure result scene can be predicted " collection of the set belonging to this element, as target design meaning
Fau (d) is closed, and then determines target design meaning.
4. the priorities of test cases method of adjustment according to claim 1 based on the adjustment of two attribute hierarchies, its feature exist
In the specific operation process of the step 3 is：
Step 3.1, it is not carried out use-case classifying and dividing：If in test process, a certain test case performs failure, then with the failure
Test case had both belonged to same function type, and the test case comprising same design meaning is classified as one-level lifting use-case；Will category
In same function type, or test case comprising same design meaning is classified as two-stage hoisting use-case；Outside both the above
Test case is classified as that use-case wouldn't be adjusted；
Step 3.2, according to the history implementation status of test case and functional module classification order, to each test in step 3.1
Use-case carries out initialization sequence；
Step 3.3, sorted according to initialization in step 3.2, the implementation of test cases since highest priority, if testing
Certain use-case performs failure in journey, i.e. implementing result is different from expected results, then one-level in step 3.1 first is lifted into the preferential of use-case
Level lifting is to after currently performing use-case, if the test case only covers a design sense, directly by step 3.1 two
Level lifting use-case is calculated according to formula (1), and lifting amplitude is adjusted；If the test case covers multiple design senses,
Then first pass through and determine target design meaning using step 2, then by two-stage hoisting use-case in step 3.1 according to formula (1), calculating carries
Increasing degree degree is adjusted；
Δ range=c (caseNum-exeNum-lv1Num) (1)
Wherein, Δ range is the number of degrees for needing to be lifted；CaseNum is that test case concentrates the total use-case number included；
ExeNum is the use-case number of executed；Lv1Num represents to have been determined as the number of one-level lifting use-case；C is grade lifting system
Number, for controlling the size of lifting grade, and c ∈ (0,1).
5. the priorities of test cases method of adjustment according to claim 4 based on the adjustment of two attribute hierarchies, its feature exist
In history implementation status is specially the error detection rate or errorlevel of test case in the step 3.2.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201711071737.2A CN107861873B (en) | 2017-11-03 | 2017-11-03 | Test case priority adjusting method based on two-attribute hierarchical adjustment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201711071737.2A CN107861873B (en) | 2017-11-03 | 2017-11-03 | Test case priority adjusting method based on two-attribute hierarchical adjustment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107861873A true CN107861873A (en) | 2018-03-30 |
| CN107861873B CN107861873B (en) | 2020-07-28 |
Family
ID=61700743
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201711071737.2A Active CN107861873B (en) | 2017-11-03 | 2017-11-03 | Test case priority adjusting method based on two-attribute hierarchical adjustment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107861873B (en) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110515843A (en) * | 2019-08-13 | 2019-11-29 | 成都飞机工业（集团）有限责任公司 | Test case prioritization method based on defect set and inverted index |
| CN111008137A (en) * | 2019-12-06 | 2020-04-14 | 广州品唯软件有限公司 | Method and system for customizing test set |
| CN111510839A (en) * | 2020-04-13 | 2020-08-07 | 广东思派康电子科技有限公司 | Testing method and testing system of earphone |
| CN113094251A (en) * | 2019-12-23 | 2021-07-09 | 深圳奇迹智慧网络有限公司 | Embedded system testing method and device, computer equipment and storage medium |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20090217246A1 (en) * | 2008-02-27 | 2009-08-27 | Nce Technologies, Inc. | Evaluating Software Programming Skills |
| CN101599044A (en) * | 2008-06-05 | 2009-12-09 | 国网南京自动化研究院 | A kind of manner of execution of test case |
| CN102880545A (en) * | 2012-08-30 | 2013-01-16 | 中国人民解放军63928部队 | Method for dynamically adjusting priority sequence of test cases |
| CN103500142A (en) * | 2013-10-12 | 2014-01-08 | 南京大学 | Method for testing multiple target test case priorities facing dynamic Web application |
| CN105446885A (en) * | 2015-12-28 | 2016-03-30 | 西南大学 | Regression testing case priority ranking technology based on needs |
| CN106874199A (en) * | 2017-02-10 | 2017-06-20 | 腾讯科技（深圳）有限公司 | Test case treating method and apparatus |
-
2017
- 2017-11-03 CN CN201711071737.2A patent/CN107861873B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20090217246A1 (en) * | 2008-02-27 | 2009-08-27 | Nce Technologies, Inc. | Evaluating Software Programming Skills |
| CN101599044A (en) * | 2008-06-05 | 2009-12-09 | 国网南京自动化研究院 | A kind of manner of execution of test case |
| CN102880545A (en) * | 2012-08-30 | 2013-01-16 | 中国人民解放军63928部队 | Method for dynamically adjusting priority sequence of test cases |
| CN103500142A (en) * | 2013-10-12 | 2014-01-08 | 南京大学 | Method for testing multiple target test case priorities facing dynamic Web application |
| CN105446885A (en) * | 2015-12-28 | 2016-03-30 | 西南大学 | Regression testing case priority ranking technology based on needs |
| CN106874199A (en) * | 2017-02-10 | 2017-06-20 | 腾讯科技（深圳）有限公司 | Test case treating method and apparatus |
Cited By (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110515843A (en) * | 2019-08-13 | 2019-11-29 | 成都飞机工业（集团）有限责任公司 | Test case prioritization method based on defect set and inverted index |
| CN110515843B (en) * | 2019-08-13 | 2022-05-06 | 成都飞机工业（集团）有限责任公司 | Test case priority ordering method based on defect set and inverted index |
| CN111008137A (en) * | 2019-12-06 | 2020-04-14 | 广州品唯软件有限公司 | Method and system for customizing test set |
| CN111008137B (en) * | 2019-12-06 | 2023-06-23 | 广州品唯软件有限公司 | Method and system for customizing test set |
| CN113094251A (en) * | 2019-12-23 | 2021-07-09 | 深圳奇迹智慧网络有限公司 | Embedded system testing method and device, computer equipment and storage medium |
| CN113094251B (en) * | 2019-12-23 | 2024-02-23 | 深圳奇迹智慧网络有限公司 | Method and device for testing embedded system, computer equipment and storage medium |
| CN111510839A (en) * | 2020-04-13 | 2020-08-07 | 广东思派康电子科技有限公司 | Testing method and testing system of earphone |
| CN111510839B (en) * | 2020-04-13 | 2021-10-29 | 广东思派康电子科技有限公司 | Testing method and testing system of earphone |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107861873B (en) | 2020-07-28 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107861873A (en) | Priorities of test cases method of adjustment based on the adjustment of two attribute hierarchies | |
| Charrad et al. | NbClust: an R package for determining the relevant number of clusters in a data set | |
| CN112465040B (en) | Software defect prediction method based on class unbalance learning algorithm | |
| CN104965787B (en) | A kind of two benches Software Defects Predict Methods based on three decision-makings | |
| EP4060607A1 (en) | Information processing device, information processing method, and program | |
| CN105389480B (en) | Multiclass imbalance genomics data iteration Ensemble feature selection method and system | |
| CN107391369A (en) | A kind of spanned item mesh failure prediction method based on data screening and data oversampling | |
| CN107579846B (en) | Cloud computing fault data detection method and system | |
| CN110059714A (en) | Diagnosis Method of Transformer Faults based on multi-category support vector machines | |
| CN108766559A (en) | Clinical decision support method and system for intelligent disorder in screening | |
| CN105975611A (en) | Self-adaptive combined downsampling reinforcing learning machine | |
| CN111539451A (en) | Sample data optimization method, device, equipment and storage medium | |
| CN108829878A (en) | A kind of industry experiment data abnormal point detecting method and device | |
| CN109886284A (en) | Fraud detection method and system based on hierarchical clustering | |
| CN111522743B (en) | Software defect prediction method based on gradient lifting tree support vector machine | |
| CN106250913B (en) | A kind of combining classifiers licence plate recognition method based on local canonical correlation analysis | |
| CN107247450A (en) | Circuit breaker failure diagnostic method based on Bayesian network | |
| CN109919166A (en) | The method and apparatus for obtaining the classification information of attribute | |
| CN107193993A (en) | The medical data sorting technique and device selected based on local learning characteristic weight | |
| CN110515843A (en) | Test case prioritization method based on defect set and inverted index | |
| CN110020868A (en) | Anti- fraud module Decision fusion method based on online trading feature | |
| CN109117810A (en) | Fatigue driving behavioral value method, apparatus, computer equipment and storage medium | |
| CN113343123B (en) | Training method and detection method for generating confrontation multiple relation graph network | |
| CN110334773A (en) | Model based on machine learning enters the screening technique of modular character | |
| CN113469252A (en) | Extra-high voltage converter valve operation state evaluation method considering unbalanced samples |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |