CN111400176B - Test sequence generation method and system, test method and system of high-credibility software - Google Patents
Test sequence generation method and system, test method and system of high-credibility software Download PDFInfo
- Publication number
- CN111400176B CN111400176B CN202010161800.7A CN202010161800A CN111400176B CN 111400176 B CN111400176 B CN 111400176B CN 202010161800 A CN202010161800 A CN 202010161800A CN 111400176 B CN111400176 B CN 111400176B
- Authority
- CN
- China
- Prior art keywords
- test sequence
- tested
- sequence
- covered
- event
- 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.)
- Active
Links
- 238000012360 testing method Methods 0.000 title claims abstract description 218
- 238000000034 method Methods 0.000 title claims abstract description 44
- 238000010998 test method Methods 0.000 title abstract description 7
- 238000013101 initial test Methods 0.000 claims abstract description 41
- 230000009191 jumping Effects 0.000 claims abstract description 4
- 230000009467 reduction Effects 0.000 description 4
- 238000013522 software testing Methods 0.000 description 4
- 238000010276 construction Methods 0.000 description 3
- 230000003993 interaction Effects 0.000 description 2
- 230000009471 action Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 230000008878 coupling Effects 0.000 description 1
- 238000010168 coupling process Methods 0.000 description 1
- 238000005859 coupling reaction Methods 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000005065 mining Methods 0.000 description 1
- 230000008569 process Effects 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
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/3676—Test management for coverage analysis
-
- 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
Abstract
The invention discloses a test sequence generation method and system, a test method and system of high-reliability software. The test sequence generation method comprises the following steps: determining a sequence set to be covered according to the event set to be tested and the sequential coverage; determining an initial test sequence and taking the initial test sequence as a current test sequence; judging whether the current test sequence completely covers each sub-sequence to be covered or not; if not, each event to be tested in the event set to be tested is respectively and independently added to the back of the current test sequence to obtain a plurality of candidate test sequences; selecting the candidate test sequence with the largest number of the sequences to be covered from the candidate test sequences to replace the current test sequence, and jumping to the step of judging whether the current test sequence completely covers each sequence to be covered; if so, taking the current test sequence which completely covers each sub-sequence to be covered as the test sequence for testing the high-credibility software. The invention can reduce the SCA sequence coverage redundancy.
Description
Technical Field
The present invention relates to the field of high-reliability software testing, and in particular, to a method and a system for generating a test sequence of high-reliability software, and a test method and a test system thereof.
Background
The test of the high-reliability software provides important guarantee for the reliability of the high-reliability software. Event driven software testing techniques have found wide application in the field of high-trust software testing, with common examples spanning multiple fields, from embedded systems to web and GUI applications. Test methods based on event execution arrangement are common in the field of software testing. Existing T-way strategies are very useful for detecting interaction faults between parameters, especially at higher interaction strengths, but still lack support for testing event sequences or parameter occurrences. Kuhn et al provide an effective strategy using a combinatorial approach, table 1 shows an example of SCA generated by a sequential coverage array generator tool, and it can be seen from table 1 that 3-way sequential coverage of 4 events generates 8 test sequences.
TABLE 1 3-way coverage test sequence for four events
It can be seen that in the above method, the generation of the SCA coverage array does not take into account that multiple test sequences may simultaneously cover the same sequential event sub-sequence, thereby causing a problem of sequential coverage redundancy.
Disclosure of Invention
The invention aims to provide a test sequence generation method and system for high-credibility software, a test method and system, and a test program, which can reduce SCA sequence coverage redundancy.
In order to achieve the above object, the present invention provides the following solutions:
the invention provides a test sequence generation method of high-credibility software, which comprises the following steps:
determining a sequence coverage of an event set to be tested and an event to be tested;
determining a sequence set to be covered according to the event set to be tested and the sequential coverage power;
determining an initial test sequence and taking the initial test sequence as a current test sequence; the initial test sequence is a test sequence consisting of events to be tested in the event set to be tested;
judging whether the current test sequence completely covers each sub-sequence to be covered or not;
if not, each event to be tested in the event set to be tested is respectively and independently added to the back of the current test sequence to obtain a plurality of candidate test sequences;
selecting the candidate test sequence with the largest number of the sequences to be covered from the candidate test sequences to replace the current test sequence, and jumping to the step of judging whether the current test sequence completely covers each sequence to be covered;
and if so, taking the current test sequence which completely covers each to-be-covered subsequence as a test sequence for testing the high-reliability software.
Optionally, the determining the sequence set to be covered according to the event set to be tested and the sequential coverage degree specifically includes:
and taking t events to be tested from the event set to be tested to perform full-permutation and combination to obtain a sequence set to be covered, wherein t is the sequential coverage.
Optionally, the determining an initial test sequence specifically includes:
and determining a sequence obtained by randomly arranging all the events to be tested in the event set to be tested as the initial test sequence.
Optionally, before the determining the event set to be tested, the method further includes:
carrying out unified abstract expression on the events to be tested to obtain marks representing the events to be tested;
and constructing the event set to be tested by adopting the marks of the events to be tested.
The invention also provides a method for testing the high-credibility software, which comprises the following steps:
the test sequence is generated by adopting the test sequence generation method of the high-credibility software;
and testing the high-reliability software by adopting the test sequence.
The invention also provides a test sequence generation system of the high-credibility software, which comprises the following steps:
the parameter determining module is used for determining an event set to be tested and the sequential coverage of the events to be tested;
the to-be-covered subsequence determining module is used for determining a to-be-covered subsequence set according to the to-be-tested event set and the sequential coverage power;
the initial test sequence determining module is used for determining an initial test sequence and taking the initial test sequence as a current test sequence; the initial test sequence is a test sequence consisting of events to be tested in the event set to be tested;
the judging module is used for judging whether the current test sequence completely covers each sequence to be covered or not;
the candidate test sequence generation module is used for respectively and independently adding each event to be tested in the event set to be tested to the back of the current test sequence when the current test sequence does not completely cover each sub-sequence to be covered, so as to obtain a plurality of candidate test sequences;
the current test sequence updating module is used for selecting the candidate test sequence with the largest number of the sequences to be covered from the candidate test sequences to replace the current test sequence;
and the test sequence determining module is used for taking the current test sequence which completely covers each to-be-covered subsequence as the test sequence for testing the high-reliability software when the current test sequence completely covers each to-be-covered subsequence.
Optionally, the to-be-covered subsequence module specifically includes:
and the to-be-covered subsequence unit is used for taking t to-be-tested events from the to-be-tested event set to perform full permutation and combination to obtain the to-be-covered subsequence set, wherein t is the sequential coverage.
Optionally, the initial test sequence determining module specifically includes:
and the initial test sequence determining unit is used for determining a sequence obtained by randomly arranging all the events to be tested in the event set to be tested as the initial test sequence.
Optionally, the system further comprises:
the to-be-tested event abstract description module is used for carrying out unified abstract expression on to-be-tested events to obtain marks representing the to-be-tested events;
the event set to be tested building module is used for building the event set to be tested by adopting the marks of the events to be tested.
The invention also provides a test system of the high-credibility software, which comprises:
the invention provides a test sequence generation system of high-credibility software; and a test system for testing the high-trust software by adopting the test sequence.
According to the specific embodiment provided by the invention, the invention discloses the following technical effects: when a test sequence is generated, only one event to be tested is added in each step on the basis of the initial test sequence, then one candidate test sequence with the largest number of sequences to be covered is selected from a plurality of obtained candidate test sequences to replace the current test sequence, then whether the current test sequence covers all sequences to be covered is judged, if not, then one event to be tested is added after the current test sequence, and the operation is repeated until the obtained current test sequence covers all sequences to be covered. The invention greatly reduces the coverage redundancy of the SCA sequence.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings that are needed in the embodiments will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a flowchart of a test sequence generation method of high-reliability software in an embodiment of the invention;
FIG. 2 is a graph showing the relationship between the number of events included in a test sequence and the number of events to be tested according to an embodiment of the present invention;
fig. 3 is a schematic diagram of a test sequence generating system of high-reliability software according to an embodiment of the present invention.
Detailed Description
The following description of the embodiments of the present invention will be made clearly and completely with reference to the accompanying drawings, in which it is apparent that the embodiments described are only some embodiments of the present invention, but not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
In order that the above-recited objects, features and advantages of the present invention will become more readily apparent, a more particular description of the invention will be rendered by reference to the appended drawings and appended detailed description.
The first aspect of the present invention provides a method for generating a test sequence of high-trusted software, as shown in fig. 1, the method for generating the test sequence includes the following steps:
step 101: determining a sequence coverage of an event set to be tested and an event to be tested;
step 102: determining a sequence set to be covered according to the event set to be tested and the sequential coverage power;
step 103: determining an initial test sequence and taking the initial test sequence as a current test sequence; the initial test sequence is a test sequence consisting of events to be tested in the event set to be tested;
step 104: judging whether the current test sequence completely covers each sub-sequence to be covered or not;
step 105: if the current test sequence does not completely cover each sequence to be covered, each event to be tested in the event set to be tested is respectively and independently added to the back of the current test sequence, so that a plurality of candidate test sequences are obtained;
step 106: selecting the candidate test sequence with the largest number of the sequences to be covered from the candidate test sequences to replace the current test sequence, and jumping to step 104;
step 107: and if the current test sequence completely covers each to-be-covered subsequence, taking the current test sequence completely covering each to-be-covered subsequence as a test sequence for testing the high-reliability software.
In this embodiment, only one test event to be tested is added after the initial test sequence in each iteration until a test sequence capable of covering all the sub-sequences to be covered is obtained. Compared with the prior art, the test sequence generated by the embodiment greatly reduces coverage redundancy.
In an embodiment, as a preferred implementation, step 102 may specifically be:
and taking t events to be tested from the event set to be tested to perform full-permutation and combination to obtain a sequence set to be covered, wherein t is the sequential coverage. The sequential coverage force t refers to the sequential combined force of n events to be tested.
In an embodiment, as a preferred implementation, step 103 may specifically be:
and determining a sequence obtained by randomly arranging all the events to be tested in the event set to be tested as the initial test sequence. For example, a list of initial test sequences is generated according to the input order of the events to be tested.
The step mainly realizes the construction of an initial test sequence, and lays a foundation for the subsequent requirement of t-way sequence coverage by expanding the sequence. The realization method is that the input events to be tested are arranged into a column in sequence, wherein the sequence of the events is unconstrained. Taking four events a, b, c, d as an example, four times are listed in order to obtain an initial sequence: a-b-c-d.
In an embodiment, as a preferred implementation manner, before step 101, the method may further include:
carrying out unified abstract expression on the events to be tested to obtain marks representing the events to be tested;
and constructing the event set to be tested by adopting the marks of the events to be tested.
In this embodiment, a unified abstract expression is performed on an event to be tested that occurs in a software test process, for example, if a certain test event is a left turn control command execution, the test event can be abstracted into an event a, and a right turn control command is abstracted into an event b. The representation of the test sequence and the generation of the test sequence are facilitated.
In an embodiment, steps 104-106 may include the following:
step 104 first checks whether the first to-be-tested event in the to-be-covered sub-sequence is the same as each to-be-tested event in the current test sequence one by one, if so, the number of repeated events Nr is increased by one, and checks whether the second to-be-tested event in the to-be-covered sub-sequence is the same as the next to-be-tested event in the candidate test sequence. The operation is repeated until all the subsequences to be covered have been detected. Then checking whether the event repetition number Nr is consistent with the length of the sequence to be covered, if so, indicating that the sequence to be covered is covered by the current test sequence, and setting a coverage flag of the sequence to be covered to 1. If the sequences are inconsistent, the current test sequence is not capable of covering the sequence to be covered, and the coverage mark of the subsequence is kept to be 0.
When step 104 determines that the current test sequence does not cover all the sub-sequences to be covered, step 105 is executed: the candidate test sequences are constructed, and the input n test events to be tested are respectively and independently added to the back of the current test sequence, so that n candidate test sequences are constructed. Step 105 is to expand the test sequence by adding each event to be tested separately to the tail end of the current test sequence, thereby constructing n candidate test sequences.
Step 106 checks the number of the n candidate test sequences each covering the sub-sequences to be covered, and selects the candidate test sequence covering more sub-sequences to be covered to replace the current test sequence, updates the best coverage number, and jumps to step 104. The method of checking the number of the sequences to be covered by each candidate test sequence in step 106 is the same as the method of judging the sequences to be covered in step 104.
Taking the motion control instruction sequence test of the controller embedded software as an example. The controller receives instructions from an external communication protocol. In order to test whether the embedded software can still guarantee the reliability under various possible sequence combinations of the received instructions in all directions, test cases covering all event sequence combinations are designed. The receivable direction instructions include left turn (instruction a), right turn (instruction b), up (instruction c), down (instruction d), forward (instruction e), backward (instruction f). Due to the fact that coupling exists between the execution structures, after the controller receives the action command, the controller sequentially executes another movement after one movement, and faults can be caused. Thus, the event test sequence to be generated should cover the t-way sequential combination of instructions in each direction to test the system.
Taking the input event number as 6 and the sequential coverage force t as 3 as an example, the 3-way coverage test sequence obtained by adopting the test sequence generation method of the invention is as follows: left turn-right turn-up-down-forward-reverse-left turn-right turn-up-down-forward-left turn-reverse-right turn-up-down. Taking an input event as 6 and a sequential coverage degree t as 4 as an example, the 4-way coverage test sequence obtained by adopting the test sequence generation method of the invention is as follows: left turn-right turn-up-down-forward-backward-forward-left turn-up-down-forward-left turn-backward-right turn-up. By executing the commands in the sequence of test sequences above, system faults triggered by the sequence of events can be discovered, thereby mining more faults.
The test sequence generation method provided by the invention is comprehensively compared with the existing t-seq generation method and SCA reduction method.
Tables 2 and 3 show the 3-way sequence and 4-way overlay test sequence, respectively, of event numbers from 5 to 8 generated using the test sequence generation method of the present invention.
TABLE 2 3-way coverage test sequence generated by direct construction method
TABLE 3 4-way coverage test sequence generated by direct construction method
Event number | 4-way overlay test sequence |
5 | a-b-c-d-e-a-b-c-d-e-a-b-c-d-a-e-b |
6 | a-b-c-d-e-f-a-b-c-d-e-f-a-b-c-d-e-a-f-b-c |
7 | a-b-c-d-e-f-g-a-b-c-d-e-f-g-a-b-c-d-e-f-a-g-b-c-d |
8 | a-b-c-d-e-f-g-h-a-b-c-d-e-f-g-h-a-b-c-d-e-f-g-a-h-b-c-d-e |
Table 4 compares the number of events contained in the test sequence generated by the T-seq method, the number of events contained in the test sequence generated by the sequence coverage array SCA reduction method, and the number of events contained in the test sequence generated by the present invention.
Table 4 comparison of test sequence event counts satisfying 3-way coverage and 4-way coverage
FIG. 2 shows the trend of increasing number of events contained in the test sequences generated by each of the comparison methods as the number of test events increases. As can be seen from FIG. 2, the present invention greatly reduces the number of test sequence events based on the same event sequence coverage generated and satisfied compared with the T-seq method and the SCA reduction method, which can effectively reduce the test time and the test cost.
The invention greatly compresses the event number of the test sequence, especially the larger the number of the events to be tested, the larger the advantages of the invention compared with the SCA method and the reduction method.
A second aspect of the present invention provides a method of testing highly trusted software, the method comprising: generating a test sequence by adopting the test sequence generation method of the high-credibility software provided by the first aspect of the invention; and testing the high-reliability software by adopting the test sequence.
A third aspect of the present invention provides a test sequence generation system for highly trusted software, as shown in fig. 3, the system comprising:
the parameter determining module 301 is configured to determine a set of events to be tested and a sequential coverage of the events to be tested;
a to-be-covered subsequence determining module 302, configured to determine a to-be-covered subsequence set according to the to-be-tested event set and the sequential coverage power;
an initial test sequence determining module 303, configured to determine an initial test sequence, and use the initial test sequence as a current test sequence; the initial test sequence is a test sequence consisting of events to be tested in the event set to be tested;
a judging module 304, configured to judge whether the current test sequence completely covers each of the sub-sequences to be covered;
the candidate test sequence generating module 305 is configured to, when the current test sequence does not completely cover each of the sub-sequences to be covered, separately add each of the events to be tested in the set of events to be tested to the back of the current test sequence, so as to obtain a plurality of candidate test sequences;
a current test sequence updating module 306, configured to select, from the candidate test sequences, a candidate test sequence with the largest number of sequences to be covered to replace the current test sequence;
and the test sequence determining module 307 is configured to take the current test sequence that completely covers each of the to-be-covered subsequences as a test sequence for testing the high-reliability software when the current test sequence completely covers each of the to-be-covered subsequences.
In an embodiment, as a preferred implementation manner, the to-be-covered subsequence module 302 may include:
and the to-be-covered subsequence unit is used for taking t to-be-tested events from the to-be-tested event set to perform full permutation and combination to obtain the to-be-covered subsequence set, wherein t is the sequential coverage.
In an embodiment, as a preferred implementation manner, the initial test sequence determining module 303 may include:
and the initial test sequence determining unit is used for determining a sequence obtained by randomly arranging all the events to be tested in the event set to be tested as the initial test sequence.
In an embodiment, as a preferred implementation manner, the test sequence generating system of the high-trust software provided by the invention may further include:
the to-be-tested event abstract description module is used for carrying out unified abstract expression on to-be-tested events to obtain marks representing the to-be-tested events;
the event set to be tested building module is used for building the event set to be tested by adopting the marks of the events to be tested.
A fourth aspect of the invention provides a test system for highly trusted software, the system comprising: the test sequence generation system of the high-reliability software provided by the third aspect of the invention; the method comprises the following steps: the test system for testing the high-reliability software by using the test sequence generated by the test sequence generation system of the high-reliability software provided by the third aspect of the invention.
In the present specification, each embodiment is described in a progressive manner, and each embodiment is mainly described in a different point from other embodiments, and identical and similar parts between the embodiments are all enough to refer to each other.
The principles and embodiments of the present invention have been described herein with reference to specific examples, the description of which is intended only to assist in understanding the methods of the present invention and the core ideas thereof; also, it is within the scope of the present invention to be modified by those of ordinary skill in the art in light of the present teachings. In view of the foregoing, this description should not be construed as limiting the invention.
Claims (10)
1. A method for generating a test sequence of highly trusted software, comprising:
determining a sequence coverage of an event set to be tested and an event to be tested;
determining a sequence set to be covered according to the event set to be tested and the sequential coverage power;
determining an initial test sequence and taking the initial test sequence as a current test sequence; the initial test sequence is a test sequence consisting of events to be tested in the event set to be tested;
judging whether the current test sequence completely covers each sub-sequence to be covered or not, wherein the method specifically comprises the following steps: firstly checking whether a first event to be tested in a sequence to be covered is identical to each event to be tested in a current test sequence one by one, if so, adding one to the repeated number Nr of events, and checking whether a second event to be tested in the sequence to be covered is identical to the next event of the repeated event to be tested in a candidate test sequence, repeating the operation until the sequence to be covered is completely detected, then checking whether the repeated number Nr of events is consistent with the length of the sequence to be covered, if so, indicating that the sequence to be covered is covered by the current test sequence, setting a coverage mark of the sequence to be covered to 1, if not, indicating that the current test sequence cannot cover the sequence to be covered, and keeping the coverage mark of the subsequence to be 0;
if not, each event to be tested in the event set to be tested is respectively and independently added to the back of the current test sequence to obtain a plurality of candidate test sequences;
selecting the candidate test sequence with the largest number of the sequences to be covered from the candidate test sequences to replace the current test sequence, and jumping to the step of judging whether the current test sequence completely covers each sequence to be covered;
and if so, taking the current test sequence which completely covers each to-be-covered subsequence as a test sequence for testing the high-reliability software.
2. The method for generating a test sequence of high-confidence software according to claim 1, wherein the determining a set of sub-sequences to be covered according to the set of events to be tested and the sequential coverage degree specifically comprises:
and taking t events to be tested from the event set to be tested to perform full-permutation and combination to obtain a sequence set to be covered, wherein t is the sequential coverage.
3. The method for generating a test sequence of high-confidence software according to claim 1, wherein the determining an initial test sequence specifically comprises:
and determining a sequence obtained by randomly arranging all the events to be tested in the event set to be tested as the initial test sequence.
4. The method of generating a test sequence for highly-trusted software of claim 1, further comprising, prior to said determining the set of events to be tested:
carrying out unified abstract expression on the events to be tested to obtain marks representing the events to be tested;
and constructing the event set to be tested by adopting the marks of the events to be tested.
5. A method for testing highly trusted software, comprising:
generating a test sequence by using the test sequence generation method of the high-trust software according to any one of claims 1 to 4;
and testing the high-reliability software by adopting the test sequence.
6. A test sequence generation system for highly trusted software, comprising:
the parameter determining module is used for determining an event set to be tested and the sequential coverage of the events to be tested;
the to-be-covered subsequence determining module is used for determining a to-be-covered subsequence set according to the to-be-tested event set and the sequential coverage power;
the initial test sequence determining module is used for determining an initial test sequence and taking the initial test sequence as a current test sequence; the initial test sequence is a test sequence consisting of events to be tested in the event set to be tested;
the judging module is configured to judge whether the current test sequence completely covers each of the sequences to be covered, and specifically includes: firstly checking whether a first event to be tested in a sequence to be covered is identical to each event to be tested in a current test sequence one by one, if so, adding one to the repeated number Nr of events, and checking whether a second event to be tested in the sequence to be covered is identical to the next event of the repeated event to be tested in a candidate test sequence, repeating the operation until the sequence to be covered is completely detected, then checking whether the repeated number Nr of events is consistent with the length of the sequence to be covered, if so, indicating that the sequence to be covered is covered by the current test sequence, setting a coverage mark of the sequence to be covered to 1, if not, indicating that the current test sequence cannot cover the sequence to be covered, and keeping the coverage mark of the subsequence to be 0;
the candidate test sequence generation module is used for respectively and independently adding each event to be tested in the event set to be tested to the back of the current test sequence when the current test sequence does not completely cover each sub-sequence to be covered, so as to obtain a plurality of candidate test sequences;
the current test sequence updating module is used for selecting the candidate test sequence with the largest number of the sequences to be covered from the candidate test sequences to replace the current test sequence;
and the test sequence determining module is used for taking the current test sequence which completely covers each to-be-covered subsequence as the test sequence for testing the high-reliability software when the current test sequence completely covers each to-be-covered subsequence.
7. The system for generating a test sequence of high-confidence software according to claim 6, wherein the to-be-covered subsequence module specifically comprises:
and the to-be-covered subsequence unit is used for taking t to-be-tested events from the to-be-tested event set to perform full permutation and combination to obtain the to-be-covered subsequence set, wherein t is the sequential coverage.
8. The system for generating test sequences for highly trusted software of claim 6, wherein said initial test sequence determination module comprises:
and the initial test sequence determining unit is used for determining a sequence obtained by randomly arranging all the events to be tested in the event set to be tested as the initial test sequence.
9. The high-trust software test sequence generation system of claim 6, further comprising:
the to-be-tested event abstract description module is used for carrying out unified abstract expression on to-be-tested events to obtain marks representing the to-be-tested events;
the event set to be tested building module is used for building the event set to be tested by adopting the marks of the events to be tested.
10. A system for testing highly trusted software, comprising:
a test sequence generation system for highly trusted software as claimed in any one of claims 6 to 9; and a test system for testing the high-trust software by adopting the test sequence.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202010161800.7A CN111400176B (en) | 2020-03-10 | 2020-03-10 | Test sequence generation method and system, test method and system of high-credibility software |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202010161800.7A CN111400176B (en) | 2020-03-10 | 2020-03-10 | Test sequence generation method and system, test method and system of high-credibility software |
Publications (2)
Publication Number | Publication Date |
---|---|
CN111400176A CN111400176A (en) | 2020-07-10 |
CN111400176B true CN111400176B (en) | 2023-12-08 |
Family
ID=71436089
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN202010161800.7A Active CN111400176B (en) | 2020-03-10 | 2020-03-10 | Test sequence generation method and system, test method and system of high-credibility software |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN111400176B (en) |
Families Citing this family (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN111782544B (en) * | 2020-07-22 | 2022-09-06 | 中国人民解放军国防科技大学 | Software radio conformance testing method based on multi-population genetic algorithm |
CN112951351B (en) * | 2021-03-31 | 2023-08-22 | 南京信息工程大学 | Drug clinical trial design method based on row limiting coverage array |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101916225A (en) * | 2010-09-02 | 2010-12-15 | 于秀山 | Graphical user interface software function coverage testing method |
CN106095692A (en) * | 2016-08-12 | 2016-11-09 | 哈尔滨工业大学 | The one-parameter sequence of events test data generating method of embedded software |
CN108415841A (en) * | 2018-03-19 | 2018-08-17 | 南京邮电大学 | A kind of combined test use-case prioritization method based on covering dynamics increment |
Family Cites Families (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7293257B2 (en) * | 2003-10-14 | 2007-11-06 | Microsoft Corporation | Method and system for efficient testing of sequences of computer-related operations |
US20130111267A1 (en) * | 2011-11-01 | 2013-05-02 | International Business Machines Corporation | Optimizing regression testing based on code coverage analysis |
-
2020
- 2020-03-10 CN CN202010161800.7A patent/CN111400176B/en active Active
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101916225A (en) * | 2010-09-02 | 2010-12-15 | 于秀山 | Graphical user interface software function coverage testing method |
CN106095692A (en) * | 2016-08-12 | 2016-11-09 | 哈尔滨工业大学 | The one-parameter sequence of events test data generating method of embedded software |
CN108415841A (en) * | 2018-03-19 | 2018-08-17 | 南京邮电大学 | A kind of combined test use-case prioritization method based on covering dynamics increment |
Non-Patent Citations (3)
Title |
---|
孔庆彦 ; 伦立军 ; 刘永纯 ; 宋益波 ; .一种软件体系结构测试序列生成方法.小型微型计算机系统.2009,(04),全文. * |
王子元 ; 徐宝文 ; 聂长海 ; .组合测试用例生成技术.计算机科学与探索.2008,(06),全文. * |
陈翔 ; 顾庆 ; 王新平 ; 陈道蓄 ; .组合测试研究进展.计算机科学.2010,(03),全文. * |
Also Published As
Publication number | Publication date |
---|---|
CN111400176A (en) | 2020-07-10 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN111400176B (en) | Test sequence generation method and system, test method and system of high-credibility software | |
US9654490B2 (en) | System and method for fuzzing network application program | |
CN102855184A (en) | Android automatic test cross application device and method | |
JPH09145800A (en) | Test pattern generation system | |
CN106708725A (en) | Test sequence dynamic management method combining test with diagnosis | |
US20060195732A1 (en) | Method and system for executing test cases for a device under verification | |
US8533544B2 (en) | System for tree sequence testing of a device and method for tree sequence testing of a device in a test framework architecture | |
Yu et al. | Efficient algorithms for t-way test sequence generation | |
CN110633221B (en) | Fuzzy test automation vulnerability positioning method | |
CN104008056A (en) | Software testing method and device | |
CN110674042B (en) | Concurrency performance testing method and device | |
Piparia et al. | Combinatorial testing of context aware android applications | |
CN108205490B (en) | Software watchdog test method and device | |
KR101989311B1 (en) | Apparatus and method for generating test scripts for testing embedded system | |
CN114492266A (en) | Chip verification method and device, electronic equipment and storage medium | |
CN112395207A (en) | Efficient verification method, device and storage medium for complex state machine | |
KR20120000320A (en) | Method generating test case for program error check | |
Kuhn et al. | Ordered t-way combinations for testing state-based systems | |
CN111031089A (en) | Test method for web conference control client and computer equipment | |
KR102251703B1 (en) | Simulation system for diagnosing cables and Method for controlling the same | |
CN111983998B (en) | Automatic diagnosis test case generation system and method | |
JPH06324904A (en) | Correcting method for testing instruction | |
CN107562566A (en) | A kind of processing method and processing device by correcting and eleting codes to data | |
Kyaw et al. | Model Based Automatic Optimal Test Path Generation via Search Optimization Techniques: A Critical Review | |
Harel et al. | Loops |
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 |