CN111258915A - Method for carrying out automatic unit test aiming at PLC program - Google Patents
Method for carrying out automatic unit test aiming at PLC program Download PDFInfo
- Publication number
- CN111258915A CN111258915A CN202010124563.7A CN202010124563A CN111258915A CN 111258915 A CN111258915 A CN 111258915A CN 202010124563 A CN202010124563 A CN 202010124563A CN 111258915 A CN111258915 A CN 111258915A
- Authority
- CN
- China
- Prior art keywords
- test
- plc
- program
- ltest
- library
- 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
- G06F11/3684—Test management for test design, e.g. generating new test cases
-
- 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
- Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
- Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
- Y02P90/02—Total factory control, e.g. smart factories, flexible manufacturing systems [FMS] or integrated manufacturing systems [IMS]
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)
- Programmable Controllers (AREA)
Abstract
The invention discloses a method for carrying out automatic unit test aiming at a PLC program, which comprises the following steps: 1) inputting a source code through a C # program, and compiling a functional block capable of automatically testing PLC software; 2) compiling the program source code to generate a common intermediate language file; 3) generating a solid library file from the public intermediate language file through a solid library generator in the PLC programming software, and constructing a solid library; 4) adding the built firmware library in the PLC programming software; 5) building a test framework by using functional blocks in a firmware library through PLC programming software; 6) compiling the PLC program according to the constructed test framework, and generating a PLC engineering mirror image; 7) and installing the generated engineering mirror image in an operation platform of the PLC program, and starting operation. According to the invention, the automatic test framework is introduced into the PLC programming, so that the test group or the test case to be executed can be flexibly adjusted according to the requirement, the writing of the test program is simplified, and the test efficiency is improved.
Description
Technical Field
The invention relates to the technical field of software testing, in particular to a method for carrying out automatic unit testing aiming at a PLC program.
Background
PLC programming is an electronic system of digital arithmetic operations designed specifically for application in an industrial environment. It uses programmable memory to store the instructions for executing logical operation, sequence control, timing, counting and arithmetic operation, etc. and controls various types of machinery or production process by digital and analog input and output. The programmable controller and its related equipment are designed according to the principle of easy making industrial control system form a whole body and easy to expand its function.
With the rapid development of microprocessors, computers and digital communication technologies, computer control has expanded into almost all industrial fields. Modern society requires that the manufacturing industry respond rapidly to market demands to produce small-lot, multi-variety, multi-specification, low-cost, and high-quality products, and in order to meet this requirement, the control systems of production equipment and automated production lines must have extremely high reliability and flexibility, and PLC programming is emerging in compliance with this requirement, which is a general industrial control device based on a microprocessor. A
Unit testing refers to checking and verifying the smallest testable unit in software. For the meaning of the unit in the unit test, generally, the specific meaning is determined according to the actual situation, for example, the unit in the C language refers to a function, the unit in the Java refers to a class, and the graphical software may refer to a window or a menu. In general, the unit is the minimum tested functional module specified by human. Unit testing is the lowest level of testing activity to be performed during software development, and individual units of software will be tested in isolation from other parts of the program.
At present, the technical means limited to testing the automatic control PLC software is few, and commercial software cannot directly test the software. Generally, an actual software and hardware operating environment is set up, so that the test cost is high, and the test coverage rate cannot be guaranteed. The PLC software testing technology research is developed, the PLC software is isolated from the real environment, independent software testing and verification are carried out under the condition that hardware is not connected, the software and hardware faults are separated, the testing cost of the software at present is reduced, the testing efficiency and the testing quality are improved, and the method has important significance.
Disclosure of Invention
The invention aims to provide a method for carrying out automatic unit test aiming at a PLC program, which has the advantages of higher test efficiency, simpler test and good flexibility and is suitable for extension.
The invention is realized by the following technical scheme: a method of automated unit testing for a PLC program, comprising the steps of:
(1) inputting a source code through a C # program, and compiling a functional block capable of automatically testing PLC software;
(2) compiling the program source code to generate a common intermediate language file;
(3) generating a solid library file from the public intermediate language file through a solid library generator in the PLC programming software, and constructing a solid library;
(4) adding the built firmware library in the PLC programming software;
(5) building a test framework by using functional blocks in a firmware library through PLC programming software;
(6) compiling the PLC program according to the constructed test framework, and generating a PLC engineering mirror image;
(7) and installing the generated engineering mirror image in an operation platform of a PLC program, starting operation, filling codes to be tested in the frame, and performing cycle test.
Unit testing is also called module testing, and is a test work for performing correctness checking on a program module (a minimum unit of software design). The traditional PLC program has low testing efficiency or needs relatively complex PLC programming, has low flexibility and is not easy to expand, the automatic unit test is introduced into the PLC program for compiling, the development efficiency of PLC software can be improved, and the technical scheme provides the method for introducing the automatic unit test into the PLC program.
Since PLC programming is a programming language designed specifically for industrial environment applications, PLC programs operate in a "sequential scan, continuous loop" manner.
Function (FU): the function is a pou (programorganization units) with a number of input parameters and exactly one output parameter. Invoking a function with the same value always returns the same result. The return value may be a simple data type. Within one function, additional functions may be called, but function blocks or procedures cannot be called, not allowing recursive calls.
Function Block (FB): function blocks are pous (programorganization units) with a number of input/output parameters and internal memory locations, the return value of a function block depends on the value of its internal memory location, and exceptional function blocks or functions can be called within a function block, but no program can be called, and no recursive calls are allowed.
The method specifically comprises the steps of compiling functional blocks of an automatic unit test by using a C # program, then generating a solid library file for the functional blocks, loading the solid library through PLC programming software, constructing test codes according to the functional blocks in the solid library, finally generating an engineering mirror image capable of running on a PLC program target platform, then loading the engineering mirror image on the target platform, and running the test program through the target platform to realize the automatic unit test of the PLC software.
In order to better implement the present invention, further, the program written by inputting the source code through the C # program in step (1) includes:
the LTest _ SetUp declares a public execution part of the test group before the test case is started to be executed;
the LTest _ SetUpDone and the LTest _ SetUp are used in pair;
the test _ Teardown states that the test group performs the public execution part after the test case is executed;
the LTest _ TearDown Done and the LTest _ TearDown are used in pair;
LTest _ TestCaseStart, declare the test case;
the LTest _ TestCaseEnd is used in pair with the LTest _ TestCaseStart;
the LTest _ Result is used for obtaining the execution Result of the current test;
LTest _ Config, configuring test cases that need to be executed or not.
The test _ SetUp and the test _ TearDown are common execution parts added before and after the test case, and can be understood as a start character and an end character of the test group to identify the test group. All test cases are grouped according to the same start and end, so that repeated code copying is avoided, the groups are called test groups, and certainly, the grouping can be further performed according to the tested functions.
And executing each Test case according to the sequence of SetUp- > Test- > Teardown to Test.
During operation, the SetUp and the TearDown divide the PLC program into a plurality of test groups, and the Start and the End divide the program in the test groups into a plurality of test cases.
All the function blocks are managed by an internal state machine in a unified way, each function block (except Result and Config) corresponds to an internal state, namely, Done and End, and is used for recording the state, representing that the execution of the code segment is finished, whether a code between SetUp and SetUpDone is controlled by SetUp is executed, whether a code between TearDown and TearDown is controlled by TearDown is executed, and whether a code between TestCaseStart and TestCaseEnd is executed is controlled by TestCaseStart.
In order to better implement the present invention, further, the firmware library file generated in step (3) includes a function block name, an input variable, an output variable, and an input/output variable.
In order to better implement the invention, further, the PLC programming software is Multiprog. The MultiProg is a programming system based on IEC standard and traditional PLC standard, and can edit, compile and debug PLC engineering.
In order to better implement the present invention, in the step (6), the process of compiling the PLC program according to the constructed test code is to convert the common intermediate language file into the machine code of the ProConOS platform by using a method of converting the common intermediate language file into the machine code. ProconOS is a high performance PLC engine designed specifically for embedded and PC-based control applications. ProconOS can work in conjunction with mainstream embedded systems (e.g., Vxworks, QNX, OS 9) and the like, providing deterministic control performance down to 1ms run-time.
In order to better implement the present invention, further, the running platform of the PLC program in step (7) is a ProConOS platform.
Compared with the prior art, the invention has the following advantages and beneficial effects:
(1) according to the invention, the automatic test framework is introduced into the PLC programming, so that a test group or a test case to be executed can be flexibly adjusted according to the requirement, the writing of a test program of the PLC software is simplified, and the test efficiency of the PLC software is greatly improved;
(2) according to the invention, the program test of the PLC software is realized by using the C # program programming, so that the written functional block can meet the standard of 61131-3 without additionally setting parameters;
(3) the invention has simple technical principle and simple implementation process, is beneficial to the program test of PLC software and is suitable for wide popularization and application.
Drawings
Other features, objects and advantages of the invention will become more apparent upon reading of the detailed description of non-limiting embodiments with reference to the following drawings:
FIG. 1 is a basic flow diagram of an implementation of the present invention;
FIG. 2 is a timing diagram of the execution of the test case according to the present invention.
Detailed Description
The present invention will be described in further detail with reference to the following examples for the purpose of making clear the objects, process conditions and advantages of the present invention, but the embodiments of the present invention are not limited thereto, and various substitutions and modifications can be made according to the common technical knowledge and the conventional means in the art without departing from the technical idea of the present invention described above, and the specific examples described herein are only for explaining the present invention and are not intended to limit the present invention.
Example 1:
the embodiment provides a method for performing an automation unit test for a PLC program, and a specific flow is shown in fig. 1, and the method includes the following steps:
(1) inputting a source code through a C # program, and compiling a functional block capable of automatically testing PLC software;
(2) compiling the program source code to generate a common intermediate language file;
(3) generating a solid library file from the public intermediate language file through a solid library generator in the PLC programming software, and constructing a solid library;
(4) adding the built firmware library in the PLC programming software;
(5) building a test framework by using functional blocks in a firmware library through PLC programming software;
(6) compiling the PLC program according to the constructed test framework, and generating a PLC engineering mirror image;
(7) and installing the generated engineering mirror image in an operation platform of a PLC program, starting operation, filling codes to be tested in the frame, and performing cycle test.
The automatic unit Test framework constructed in the method can divide the Test engineering into a plurality of Test groups, each Test group comprises a plurality of Test cases, each Test case is executed according to the sequence of the process SetUp- > Test- > Teardown, and the execution process is shown in figure 2.
The test frame is packaged into a functional block meeting the 61131-3 standard without setting parameters additionally
1. The Test framework classifies all Test cases into groups, each group being called a Test group
2. The test group comprises a start segment (SetUp) and an end segment (TearDown);
3. executing each Test case according to the sequence of SetUp- > Test- > Teardown to Test;
4. displaying the test structure after all the test cases are executed;
5. the Test group (TestGroup) or the Test case (Test) to be executed can be flexibly adjusted according to the requirement.
Example 2:
on the basis of the foregoing embodiment, in this embodiment, further, the program written by inputting the source code through the C # program in step (1) includes:
the LTest _ SetUp declares a public execution part of the test group before the test case is started to be executed;
the LTest _ SetUpDone and the LTest _ SetUp are used in pair;
the test _ Teardown declares the test, and after the test case is executed by the test group, the test group executes the part in public;
the LTest _ TearDown Done and the LTest _ TearDown are used in pair;
LTest _ TestCaseStart, declare the test case;
the LTest _ TestCaseEnd is used in pair with the LTest _ TestCaseStart;
the LTest _ Result is used for obtaining the execution Result of the current test;
LTest _ Config, configuring test cases that need to be executed or not.
The test _ SetUp and the test _ TearDown are common execution parts added before and after the test case, and can be understood as a start character and an end character of the test group to identify the test group. All test cases are grouped according to the same start and end, so that repeated code copying is avoided, the groups are called test groups, and certainly, the grouping can be further performed according to the tested functions.
And executing each Test case according to the sequence of SetUp- > Test- > Teardown to Test.
During operation, the SetUp and the TearDown divide the PLC program into a plurality of test groups, and the Start and the End divide the program in the test groups into a plurality of test cases.
All the function blocks are managed by an internal state machine in a unified way, each function block (except Result and Config) corresponds to an internal state, namely, Done and End, and is used for recording the state, representing that the execution of the code segment is finished, whether a code between SetUp and SetUpDone is controlled by SetUp is executed, whether a code between TearDown and TearDown is controlled by TearDown is executed, and whether a code between TestCaseStart and TestCaseEnd is executed is controlled by TestCaseStart.
Other parts of this embodiment are the same as those of the above embodiment, and are not described again here.
Example 3:
in this embodiment, on the basis of the above embodiment, the firmware library file generated in the step (3) further includes a function block name, an input variable, an output variable, and an input/output variable.
Example 4:
in this embodiment, based on the above embodiment, further, the PLC programming software is Multiprog. The MultiProg is a programming system based on IEC standard and traditional PLC standard, and can edit, compile and debug PLC engineering. Other parts of this embodiment are the same as those of the above embodiment, and are not described again here.
Example 5:
in this embodiment, on the basis of the above embodiment, in the step (6), the process of compiling the PLC program according to the constructed test code is to convert the common intermediate language file into the machine code of the ProConOS platform by using a method of converting the common intermediate language file into the machine code. Other parts of this embodiment are the same as those of the above embodiment, and are not described again here.
Example 6:
in this embodiment, on the basis of the above embodiment, the running platform of the PLC program in step (7) is a ProConOS platform. ProconOS is a high performance PLC engine designed specifically for embedded and PC-based control applications. ProconOS can work in conjunction with mainstream embedded systems (e.g., Vxworks, QNX, OS 9) and the like, providing deterministic control performance down to 1ms run-time. Other parts of this embodiment are the same as those of the above embodiment, and are not described again here.
While embodiments of the invention have been shown and described, it will be understood by those of ordinary skill in the art that: various changes, modifications, substitutions and alterations can be made to these embodiments without departing from the principles and spirit of the invention, the scope of which is defined by the claims and their equivalents.
Claims (6)
1. A method for carrying out automatic unit test aiming at a PLC program is characterized by comprising the following steps:
(1) inputting a source code through a C # program, and compiling a functional block capable of automatically testing PLC software;
(2) compiling the program source code to generate a common intermediate language file;
(3) generating a solid library file from the public intermediate language file through a solid library generator in the PLC programming software, and constructing a solid library;
(4) adding the built firmware library in the PLC programming software;
(5) building a test framework by using functional blocks in a firmware library through PLC programming software;
(6) compiling the PLC program according to the constructed test framework, and generating a PLC engineering mirror image;
(7) and installing the generated engineering mirror image in an operation platform of a PLC program, starting operation, filling codes to be tested in the frame, and performing cycle test.
2. The method for performing the automation unit test for the PLC program according to claim 1, wherein the program written by the C # program input source code in the step (1) includes:
the LTest _ SetUp declares a public execution part of the test group before the test case is started to be executed;
the LTest _ SetUpDone and the LTest _ SetUp are used in pair;
the test _ Teardown declares a test, and a common execution part of the test group is after the test case is executed;
the LTest _ TearDown Done and the LTest _ TearDown are used in pair;
LTest _ TestCaseStart, declare the test case;
the LTest _ TestCaseEnd is used in pair with the LTest _ TestCaseStart;
the LTest _ Result is used for obtaining the execution Result of the current test;
LTest _ Config, configuring test cases that need to be executed or not.
3. The method for conducting the automation unit test for the PLC program according to claim 1 or 2, wherein the firmware library file generated in the step (3) includes a function block name, an input variable, an output variable, and an input/output variable.
4. A method for automated unit testing of a PLC program according to claim 1 or 2, wherein the PLC programming software is Multiprog.
5. The method for performing automation unit testing on a PLC program according to claim 1 or 2, wherein the compiling of the PLC program according to the constructed test code in step (6) is performed by converting the common intermediate language file into the machine code of the ProConOS platform by using a method of converting the common intermediate language file into the machine code.
6. The method for conducting an automated unit test for a PLC program according to claim 1 or 2, wherein the running platform of the PLC program in the step (7) is a ProConOS platform.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010124563.7A CN111258915B (en) | 2020-02-27 | 2020-02-27 | Method for carrying out automatic unit test on PLC program |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010124563.7A CN111258915B (en) | 2020-02-27 | 2020-02-27 | Method for carrying out automatic unit test on PLC program |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111258915A true CN111258915A (en) | 2020-06-09 |
| CN111258915B CN111258915B (en) | 2023-07-04 |
Family
ID=70951357
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010124563.7A Active CN111258915B (en) | 2020-02-27 | 2020-02-27 | Method for carrying out automatic unit test on PLC program |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111258915B (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112349340A (en) * | 2020-11-08 | 2021-02-09 | 北京工业大学 | Waste equipment overwriting scheme library building method based on cycle test |
| CN112506793A (en) * | 2020-12-18 | 2021-03-16 | 航天信息股份有限公司 | Embedded software unit testing method, system, readable medium and electronic equipment |
Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101876940A (en) * | 2009-11-30 | 2010-11-03 | 北京飞天诚信科技有限公司 | Automatic test method and device |
| US8279204B1 (en) * | 2005-12-22 | 2012-10-02 | The Mathworks, Inc. | Viewer for multi-dimensional data from a test environment |
| CN103645730A (en) * | 2013-12-09 | 2014-03-19 | 成都乐创自动化技术股份有限公司 | Motion control card with self-checking function and detection method |
| CN104407973A (en) * | 2014-11-25 | 2015-03-11 | 珠海格力电器股份有限公司 | Method and device for realizing automatic unit test |
| CN105740477A (en) * | 2016-03-18 | 2016-07-06 | 中国科学院信息工程研究所 | Function searching method for large-scale embedded device firmware and search engine |
| US20160299829A1 (en) * | 2015-04-10 | 2016-10-13 | Siemens Aktiengesellschaft | Verification and Validation of Third Party PLC Code |
| CN108052453A (en) * | 2017-12-29 | 2018-05-18 | 北京天诚同创电气有限公司 | Test method, device, equipment and the medium of programmable logic controller program |
| CN108415828A (en) * | 2018-01-23 | 2018-08-17 | 广州视源电子科技股份有限公司 | Program testing method and device, readable storage medium and computer equipment |
| CN109840201A (en) * | 2018-12-15 | 2019-06-04 | 中国平安人寿保险股份有限公司 | UI test method, device, electronic equipment and computer readable storage medium |
| CN110471851A (en) * | 2019-08-09 | 2019-11-19 | 北京首都在线科技股份有限公司 | A kind of automated testing method and device |
| CN110532177A (en) * | 2019-08-05 | 2019-12-03 | 华东师范大学 | A kind of automatic test cases generation system towards PLC program |
-
2020
- 2020-02-27 CN CN202010124563.7A patent/CN111258915B/en active Active
Patent Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8279204B1 (en) * | 2005-12-22 | 2012-10-02 | The Mathworks, Inc. | Viewer for multi-dimensional data from a test environment |
| CN101876940A (en) * | 2009-11-30 | 2010-11-03 | 北京飞天诚信科技有限公司 | Automatic test method and device |
| CN103645730A (en) * | 2013-12-09 | 2014-03-19 | 成都乐创自动化技术股份有限公司 | Motion control card with self-checking function and detection method |
| CN104407973A (en) * | 2014-11-25 | 2015-03-11 | 珠海格力电器股份有限公司 | Method and device for realizing automatic unit test |
| US20160299829A1 (en) * | 2015-04-10 | 2016-10-13 | Siemens Aktiengesellschaft | Verification and Validation of Third Party PLC Code |
| CN105740477A (en) * | 2016-03-18 | 2016-07-06 | 中国科学院信息工程研究所 | Function searching method for large-scale embedded device firmware and search engine |
| CN108052453A (en) * | 2017-12-29 | 2018-05-18 | 北京天诚同创电气有限公司 | Test method, device, equipment and the medium of programmable logic controller program |
| CN108415828A (en) * | 2018-01-23 | 2018-08-17 | 广州视源电子科技股份有限公司 | Program testing method and device, readable storage medium and computer equipment |
| CN109840201A (en) * | 2018-12-15 | 2019-06-04 | 中国平安人寿保险股份有限公司 | UI test method, device, electronic equipment and computer readable storage medium |
| CN110532177A (en) * | 2019-08-05 | 2019-12-03 | 华东师范大学 | A kind of automatic test cases generation system towards PLC program |
| CN110471851A (en) * | 2019-08-09 | 2019-11-19 | 北京首都在线科技股份有限公司 | A kind of automated testing method and device |
Non-Patent Citations (2)
| Title |
|---|
| SUSANNERÖSCH* 等: "Model-based testing of PLC software: test of plants" reliability by using fault injection on component level", 《IFAC PROCEEDINGS VOLUMES》 * |
| 甘红胜 等: "基于PLC控制的温度控制器测试系统的设计", 《机电一体化》 * |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112349340A (en) * | 2020-11-08 | 2021-02-09 | 北京工业大学 | Waste equipment overwriting scheme library building method based on cycle test |
| CN112349340B (en) * | 2020-11-08 | 2023-10-10 | 北京工业大学 | Method for constructing waste equipment overwriting scheme library based on cyclic test |
| CN112506793A (en) * | 2020-12-18 | 2021-03-16 | 航天信息股份有限公司 | Embedded software unit testing method, system, readable medium and electronic equipment |
| CN112506793B (en) * | 2020-12-18 | 2024-05-28 | 航天信息股份有限公司 | Method and system for testing embedded software unit, readable medium and electronic equipment |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111258915B (en) | 2023-07-04 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107273286B (en) | Scene automatic test platform and method for task application | |
| CN108345265B (en) | Programming method of hardware device, visual programming platform, memory and processor | |
| US11687062B2 (en) | Configuration of a modular plant | |
| CN111258915B (en) | Method for carrying out automatic unit test on PLC program | |
| CN108132876B (en) | Embedded software object code unit testing method based on injection mode | |
| US20070061641A1 (en) | Apparatus and method for generating test driver | |
| CN113254054B (en) | Intelligent contract one-stop development system and method | |
| CN111723009A (en) | Framework system of python automated testing series products | |
| CN115202799A (en) | Aircraft engine control software simulation system and generation method thereof | |
| Wahler et al. | CAST: Automating software tests for embedded systems | |
| US11604446B2 (en) | Method and system for validating a control program | |
| KR20190094779A (en) | Automatically Generate Device for PLC Instruction Compiler Test-Case | |
| CN112858876A (en) | Self-adaptive chip automatic testing method | |
| JP3965068B2 (en) | Integrated test case language for verifying hardware designs | |
| CN109144849A (en) | A kind of embedded software adjusting, measuring method | |
| EP0801348A1 (en) | Method of monitoring the operation of a computer | |
| Zhang et al. | An approach for resource Function Block generation: Towards RAMI4. 0-compliant PLC Programming | |
| CN111723011B (en) | Platform implementation method for radar algorithm deployment and performance test | |
| CN113392436A (en) | CAE analysis software and office software integrated control method and platform | |
| CN117215283A (en) | In-loop test method and device for engine controller | |
| Hofer | IEC 61131–3 Software Testing-Automatic test generation for native applications | |
| CN115757088B (en) | Fault injection method, device and equipment based on environment variable | |
| CN111723011A (en) | Platform implementation method for radar algorithm deployment and performance test | |
| CN118550784A (en) | Automatic test case integration method and device and case test method and device | |
| CN115543777A (en) | Cross test framework design method and system for embedded software |
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 |