CN111190819A - State control method for airborne software test project - Google Patents
State control method for airborne software test project Download PDFInfo
- Publication number
- CN111190819A CN111190819A CN201911359037.2A CN201911359037A CN111190819A CN 111190819 A CN111190819 A CN 111190819A CN 201911359037 A CN201911359037 A CN 201911359037A CN 111190819 A CN111190819 A CN 111190819A
- Authority
- CN
- China
- Prior art keywords
- state
- test
- library
- project
- software
- 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
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
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)
- Stored Programmes (AREA)
- Debugging And Monitoring (AREA)
Abstract
The embodiment of the invention discloses a state control method for an airborne software test project, which comprises the following steps: establishing a state library of the test items according to a preset basic library of the test items, and determining the state of key points of the software test items in the test process; determining the corresponding relation between the test item and the state according to the state library of the test item; establishing a problem library of the test items according to the base library and the unique identification of the test items in the base library, extracting problem information of the test items in the base library, and identifying problem states; zeroing the problems which are not zeroed in the problem library, and mapping the zeroing state into a state library; and carrying out item ending processing on the key point state in the state library according to the item ending condition of the test item. The embodiment of the invention solves the problems of unclear change test state and problem state of multi-version software, uncontrolled multi-round software test process of software test projects, zero return time of project leaving problems, uncertain tracing and the like.
Description
Technical Field
The present application relates to, but not limited to, the field of onboard software testing technologies, and in particular, to a method for controlling a state of an onboard software test project.
Background
With the development of modern aircraft, the requirements for aircraft function, performance and safety have changed and increased, and even on the same type of aircraft, the systems may exhibit a number of different states.
During development of aircraft systems, changes in the requirements of the top layer may result in changes in the state of system software, changes in the state of system hardware, and even changes in the state of other systems linked thereto, and so forth. And the on-board software is used as a key component of an aircraft system, and the change of the state of the on-board software directly influences the function, the performance and the safety of the aircraft.
The airborne software test is an important link in the software life cycle, is a key step of software quality assurance, and is an important guarantee before the software is put into operation. However, with the difference of the airplane rack times of the same airplane type and the difference of the system function requirements, a plurality of software version states are generated, and when the functions are overlapped, the problem of the project left by different versions occurs due to software design factors, software testing environment factors and the like. Due to high requirements on the modern work output, urgent project nodes and fast change of user requirements, software test project members are forced to put most of time into software test technology and test work, and are oblivious to the test project states of all versions of airborne software, problem tracking of legacy problems, management of zeroing states and the like, so that the projects are not traceable, can be checked without data, are disordered in state, and can be managed disorderly and not tracked to zero in serious cases, thereby affecting the software reliability and the airplane safety.
Disclosure of Invention
In order to solve the technical problems, embodiments of the present invention provide a state control method for an airborne software test project, so as to improve the state management efficiency of the airborne software test project, and solve the problems of unclear change test state and problem state of multi-version software, uncontrolled multi-software test process of the software test project, uncertain zeroing time and traceability of project leaving problems, and the like.
The embodiment of the invention provides a state control method for an airborne software test project, which comprises the following steps:
establishing a state library of the test items according to a preset basic library of the test items, and determining the state of key points of the software test items in the test process;
determining the corresponding relation between the test item and the state according to the state library of the test item;
establishing a problem library of the test items according to the unique identifiers of the basic library and the test items in the basic library, extracting problem information of the test items in the basic library, and identifying problem states;
zeroing the problems which are not zeroed in the problem library, and mapping the zeroing state into the state library;
and carrying out item ending processing on the key point states in the state library according to item ending conditions of the test items.
Optionally, in the method for controlling the state of the onboard software test item, the method further includes:
establishing a basic library of the test items, and determining the unique identification of the test items according to the information in the basic library, wherein the unique identification of the test items comprises: model name, system name, subsystem name, software name, and version number.
Alternatively, in the state control method of the on-board software test item as described above,
the key point states include: configuring a management state, a quality assurance state, a multi-turn regression test state, a test document state, a project problem state and a project remaining problem zeroing state;
optionally, in the method for controlling the state of the onboard software test item, the method further includes:
and establishing a mapping relation between the key point state in the state library and the state in the basic library.
Optionally, in the method for controlling the state of the onboard software test item, the question information of the test item includes the question type, the question level and the question content of the test item, and the question state includes return-to-zero and non-return-to-zero.
Optionally, in the method for controlling the state of the onboard software test project, the zeroing the non-zeroed questions in the question bank includes:
and defining the problem with the status not returning to zero in the problem library as a project remaining problem, and carrying out status control on the project remaining problem.
Optionally, in the method for controlling the state of the onboard software test project, the performing state control on the project leave-behind problem includes:
extracting problem information of the project remaining problems;
according to the extracted problem information and the content of the airborne software, carrying out zero-setting processing on the project remaining problems, wherein the zero-setting processing comprises modifying the content of the airborne software according to the extracted problem information;
testing and verifying the onboard software subjected to the zeroing treatment according to the extracted problem information and the contents of the onboard software subjected to the zeroing treatment;
and establishing a return-to-zero tracing relation according to a test verification result, and changing the state of the project legacy problem to return to zero.
Optionally, in the method for controlling the state of the onboard software test item, performing an item ending process on the key point state in the state library according to an item ending condition of the test item includes:
extracting a decisive state in the test process from the state library, carrying out logic operation on the decisive state, and judging whether the test item meets an item ending condition according to an operation result;
when the test item does not accord with the end condition, searching a state influencing the end through a user interface, and processing the state to finish the state;
and when the test item meets an ending condition, determining that the test item finishes ending.
The state control method of the airborne software test project provided by the embodiment of the invention solves the problems of unclear change test state and problem state of multi-version software, uncontrolled multi-software test process of the software test project, uncertain zeroing time and traceability of the project legacy problem and the like, ensures that the state of each software test project is clear, the project problem processing result is clear and the traceability of the project legacy problem is strong, directly improves the state management efficiency of the airborne software test project and indirectly improves the reliability of software, aiming at the software test project with more system/software requirement changes, more software states, and longer project problem zeroing period. The scheme of the embodiment of the invention has the following advantages:
a) the state of the onboard software test project and incomplete process nodes can be accurately checked in real time;
b) the specific information and the zeroing state of the problem can be checked in the problem database according to the uniqueness of the airborne software;
c) carrying out problem tracking on the left problems of the states of all versions of the airborne software test project, and tracing the state of the carrier after the zero return;
d) a user interface is defined, and the state information of the item concerned by the user can be checked in a concise and clear mode;
e) the workload of testing personnel is reduced, and the testing efficiency and accuracy are increased;
f) the method has strong universality, and can be applied to management methods with uncertain user requirements and many finished product states in other fields;
g) manpower resources are reduced, and the state management efficiency and the correctness of the airborne software test project are improved.
Drawings
The accompanying drawings are included to provide a further understanding of the invention and are incorporated in and constitute a part of this specification, illustrate embodiments of the invention and together with the example serve to explain the principles of the invention and not to limit the invention.
FIG. 1 is a flowchart of a method for controlling the status of an airborne software test project according to an embodiment of the present invention;
FIG. 2 is a schematic diagram of a method for controlling the status of an airborne software test item according to an embodiment of the present invention;
FIG. 3 is a diagram illustrating a mapping relationship between a state library and a base library according to an embodiment of the present invention;
FIG. 4 is a flow chart of state control for project leave issues in the practice of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, embodiments of the present invention will be described in detail below with reference to the accompanying drawings. It should be noted that the embodiments and features of the embodiments in the present application may be arbitrarily combined with each other without conflict.
The following specific embodiments of the present invention may be combined, and the same or similar concepts or processes may not be described in detail in some embodiments.
Fig. 1 is a flowchart of a method for controlling a status of an airborne software test item according to an embodiment of the present invention, and fig. 2 is a schematic diagram of a method for controlling a status of an airborne software test item according to an embodiment of the present invention. The state control method for the onboard software test item provided by the embodiment can comprise the following steps:
s110, establishing a state library of the test item according to a preset basic library of the test item, and determining the state of a key point of the software test item in the test process;
s120, determining the corresponding relation between the test item and the state according to the state library of the test item;
s130, establishing a problem library of the test items according to the base library and the unique identifiers of the test items in the base library, extracting problem information of the test items in the base library, and identifying problem states;
s140, zeroing the problems which are not zeroed in the problem library, and mapping the zeroing state into a state library;
and S150, performing item ending processing on the key point states in the state library according to item ending conditions of the test items.
Optionally, before S110, the method provided in the embodiment of the present invention may further include:
s100, establishing a basic library of the test items, and determining the unique identification of the test items according to the information in the basic library, wherein the unique identification of the test items comprises: model name, system name, subsystem name, software name, and version number.
Optionally, the key point state in the embodiment of the present invention may include: configuring a management state, a quality assurance state, a multi-turn regression test state, a test document state, a project problem state and a project remaining problem zeroing state;
correspondingly, the method provided by the embodiment of the invention can further comprise the following steps:
and establishing a mapping relation between the key point state in the state library and the state in the basic library. Fig. 3 is a schematic diagram of a mapping relationship between a state library and a base library in the embodiment of the present invention.
Optionally, the question information of the test item in the embodiment of the present invention includes a question type, a question level, and a question content of the test item, and the question status includes a return-to-zero status and a non-return-to-zero status.
Optionally, an implementation manner of performing zeroing processing on the non-zeroed questions in the question bank in S140 in the embodiment of the present invention may include:
and defining the problem with the status not returning to zero in the problem library as a project remaining problem, and performing status control on the project remaining problem.
FIG. 4 is a flow chart of state control for project leave issues in the practice of the present invention. In practical applications, as shown in fig. 4, a specific embodiment of performing state control on the project leave problem may include:
s1, extracting problem information of the project remaining problems;
s2, according to the extracted problem information and the content of the airborne software, carrying out zero-setting processing on the project remaining problems, wherein the zero-setting processing comprises the step of modifying the content of the airborne software according to the extracted problem information;
s3, testing and verifying the onboard software subjected to the zeroing treatment according to the extracted problem information and the contents of the onboard software subjected to the zeroing treatment;
and S4, establishing a zeroing traceability relation according to the test verification result, and changing the state of the project legacy problem to be zeroed.
Optionally, an implementation manner of S150 in the embodiment of the present invention may include:
s1, extracting the decisive state in the test process from the state library, carrying out logic operation on the decisive state, and judging whether the test item meets the result condition according to the operation result; the logical operation may be a logical and, that is, all states are completion conditions and are considered to be completed;
s2, when the test item is not in accordance with the end condition, searching the state affecting the end item through the user interface, and processing the state to complete the state;
and S3, when the test item meets the end condition, determining that the test item finishes the end.
The embodiment of the invention provides a state management method of an airborne software test project for the first time, aiming at the software test project which has the advantages of more system/software requirement changes, more software states, incapability of timely processing project problems and long project leave-behind problem zeroing period, solving the problems of unclear change test state and problem state of multi-version software, uncontrolled multi-software test process of the software test project, zeroing time of the project leave-behind problem, uncertain traceability and the like, ensuring that the state of each software test project is clear, the processing result of the project problem is clear and the traceability of the project leave-behind problem is strong, directly improving the state management efficiency of the airborne software test project and indirectly improving the reliability of software.
The state management method of the airborne software test project has the following characteristics:
a) a management method based on more system/software requirements and more software states;
b) the whole management process is optimized in a flow mode through the uniqueness of the project, and the situation that the project state is judged by repeatedly referring to relevant data is avoided;
c) establishing information association concerned by a manager through the uniqueness of the project, and displaying the state information of the project through an interface;
d) effectively managing the problem state of the project and the zero returning situation of the remaining problems;
e) correctly tracing the carrier with the project leaving problem reset to zero;
f) the method has strong universality, and can be applied to management methods with uncertain user requirements and many finished product states in other fields;
g) manpower resources are reduced, and the state management efficiency and the correctness of the airborne software test project are improved.
The following describes an implementation of a method for controlling the state of an onboard software test item according to an embodiment of the present invention with a specific implementation example. A schematic diagram of a status management method of an onboard software test project is shown in fig. 2, and the specific implementation manner is as follows:
step 1, establishing a test project base library aiming at a multi-state airborne software test project, wherein the information of the project base library comprises a model name, a system name, a subsystem name, a software name, a version, a tester, a quality assurance worker, a software level, a management state classification and the like; determining a unique identifier of a software test item according to the constituent elements in the basic library, namely the uniqueness of the test item, and establishing a direct relation with other elements through the identifier of each test item, so that a user can conveniently and intuitively check related information of a certain software test item in real time on a user interface; if the model name, the system name, the subsystem name, the software name and the version are determined as the unique identification of the airborne software testing project in the airborne software testing project;
step 2, establishing a state requirement library of the airborne software test project, and determining key points in the process of the airborne software test project, such as a configuration management state, a quality assurance state, a multi-turn regression test state, a test document state, a project problem state, a project remaining problem zeroing state and the like; the state data source is taken from a basic library of the test project, and a mapping relation is established between a key name in a state requirement library and a management state in a project basic library, so that data entry of a manager and data viewing of a user are facilitated; FIG. 3 is a mapping relationship diagram of a status requirement library and a project base library;
step 3, establishing a project problem library according to the unique identification of the software test project, extracting information such as the type, the level, the content and the like of the project problem from the project basic library, and identifying the problem state: return-to-zero problems, non-return-to-zero problems; defining the problem with the status not returning to zero as a project remaining problem, and performing status management on the project remaining problem;
step 4, the software developer takes the information of the type, level, content and the like of the project remaining problems as the input of the zeroing, correspondingly changes the source program/document and zeroes the problems; the software testing party verifies and confirms whether the problem returns to zero, establishes a return-to-zero tracking relation in a corresponding project legacy problem database, and traces back a return-to-zero source to facilitate future reference; FIG. 4 is a flow diagram of project leave-behind problem and zeroing tracking;
step 5, according to the management requirement of the on-board software test project conclusion, extracting decisive elements from the project state requirement library, carrying out logic operation on the decisive elements, and judging whether the software test project is completed or ended to reach an expected state; if not, a user/manager can check the factors influencing the result through the user interface, so that the software test item is in a controllable range, and the software test item can be finished according to the quality guarantee of the nodes, thereby directly improving the state management efficiency of the airborne software test item and indirectly improving the reliability of the software.
Although the embodiments of the present invention have been described above, the above description is only for the convenience of understanding the present invention, and is not intended to limit the present invention. It will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the invention as defined by the appended claims.
Claims (8)
1. A state control method for an airborne software test item is characterized by comprising the following steps:
establishing a state library of the test items according to a preset basic library of the test items, and determining the state of key points of the software test items in the test process;
determining the corresponding relation between the test item and the state according to the state library of the test item;
establishing a problem library of the test items according to the unique identifiers of the basic library and the test items in the basic library, extracting problem information of the test items in the basic library, and identifying problem states;
zeroing the problems which are not zeroed in the problem library, and mapping the zeroing state into the state library;
and carrying out item ending processing on the key point states in the state library according to item ending conditions of the test items.
2. The method for controlling the status of an onboard software test project according to claim 1, further comprising:
establishing a basic library of the test items, and determining the unique identification of the test items according to the information in the basic library, wherein the unique identification of the test items comprises: model name, system name, subsystem name, software name, and version number.
3. The method for controlling the status of an onboard software test project according to claim 1,
the key point states include: configuring a management state, a quality assurance state, a multi-turn regression test state, a test document state, a project problem state and a project leave-behind problem zeroing state.
4. The method for controlling the status of an onboard software test project according to claim 3, further comprising:
and establishing a mapping relation between the key point state in the state library and the state in the basic library.
5. The method of claim 1, wherein the problem information of the test item comprises the type, level and content of the problem of the test item, and the problem status comprises zeroed and non-zeroed.
6. The method for controlling the status of an onboard software test project according to claim 5, wherein the zeroing of the non-zeroed questions in the question bank comprises:
and defining the problem with the status not returning to zero in the problem library as a project remaining problem, and carrying out status control on the project remaining problem.
7. The method for controlling the state of the on-board software test project according to claim 6, wherein the controlling the state of the project leave-behind problem comprises:
extracting problem information of the project remaining problems;
according to the extracted problem information and the content of the airborne software, carrying out zero-setting processing on the project remaining problems, wherein the zero-setting processing comprises modifying the content of the airborne software according to the extracted problem information;
testing and verifying the onboard software subjected to the zeroing treatment according to the extracted problem information and the contents of the onboard software subjected to the zeroing treatment;
and establishing a return-to-zero tracing relation according to a test verification result, and changing the state of the project legacy problem to return to zero.
8. The method for controlling the state of the onboard software test item according to claim 1, wherein the step of performing an item processing on the key point states in the state library according to an item condition of the test item comprises the following steps:
extracting a decisive state in the test process from the state library, carrying out logic operation on the decisive state, and judging whether the test item meets an item ending condition according to an operation result;
when the test item does not accord with the end condition, searching a state influencing the end through a user interface, and processing the state to finish the state;
and when the test item meets an ending condition, determining that the test item finishes ending.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911359037.2A CN111190819B (en) | 2019-12-25 | 2019-12-25 | State control method for airborne software test project |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911359037.2A CN111190819B (en) | 2019-12-25 | 2019-12-25 | State control method for airborne software test project |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111190819A true CN111190819A (en) | 2020-05-22 |
| CN111190819B CN111190819B (en) | 2023-05-23 |
Family
ID=70707595
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911359037.2A Active CN111190819B (en) | 2019-12-25 | 2019-12-25 | State control method for airborne software test project |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111190819B (en) |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2009252167A (en) * | 2008-04-10 | 2009-10-29 | Ricoh Co Ltd | Test item creation device, test item creation system, test item creation method and test item creation program |
| CN103257918A (en) * | 2012-02-16 | 2013-08-21 | 广州博纳信息技术有限公司 | Project test procedure management method based on software testing and evaluation platform |
| CN103530232A (en) * | 2013-10-24 | 2014-01-22 | 北京经纬恒润科技有限公司 | Method and device for building software testing management framework |
| CN106709656A (en) * | 2016-12-28 | 2017-05-24 | 中国航空工业集团公司西安飞机设计研究所 | System architecture-based avionics system technology state control method |
| CN108573365A (en) * | 2017-03-07 | 2018-09-25 | 北京空间技术研制试验中心 | The service-oriented and flow state digitized management method of integration test |
| CN109657224A (en) * | 2019-01-04 | 2019-04-19 | 北京空间技术研制试验中心 | Spacecraft-testing based on Data Analysis Platform reports automatic generation method |
| US10318412B1 (en) * | 2018-06-29 | 2019-06-11 | The Travelers Indemnity Company | Systems, methods, and apparatus for dynamic software generation and testing |
| CN109889585A (en) * | 2019-02-01 | 2019-06-14 | 中电科仪器仪表有限公司 | A kind of the operating status remote supervision system and method for electronic testing instrument |
| US10387297B1 (en) * | 2016-06-15 | 2019-08-20 | Amdocs Development Limited | System, method, and computer program for end-to-end test management of a software testing project |
-
2019
- 2019-12-25 CN CN201911359037.2A patent/CN111190819B/en active Active
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2009252167A (en) * | 2008-04-10 | 2009-10-29 | Ricoh Co Ltd | Test item creation device, test item creation system, test item creation method and test item creation program |
| CN103257918A (en) * | 2012-02-16 | 2013-08-21 | 广州博纳信息技术有限公司 | Project test procedure management method based on software testing and evaluation platform |
| CN103530232A (en) * | 2013-10-24 | 2014-01-22 | 北京经纬恒润科技有限公司 | Method and device for building software testing management framework |
| US10387297B1 (en) * | 2016-06-15 | 2019-08-20 | Amdocs Development Limited | System, method, and computer program for end-to-end test management of a software testing project |
| CN106709656A (en) * | 2016-12-28 | 2017-05-24 | 中国航空工业集团公司西安飞机设计研究所 | System architecture-based avionics system technology state control method |
| CN108573365A (en) * | 2017-03-07 | 2018-09-25 | 北京空间技术研制试验中心 | The service-oriented and flow state digitized management method of integration test |
| US10318412B1 (en) * | 2018-06-29 | 2019-06-11 | The Travelers Indemnity Company | Systems, methods, and apparatus for dynamic software generation and testing |
| CN109657224A (en) * | 2019-01-04 | 2019-04-19 | 北京空间技术研制试验中心 | Spacecraft-testing based on Data Analysis Platform reports automatic generation method |
| CN109889585A (en) * | 2019-02-01 | 2019-06-14 | 中电科仪器仪表有限公司 | A kind of the operating status remote supervision system and method for electronic testing instrument |
Non-Patent Citations (5)
| Title |
|---|
| 刘文红等: "基于CMMI的软件测试项目过程管理", 《飞行器测控学报》 * |
| 吕林涛等: "基于CPN的多步骤攻击警报关联方法", 《计算机工程》 * |
| 张威等: "航天器数字化综合测试状态管理系统设计", 《航天器工程》 * |
| 柳永坡等: "大型交互式领域应用软件白盒测试的组织和实施", 《计算机应用研究》 * |
| 胡博等: "测试状态控制系统在航天领域中的应用与研究", 《中国设备工程》 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111190819B (en) | 2023-05-23 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108614770B (en) | Automatic test assertion method, device, storage medium and equipment | |
| CN110287052B (en) | Root cause task determination method and device for abnormal task | |
| CN111240994B (en) | Vulnerability processing method and device, electronic equipment and readable storage medium | |
| US8151248B1 (en) | Method and system for software defect management | |
| CN109344056B (en) | Test method and test device | |
| US20120233598A1 (en) | Completing functional testing | |
| US20120290527A1 (en) | Data extraction and testing method and system | |
| CN111563041B (en) | Test case on-demand accurate execution method | |
| US20150154097A1 (en) | System and method for automated testing | |
| KR102268053B1 (en) | Intelligent safety fault diagnostic system of robotic process automation | |
| CN110188036A (en) | A kind of method for testing software and device | |
| Tierno et al. | Open issues for the automotive software testing | |
| US20160314061A1 (en) | Software Defect Detection Identifying Location of Diverging Paths | |
| CN114116801A (en) | Data list checking method and device | |
| KR102418796B1 (en) | FMEA failure mode recommend system | |
| KR102399597B1 (en) | Intelligent safety analysis technology using AI | |
| CN116401113B (en) | Environment verification method, device and medium for heterogeneous many-core architecture acceleration card | |
| US20120124428A1 (en) | Method and system for testing software on programmable devices | |
| CN112506802A (en) | Test data management method and system | |
| CN111198920B (en) | Method and device for determining comparison table snapshot based on database synchronization | |
| CN111190819A (en) | State control method for airborne software test project | |
| CN116795425A (en) | Chip front-end development system and method based on git | |
| CN114329116B (en) | Artificial intelligence-based intelligent park resource matching degree analysis method and system | |
| CN110618943B (en) | Security service test method and device, electronic equipment and readable storage medium | |
| Pathania et al. | Role of test case prioritization based on regression testing using clustering |
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 |