CN112597029A - Standard inspection system, method, device and medium - Google Patents
Standard inspection system, method, device and medium Download PDFInfo
- Publication number
- CN112597029A CN112597029A CN202011569130.9A CN202011569130A CN112597029A CN 112597029 A CN112597029 A CN 112597029A CN 202011569130 A CN202011569130 A CN 202011569130A CN 112597029 A CN112597029 A CN 112597029A
- Authority
- CN
- China
- Prior art keywords
- rule
- checking
- microkernel
- standard
- check
- 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.)
- Pending
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/3604—Software analysis for verifying properties of programs
Abstract
The utility model provides a standard inspection system, this system includes microkernel and rule management device, microkernel and rule management device decoupling zero, rule management device is used for receiving the inspection logic of user's input, according to inspection logic generation standard inspection rule, microkernel is used for treating the code engineering file of examining and carries out the inspection logic in the corresponding standard inspection rule, realizes the standard inspection to the code engineering file to can realize the standard inspection to the code engineering file under the circumstances of many scenes.
Description
Technical Field
The present application relates to the field of software development technologies, and in particular, to a system, a method, a device, and a computer-readable storage medium for specification checking.
Background
As the complexity of software is higher and higher, the service coverage is wide, and each service module is complicated and complicated. Therefore, more and more software is in a team development mode. In team development, developers are numerous, development experience and code style are different, and a uniform standard is lacked, so that codes of the whole project are difficult to read, and risk hazards exist. Therefore, the specification of the software code needs to be checked.
With the updating of technology, the specification inspection has been changed from the traditional manual reading mode to the batch scanning mode using related tools. At present, the mature standard inspection tool implementation cases are PMD and the like.
Although the specification checking tool implementation methods meet the requirement of code specification scanning to a certain extent, the tool coupling degree is high, the change of default rules or the iteration of the functions of the tool can cause the whole release of the tool and the rules, and the potential risk problem possibly caused by the fact that a user does not update the tool in time is increased.
Disclosure of Invention
The utility model provides a standard inspection system, this system includes microkernel and rule management device, microkernel and rule management device decoupling zero, rule management device is used for receiving the inspection logic of user's input, according to inspection logic generation standard inspection rule, microkernel is used for treating the code engineering file of examining and carries out the inspection logic in the corresponding standard inspection rule, realizes the standard inspection to the code engineering file to can realize the standard inspection to the code engineering file under the circumstances of many scenes. The application also provides a method, equipment and a medium corresponding to the system.
In a first aspect, the present application provides a specification checking system, the system comprising a microkernel and a rule management device, the microkernel and the rule management device being decoupled;
the rule management device is used for receiving the check logic input by the user and generating a standard check rule according to the check logic;
and the microkernel is used for executing the check logic in the corresponding standard check rule on the code engineering file to be checked so as to realize the standard check on the code engineering file.
In some possible implementations, the microkernel is specifically configured to:
loading a corresponding rule set according to the scene information, wherein the rule set comprises at least one standard check rule;
and executing the checking logic in at least one standard checking rule in the rule set on the code engineering file to be checked to realize the standard checking on the code engineering file.
In some possible implementations, the rule management apparatus is further configured to:
and updating the specification checking rule according to user operation.
In some possible implementations, the specification checking rules include any one or more of code specification checking rules, log configuration file specification checking rules, attribute file specification checking rules, or package specification checking rules.
In some possible implementations, the rule management device is further configured to generate a shadow rule, the shadow rule being configured to load a code engineering file or generate a report when executed by the microkernel.
In some possible implementations, the microkernel is obtained from a Maven plugin, and the specification checking rule is obtained through Maven engineering.
In a second aspect, the present application provides a specification checking method, which is applied to a specification checking system, the system including a microkernel and a rule management device, the microkernel and the rule management device being decoupled, the method including:
the rule management device receives the check logic input by the user and generates a standard check rule according to the check logic;
and the microkernel executes the check logic in the corresponding standard check rule on the code engineering file to be checked to realize the standard check on the code engineering file.
In some possible implementation manners, the microkernel executes a check logic in a corresponding specification check rule on the code engineering file to be checked, so as to implement specification check on the code engineering file, including:
loading a corresponding rule set according to the scene information, wherein the rule set comprises at least one standard check rule;
and executing the checking logic in at least one standard checking rule in the rule set on the code engineering file to be checked to realize the standard checking on the code engineering file.
In some possible implementations, the method further includes:
the rule management means updates the specification check rule according to a user operation.
In some possible implementations, the specification checking rules include any one or more of code specification checking rules, log profile specification checking rules, attribute file specification checking rules, or package specification checking rules.
In some possible implementations, the method further includes:
the rule management device generates a shadow rule, and the shadow rule is used for loading a code engineering file or generating a report when being executed by the microkernel.
In some possible implementations, the microkernels are obtained from a Maven plugin, and the specification check rules are obtained from a Maven project.
In a third aspect, the present application provides an apparatus comprising a processor and a memory. The processor and the memory communicate with each other. The processor is configured to execute instructions stored in the memory to cause the apparatus to perform the specification checking method as in the second aspect or any implementation of the second aspect.
In a fourth aspect, the present application provides a computer-readable storage medium having instructions stored therein, the instructions instructing a device to execute the specification checking method according to the second aspect or any implementation manner of the second aspect.
In a fifth aspect, the present application provides a computer program product comprising instructions which, when run on a device, cause the device to perform the specification checking method of the second aspect or any implementation of the second aspect.
The present application can further combine to provide more implementations on the basis of the implementations provided by the above aspects.
According to the technical scheme, the embodiment of the application has the following advantages:
the embodiment of the application provides a standard checking system, which comprises a microkernel and a rule management device, wherein the microkernel and the rule management device are decoupled, the rule management device is used for receiving checking logic input by a user and generating a standard checking rule according to the checking logic, and the microkernel is used for executing the checking logic in the corresponding standard checking rule on a code engineering file to be checked so as to realize the standard checking on the code engineering file.
Therefore, the system has low coupling, strong robustness, high degree of freedom and strong expansibility, can support various file types, and can meet the requirement of a user on standard inspection of code engineering files in multiple scenes.
Drawings
In order to more clearly illustrate the technical method of the embodiments of the present application, the drawings needed to be used in the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and other drawings can be obtained by those skilled in the art without inventive labor.
Fig. 1 is a schematic system architecture diagram of a specification checking system according to an embodiment of the present application;
FIG. 2 is a flowchart illustrating a method for implementing a microkernel according to an embodiment of the present disclosure;
fig. 3 is a schematic flowchart of a method for a user to write inspection logic by himself according to an embodiment of the present application;
fig. 4 is a schematic flowchart of a specification checking method according to an embodiment of the present disclosure.
Detailed Description
The scheme in the embodiments provided in the present application will be described below with reference to the drawings in the present application.
The terms "first" and "second" in the embodiments of the present application are used for descriptive purposes only and are not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature.
Some technical terms referred to in the embodiments of the present application will be first described.
The specification inspection refers to a process of inspecting the specification of the code engineering file, and the specification inspection is usually performed in a batch scanning mode by using a specification inspection tool. The batch inspection tool is mainly used for carrying out static inspection on the program codes and realizing the function of standard inspection.
A programming mistake checker (PMD) is a commonly used specification checking tool. Although the specification checking tool can meet the requirement of code specification scanning to a certain extent, the coupling degree of the tool is high, when the default rule is changed or the function of the tool is iterated, the tool and the rule are integrally issued, and the potential risk problem possibly caused by the fact that a user does not update the tool in time is increased.
In view of this, the present application provides a specification checking system and method, where the system includes a microkernel and a rule management device, the microkernel and the rule management device are decoupled, the rule management device is configured to receive a checking logic input by a user, and generate a specification checking rule according to the checking logic, and the microkernel is configured to execute the checking logic in the corresponding specification checking rule on a code engineering file to be checked, so as to implement specification checking on the code engineering file. The system has low coupling, strong robustness, high degree of freedom and strong expansibility, can support various file types, and meets the requirement of a user on standard inspection of software code engineering files in multiple scenes.
For the sake of understanding, the specification checking system provided by the embodiment of the present application is described below with reference to the drawings.
Referring to FIG. 1, the system 100 includes a microkernel 102 and a rule management device 104.
The microkernel 102 is a Maven plug-in with only functions of information transfer, rule loading and execution, the rule management device 104 is used for executing the development functions of the auxiliary function and the rule, and the microkernel 102 and the rule management device 104 are decoupled.
Decoupling (decoupling) refers to using a high-cohesion connection mode, which makes the microkernel 102 and the rule management device 104 depend on each other internally, provides only necessary interfaces or message objects externally, has a low coupling degree, and improves reusability of a program.
Maven is a project object model, and particularly can manage project construction, report and document project management through a small piece of description information.
In this embodiment, the rule management device 104 is configured to receive an inspection logic input by a user (e.g., a user of the system), generate a specification inspection rule according to the inspection logic, and the microkernel 102 is configured to execute the inspection logic in the corresponding specification inspection rule on the code engineering file to be inspected, so as to implement specification inspection on the code engineering file.
In some possible implementations, the rule management device 104 is further configured to check the rule according to a user operation update specification. The specification checking rules comprise any one or more of code specification checking rules, log configuration file specification checking rules, attribute file specification checking rules or file package specification checking rules.
Rule management device 104 is also used to generate shadow rules that load code engineering files or generate reports when executed by microkernel 102.
Microkernel 102 may be available from a program development tool, such as a Maven plugin in which microkernel 102 is implemented, and in particular, the processing device receives a user request. The processing device can be different types of terminal devices, such as a mobile phone, a display, a tablet computer, and the like, and a Maven plug-in is deployed on the terminal device.
Referring to FIG. 2, taking microkernel 102 obtained via a Maven plugin as an example, an implementation process of microkernel 102 is described as follows.
S202: the processing device receives a request from a user to create a project.
In a particular implementation, a user causes a processing device to create a Maven plug-in item using a Maven-arch-plug-in command.
S204: the processing device receives a request from a user and defines a tool context.
A context is a collection of stored key-value pairs, typically as an information collection hub for the entire tool. Specifically, the processing device receives a request from a user, and defines a tool context in the Maven plugin. Where a user may define multiple contexts in the same class as desired. In some possible implementations, the Maven plugin provides the user with an interface method to customize the context in microkernel 102 to increase extensibility.
S206: the processing device receives a request from a user, defines a service providing interface implementation interface and an execution method, creates a base class to implement the interface, and rewrites the execution method.
A Service Provider Interface (SPI) is a service provision discovery mechanism built in a Java language software development kit (JDK). When a service provider provides an implementation of a service interface, a file named by the service interface needs to be created in META-INF/services/directory under a class path (classpath), and the file is a specific implementation class for implementing the service interface. When an external program assembles the service, the specific implementation class name can be found through the file, and the instantiation is loaded according to the class name.
S208: the processing device receives a user's request, defines member variables, and adds annotations.
Specifically, microkernel 102 is defined in a Maven plug-in as a member variable of a single task unit (Maven old Java object, Mojo) class in Maven, and adds @ Parameter annotation on the member variable. Further, property and alias attributes may be added to the annotation to receive parameter values that are passed in by the command line and the Project Object Model (POM).
S210: the processing equipment receives the request of the user and creates a URLClasLoader object.
Specifically, the processing device creates a URLClassLoader object in the Maven plugin according to a request of a user, and the URLClassLoader object is used for loading a rule set according to the scene information.
S212: the processing device receives a request of a user and creates a ServiceLoader object.
Specifically, the processing device creates a ServiceLoader object in the Maven plug-in according to the request of the user, so as to search and load the rule service and instantiate the rule service.
S214: the processing device receives the request of the user, calls an execution method in the interface and executes the check logic in the rule.
Specifically, the processing device calls an execution method in the interface in the Maven plug-in according to the request of the user, so as to execute the check logic in the rule.
The check logic refers to a set of preset logic check rules for analyzing, comparing, screening and collating the program code engineering files.
Likewise, the inspection logic may be made available to the user using a program development tool, such as a Maven plugin, where the processing device receives the user's request and defines the inspection logic on its own as needed. The processing device can be different types of terminal devices, such as a mobile phone, a display, a tablet computer, and the like, and a Maven plug-in is deployed on the terminal device.
Referring to fig. 3, the writing process of the user for the checking logic is described as follows.
S302: and the processing equipment receives a new project request of a user and creates a new project.
Specifically, the processing device newly builds a common Maven project according to a newly built Maven project request of a user.
S304: and the processing equipment receives a new directory request of a user and creates a new directory.
Specifically, the processing device receives a new directory request of a user, and a/META-INF/services directory is newly built under the src/main/resources directory.
S306: and the processing equipment receives a file creating request of a user and creates a new file.
Specifically, the processing device receives a file creating request of a user, and creates a file named by a service interface under the services directory.
S308: the processing device receives an interface adding request of a user, and adds an interface in the file to realize the package path.
S310: the processing device receives a rewrite request from a user, inherits the base class in the microkernel 102 in the implementation class of the rule interface, and rewrites the execution method in the base class.
S312: the processing device receives a writing request of a user, and writes specific checking logic in the execution method.
According to the scheme, the check logic in the scheme can be defined by the user according to the requirement, so that the degree of freedom of the scheme is improved.
In the scheme, the realization of the microkernel 102 and the self-defining process of the check logic can be executed in parallel, so that the user-defined check logic and the microkernel 102 with the functions of information transfer, rule loading and execution can be obtained.
In this way, the user can realize the specification check of the code engineering file through the specification check system, wherein the code engineering file not only comprises the code file, but also comprises files in other various formats. In the system, the microkernel 102 and the rule management device 104 are decoupled, so that the coupling degree of the scheme is low. Meanwhile, the microkernel 102 only has the functions of information transfer, rule loading and execution, so that frequent iteration version issuing is not needed, and the robustness of the scheme is strong. The user can define the checking logic according to the requirement, the degree of freedom is high, and various files can be checked, so that the method has wide applicability. And finally, the whole process can be developed based on the Maven plug-in, the programming idea and logic are simple, and developers can learn and apply the method conveniently.
The above is a description of the architecture of the specification checking system 100, and the following is a detailed description of the specification checking method provided in the embodiments of the present application with reference to the drawings.
Referring to fig. 4, a flowchart of a specification checking method is shown, the method comprising:
s402: the rule management device 104 receives user input of the checking logic.
The checking logic refers to a preset logic for analyzing, comparing, screening and collating the program code engineering files, and the checking logic in the application can be defined by a user according to actual needs, and the specific steps are shown in fig. 3.
Specifically, the user writes the check logic as needed, and the rule management device 104 receives the check logic input by the user through a command line or a programming language.
S404: the rule management device 104 generates a specification check rule according to the check logic.
The standard check rule is used to check whether the file to be checked meets preset check logic, such as checking whether a legacy test code (e.g., system. out. print () or the like) exists in Java code, whether a problem that Structured Query Language (SQL) injection may occur exists in an extensible markup language (XML) file, whether a dependency that may cause a production failure exists in a package for production, or the like.
In some possible implementations, the specification checking rules include any one or more of code specification checking rules, log profile specification checking rules, attribute file specification checking rules, or package specification checking rules.
In particular, rule management device 104 checks the rules according to the checking logic input by the user according to the specifications that generate the rules that can be read by subsequent microkernels 102.
In some possible implementations, the user may rewrite the inspection logic, and the rule management device 104 updates the canonical inspection rule according to the inspection logic changed by the user.
S406: microkernel 102 loads the corresponding rule set based on the context information.
The context information refers to a context environment corresponding to the code engineering file to be checked, and the microkernel 102 may be obtained by establishing a corresponding server. The code engineering files to be checked include SQL scripts, log configuration files, properties files, Java Archive (JAR) packages, Web Archive (WAR) packages and other files in various formats.
S408: microkernel 102 executes the checking logic in the corresponding standard checking rule to the code engineering file to be checked, so as to realize the standard checking of the code engineering file.
Specifically, microkernel 102 executes the corresponding checking logic in the specification checking rule for the code engineering file to be checked according to the rule configured in the rule set, thereby implementing the specification checking on the code engineering file.
In some possible implementations, the present solution further includes generating a shadow rule by rule management device 104, where the shadow rule is used to load the code engineering file or generate a report when executed by microkernel 102, and serve microkernel 102 and specification checking rules.
Therefore, the specification inspection method provided by the application can be used for carrying out specification inspection on files in various formats such as SQL scripts, log configuration files, properties files, JAR packages, WAR packages and the like, so that the requirement of a user on the specification inspection of the engineering files in multiple scenes is met.
The microkernel 102 only has the functions of information transfer, rule loading and execution, and the rule management device 104 for executing the auxiliary function and the rule development function is completely decoupled from the microkernel 102, so that the program coupling is low. Meanwhile, due to the simple function of the microkernel 102, frequent iteration version issuing is not needed, and the robustness of the program is strong.
Furthermore, the checking logic can be used for generating a rule set by combining the custom scenes of the rules according to the requirements of a user and checking the engineering file specifications, so that the degree of freedom of the program is high. After the rules are developed, the rules can be added to corresponding scenes according to requirements, so that the tool expansibility can be increased.
Finally, microkernel 102 is developed based on a Maven plug-in, documents are rich, more APIs can be called, specification checking rules are obtained through a Maven project, a Java programming language is used, programming ideas and logic are simple, and developers can learn conveniently.
The present application provides an apparatus for implementing a specification checking method. The apparatus includes a processor and a memory. The processor and the memory communicate with each other. The processor is configured to execute instructions stored in the memory to cause the device to perform the specification checking method.
The present application provides a computer-readable storage medium having stored therein instructions that, when run on a device, cause the device to perform the above-described method of specification checking.
The present application provides a computer program product comprising instructions which, when run on an apparatus, cause the apparatus to perform the above-described method of providing a specification check.
It should be noted that the above-described embodiments of the apparatus are merely schematic, where the units described as separate parts may or may not be physically separate, and the parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment. In addition, in the drawings of the embodiments of the apparatus provided in the present application, the connection relationship between the modules indicates that there is a communication connection therebetween, and may be implemented as one or more communication buses or signal lines.
Through the above description of the embodiments, those skilled in the art will clearly understand that the present application can be implemented by software plus necessary general-purpose hardware, and certainly can also be implemented by special-purpose hardware including special-purpose integrated circuits, special-purpose CPUs, special-purpose memories, special-purpose components and the like. Generally, functions performed by computer programs can be easily implemented by corresponding hardware, and specific hardware structures for implementing the same functions may be various, such as analog circuits, digital circuits, or dedicated circuits. However, for the present application, the implementation of a software program is more preferable. Based on such understanding, the technical solutions of the present application may be substantially embodied in the form of a software product, which is stored in a readable storage medium, such as a floppy disk, a usb disk, a removable hard disk, a ROM, a RAM, a magnetic disk, or an optical disk of a computer, and includes several instructions for enabling a computer device (which may be a personal computer, an exercise device, or a network device) to execute the method according to the embodiments of the present application.
In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product.
The computer program product includes one or more computer instructions. When loaded and executed on a computer, cause the processes or functions described in accordance with the embodiments of the application to occur, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, from one website site, computer, training device, or data center to another website site, computer, training device, or data center via wired (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that a computer can store or a data storage device, such as a training device, a data center, etc., that incorporates one or more available media. The usable medium may be a magnetic medium (e.g., floppy Disk, hard Disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., Solid State Disk (SSD)), among others.
Claims (10)
1. A specification checking system, said system comprising a microkernel and a rule management means, said microkernel and said rule management means being decoupled;
the rule management device is used for receiving the check logic input by the user and generating a standard check rule according to the check logic;
the microkernel is used for executing the checking logic in the corresponding standard checking rule on the code engineering file to be checked so as to realize the standard checking on the code engineering file.
2. The system of claim 1, wherein the microkernel is specifically configured to:
loading a corresponding rule set according to the scene information, wherein the rule set comprises at least one standard check rule;
and executing the checking logic in at least one standard checking rule in the rule set on the code engineering file to be checked to realize the standard checking on the code engineering file.
3. The system of claim 1, wherein the rule management device is further configured to:
and updating the specification checking rule according to user operation.
4. The system of any one of claims 1 to 3, wherein the specification checking rules comprise any one or more of code specification checking rules, log configuration file specification checking rules, attribute file specification checking rules, or package specification checking rules.
5. The system according to any one of claims 1 to 3, wherein the rule management means is further configured to generate a shadow rule, the shadow rule being configured to load the code engineering file or generate a report, etc. when executed by the microkernel.
6. The system of any of claims 1 to 3, wherein the microkernels are obtained according to a Maven plugin and the specification checking rules are obtained by Maven engineering.
7. A specification checking method applied to a specification checking system, the system including a microkernel and a rule management device, the microkernel and the rule management device being decoupled, the method comprising:
the rule management device receives check logic input by a user and generates a standard check rule according to the check logic;
and the microkernel executes the check logic in the corresponding standard check rule on the code engineering file to be checked to realize the standard check on the code engineering file.
8. An apparatus, comprising a processor and a memory;
the processor is configured to execute instructions stored in the memory to cause the device to perform the method of claim 7.
9. A computer-readable storage medium comprising instructions that direct a device to perform the method of claim 7.
10. A computer program product, characterized in that it causes a computer to carry out the method as claimed in claim 7, when the computer program product is run on the computer.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011569130.9A CN112597029A (en) | 2020-12-26 | 2020-12-26 | Standard inspection system, method, device and medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011569130.9A CN112597029A (en) | 2020-12-26 | 2020-12-26 | Standard inspection system, method, device and medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112597029A true CN112597029A (en) | 2021-04-02 |
Family
ID=75202632
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011569130.9A Pending CN112597029A (en) | 2020-12-26 | 2020-12-26 | Standard inspection system, method, device and medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112597029A (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20070283325A1 (en) * | 2006-06-02 | 2007-12-06 | Abhishek Kumar | Quality inspector tool |
| JP2015011445A (en) * | 2013-06-27 | 2015-01-19 | 株式会社東芝 | Model inspection device |
| CN107678957A (en) * | 2017-09-25 | 2018-02-09 | 中国银行股份有限公司 | A kind of Net silver code automatic checking method and device |
| CN110134579A (en) * | 2019-01-18 | 2019-08-16 | 北京车和家信息技术有限公司 | Code check method and apparatus |
| CN111797084A (en) * | 2020-06-16 | 2020-10-20 | 中国人民解放军92493部队参谋部 | Data coding through mark inspection method and system based on weapon equipment test process |
-
2020
- 2020-12-26 CN CN202011569130.9A patent/CN112597029A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20070283325A1 (en) * | 2006-06-02 | 2007-12-06 | Abhishek Kumar | Quality inspector tool |
| JP2015011445A (en) * | 2013-06-27 | 2015-01-19 | 株式会社東芝 | Model inspection device |
| CN107678957A (en) * | 2017-09-25 | 2018-02-09 | 中国银行股份有限公司 | A kind of Net silver code automatic checking method and device |
| CN110134579A (en) * | 2019-01-18 | 2019-08-16 | 北京车和家信息技术有限公司 | Code check method and apparatus |
| CN111797084A (en) * | 2020-06-16 | 2020-10-20 | 中国人民解放军92493部队参谋部 | Data coding through mark inspection method and system based on weapon equipment test process |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108027722B (en) | Dynamically updating applications in compilation and deployment | |
| US9465590B2 (en) | Code generation framework for application program interface for model | |
| US20160342413A1 (en) | Verification of backward compatibility of software components | |
| US11429365B2 (en) | Systems and methods for automated retrofitting of customized code objects | |
| US20190004774A1 (en) | Automated source code adaption to inject features between platform versions | |
| CN111399853A (en) | Templated deployment method of machine learning model and custom operator | |
| WO2017087801A1 (en) | Dynamic update of an application in compilation and deployment | |
| CN112148278A (en) | Visual block chain intelligent contract framework and intelligent contract development and deployment method | |
| CN115993966B (en) | Application development system and method | |
| CN112650526B (en) | Method, device, electronic equipment and medium for detecting version consistency | |
| CN114610598A (en) | Test method, test device, electronic equipment and computer readable storage medium | |
| CN117112060A (en) | Component library construction method and device, electronic equipment and storage medium | |
| CN110968339B (en) | Method and device for front-end building tool and electronic equipment | |
| CN112561690A (en) | Method, system, equipment and storage medium for testing credit card staging service interface | |
| WO2023151397A1 (en) | Application program deployment method and apparatus, device, and medium | |
| CN112068874A (en) | Software project continuous integration method and device, terminal equipment and storage medium | |
| CN111290961A (en) | Interface test management method and device and terminal equipment | |
| CN116414689A (en) | Interface parameter verification method and system based on reflection mechanism | |
| CN112597029A (en) | Standard inspection system, method, device and medium | |
| CN115185550A (en) | Service deployment method, device, computer equipment and storage medium | |
| CN113971019A (en) | Data type creating method, device, server and medium | |
| CN113504904A (en) | User-defined function implementation method and device, computer equipment and storage medium | |
| CN110737431B (en) | Software development method, development platform, terminal device and storage medium | |
| CN113806327A (en) | Database design method and device and related equipment | |
| CN113032004A (en) | Method, apparatus and program product for managing development jobs in a development environment |
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 |