CN106940647B - Code management method and device - Google Patents
Code management method and device Download PDFInfo
- Publication number
- CN106940647B CN106940647B CN201710165449.7A CN201710165449A CN106940647B CN 106940647 B CN106940647 B CN 106940647B CN 201710165449 A CN201710165449 A CN 201710165449A CN 106940647 B CN106940647 B CN 106940647B
- Authority
- CN
- China
- Prior art keywords
- macro definition
- macro
- definition
- value
- determining
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/73—Program documentation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/40—Transformation of program code
- G06F8/41—Compilation
- G06F8/43—Checking; Contextual analysis
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/40—Transformation of program code
- G06F8/41—Compilation
- G06F8/44—Encoding
- G06F8/443—Optimisation
Abstract
The invention discloses a code management method and device, and relates to the technical field of computer application. The code management method comprises the following steps: acquiring a first macro definition value to be compiled in a macro definition call request; when the first macro definition value is detected to be inconsistent with a second macro definition value of a pre-stored macro definition based on a detection script, determining the change state of the test marking parameter defined by the macro; and responding the macro definition call request according to the determined result. According to the technical scheme of the embodiment of the invention, when the fact that the first macro definition value to be compiled in the macro definition calling request is inconsistent with the second macro definition value of the pre-stored macro definition is detected, namely the macro definition is called and changed, the macro definition calling request is not directly responded, whether the macro definition is tested or not is determined by determining the change state of the test marking parameter of the macro definition, and then the macro definition calling request is responded according to the determination result, so that the safe calling of the macro definition can be effectively ensured.
Description
Technical Field
The embodiment of the invention relates to the technical field of computer application, in particular to a code management method and device.
Background
At present, the rapid development of computer technology and networks greatly facilitates the daily life of people. Today of science and technology, in order to meet the requirements of convenience and high efficiency in various aspects of people's life, work, entertainment and the like, more and more devices tend to adopt computer software to carry out intelligent control.
For intelligent devices developed by series such as televisions, mobile phones and the like, a situation that the same functional module or application software is developed by sharing a set of codes often occurs. In order to avoid the mutual influence between the codes for realizing different functions, the codes or code blocks of the newly added functions of engineers are expressed in a macro-definition form, so as to prevent errors, and improve the transportability, readability and convenience. However, since a set of codes may be used by multiple users and multiple clients simultaneously, if the functions corresponding to the macro definition are added without test verification, they are used by other engineers, and especially, the engineers may change the codes, such as parameter replacement, so that the code change that is not tested and verified is introduced into the production software, and the production software may have a serious quality risk.
Disclosure of Invention
The invention provides a code management method and a code management device, which are used for solving the safety problem caused by directly using a code which is not tested and verified, realizing automatic management of the code and improving the reliability and safety of the code use.
In a first aspect, an embodiment of the present invention provides a code management method, where the method includes:
acquiring a first macro definition value to be compiled in a macro definition call request;
when the first macro definition value is detected to be inconsistent with a second macro definition value of a pre-stored macro definition based on a detection script, determining the change state of the test marking parameter defined by the macro;
and responding the macro definition call request according to the determined result.
In a second aspect, an embodiment of the present invention further provides a code management apparatus, where the apparatus includes:
the obtaining module is used for obtaining a first macro definition value to be compiled in the macro definition calling request;
a change state determination module, configured to determine a change state of the test marking parameter defined by the macro when it is detected, based on the detection script, that the first macro definition value is inconsistent with a second macro definition value of a pre-stored macro definition;
and the response module is used for responding the macro definition call request according to the determination result.
According to the technical scheme of the embodiment of the invention, when the fact that the first macro definition value to be compiled in the macro definition calling request is inconsistent with the second macro definition value of the pre-stored macro definition is detected, namely the macro definition is called and changed, the macro definition calling request is not directly responded, whether the macro definition is tested or not is determined by determining the change state of the test marking parameter of the macro definition, and then the macro definition calling request is responded according to the determination result, so that the safe calling of the macro definition can be effectively ensured.
Drawings
In order to more clearly illustrate the technical solutions of the exemplary embodiments of the present invention, a brief description is given below of the drawings used in describing the embodiments. It should be clear that the described figures are only views of some of the embodiments of the invention to be described, not all, and that for a person skilled in the art, other figures can be derived from these figures without inventive effort.
Fig. 1 is a flowchart of a code management method according to an embodiment of the present invention;
fig. 2 is a flowchart of a code management method according to a second embodiment of the present invention;
fig. 3 is a block diagram of a code management apparatus according to a third embodiment of the present invention.
Detailed Description
The technical scheme of the invention is further explained by the specific implementation mode in combination with the attached drawings. It is to be understood that the specific embodiments described herein are merely illustrative of the invention and are not limiting of the invention. It should be further noted that, for the convenience of description, only some of the structures related to the present invention are shown in the drawings, not all of the structures.
Before discussing exemplary embodiments in more detail, it should be noted that some exemplary embodiments are described as processes or methods depicted as flowcharts. Although a flowchart may describe the steps as a sequential process, many of the steps can be performed in parallel, concurrently or simultaneously. In addition, the order of the steps may be rearranged. The process may be terminated when its operations are completed, but may have additional steps not included in the figure. The processes may correspond to methods, functions, procedures, subroutines, and the like.
Example one
Fig. 1 is a flowchart of a code management method according to an embodiment of the present invention. The method of the present embodiment may be performed by a code management apparatus, which may be implemented by hardware and/or software, and may be implemented by a server and a terminal in cooperation in general.
The method of the embodiment specifically includes:
s110, obtaining a first macro definition value to be compiled in the macro definition calling request.
In code management, the use of macro definitions can improve the universality and readability of programs, reduce inconsistency and reduce input errors. Especially when the program contains parameters, the macro-defined application makes program debugging more convenient. The macro definition call request typically includes a first macro definition value that is required by the user or that is required to call the macro definition. For example, the first macro definition value may be one or more parameters that indicate the details of the code segment that the macro defines, or may be a constant that indicates the state of the macro definition switch. Specifically, the first macro definition value may be represented by a numerical value, a word, and/or a character string, etc.
And S120, when the first macro definition value is detected to be inconsistent with a second macro definition value of a pre-stored macro definition based on the detection script, determining the change state of the test marking parameter of the macro definition.
In order to facilitate the management and debugging of the program code, the form of a macro definition of a code block that may be used is usually pre-stored, and a second macro definition value of the pre-stored macro definition is also an initially set macro definition value or a default value. Since the obtained macro definition call request includes the first macro definition value to be compiled, it may be detected whether the first macro definition value is consistent with the second macro definition value based on the detection script, and if not, it indicates that the user needs to enable the macro definition or change the code of the macro definition. In order to ensure the safety and practicability of the code, the change state of the test marking parameter of the macro definition can be further determined so as to confirm whether the invoked macro definition passes the test verification.
Illustratively, the change state of the quiz mark parameter defined by the macro may be determined by adding or deleting quiz marks. Specifically, the macro definition added for the first time is marked without test, and if the macro definition is detected to have the untested mark, it is determined that the test mark parameter of the macro definition has not changed. It is to be understood that, since the untested flag is added to the macro definition to distinguish whether the macro definition passes the test verification, once the macro definition that fails the test verification passes the test verification, the untested flag may be deleted or replaced with a tested flag, and when the macro definition is detected to have the tested flag, the test flag parameter of the macro definition is determined to have changed. Of course, it is also possible that no marking is performed at the time of the macro definition added for the first time, and when the test passing record of the macro definition in the system is detected, a tested mark is added for the macro definition; and if the macro definition is detected to have the tested mark, determining that the testing mark parameter of the macro definition is changed.
Considering that the macro definition calling process often needs to identify the storage path of the macro definition, the change state of the test marking parameter of the macro definition can be determined according to the storage path of the macro definition. Further, before determining the change state of the test marking parameter defined by the macro according to the macro defined storage path, the method may further include: the macro-defined test verification record recorded by the system can be acquired in real time or at intervals; and storing the macro definition according to the test verification result of the macro definition recorded by the system. For example, different header files may be created as test flags for storing macro definitions that have failed test verification and macro definitions that have passed test verification, respectively. Therefore, whether the macro definition passes the test verification can be determined only by identifying the header file in which the macro definition is stored, and the method is simple and convenient.
It will be appreciated that the above illustrates only a limited number of possible ways of determining the state of change of the parameters of the examination marks defined by the macro, and is not limiting. Since the determination result varies with the setting of the quiz mark parameter and the judgment criterion defined by the macro. The invention aims to ensure the safety and the practicability of the code, particularly, whether the macro definition is tested and verified can be determined through the test marking parameters of the macro definition, the possible risks of a user are prompted under the condition that the macro definition is not tested and verified, the debugging code is used after being tested and verified as much as possible, and the macro definition which is tested and verified can directly respond to a calling request. Therefore, the parameters of the quiz marks can be set by the user or engineer according to actual needs.
And S130, responding the macro definition calling request according to the determination result.
In this embodiment, the determination result generally includes that the parameters of the test mark defined by the macro are not changed or are changed. If the test marking parameters of the macro definition are determined to be changed, it may be stated that the macro definition passes test verification after being added, and the macro definition may be directly called to respond to the corresponding function of the code segment in the macro definition. If it is determined that the test marking parameter of the macro definition does not change, which may indicate that the invoked macro definition does not pass the test verification, a prompt message may be output, so that the user can know the current state of the macro definition in time, and further, whether to perform debugging and test verification may be queried, and if not, a possible risk may be prompted. If the test verification is passed after the debugging, the corresponding functions of the code segments in the macro definition can be directly responded when the macro definition is called again by modifying the test marking parameters.
According to the technical scheme of the embodiment of the invention, when the fact that the first macro definition value to be compiled in the macro definition calling request is inconsistent with the second macro definition value of the pre-stored macro definition is detected, namely the macro definition is called and changed, the macro definition calling request is not directly responded, whether the macro definition is tested or not is determined by determining the change state of the test marking parameter of the macro definition, and then the macro definition calling request is responded according to the determination result, so that the safe calling of the macro definition can be effectively ensured.
Example two
Fig. 2 is a flowchart of a code management method according to a second embodiment of the present invention, as shown in fig. 2, on the basis of the foregoing embodiments, in this embodiment, optionally, the determining the change state of the test flag parameter defined by the macro may include: and determining the change state of the quiz mark parameters defined by the macro according to the storage path defined by the macro.
On the basis of the above technical solution, further, responding to the macro definition invocation request according to the determination result may specifically include: and if the test marking parameters defined by the macro are not changed, outputting prompt information.
The method of the embodiment specifically includes:
s210, obtaining a first macro definition value to be compiled in the macro definition calling request.
And S220, when the first macro definition value is detected to be inconsistent with a second macro definition value of the pre-stored macro definition based on the detection script, determining the change state of the test marking parameter of the macro definition according to the storage path of the macro definition.
In this embodiment, the terminal or the server may store one or more function modules that may be used by the user in advance in a macro definition form, and when the macro definition is called, the change state of the test marking parameter defined by the macro may be determined only by acquiring the storage path defined by the macro. Alternatively, a first header file may be created for storing macro definitions that have failed test validation and a second header file may be created for storing macro definitions that have passed test validation. Specifically, if the macro definition exists in the pre-created first header file, it is determined that the test marking parameters of the macro definition are not changed, that is, the test marking parameters of the macro definition are not changed. And if the macro definition is transferred from the first header file to the second header file, determining that the test marking parameters of the macro definition are changed.
In the code management process, the change state of the test marking parameter of the macro definition can be determined only according to whether the macro definition is stored in the first header file or the second header file, so that whether the macro definition passes the test verification or not can be determined. The macro definition can be directly acquired from the storage path of the macro definition when being called, so that whether the macro definition passes the test verification can be simply and quickly determined without adding extra operation, the safety of the macro definition can be improved by monitoring the quality of the code, and the macro definition calling request of a user can be more efficiently responded.
And S230, if the test marking parameters defined by the macro are not changed, outputting prompt information.
Illustratively, the prompt information may define the current state, i.e., the attributes of itself, etc., of the macro represented by the quiz mark parameters defined by the macro. For example, the macro definition may not be verified by testing, or the macro definition may pass the testing verification. If the macro definition is not tested and verified, a risk prompt can be output to remind a user of the possible risks in direct use. If the user enters the debugging and test verification states, the user can be reminded in real time whether the current debugging passes the test verification or not, and the like. The advantage of setting up like this is that user or engineer can be through the prompt message promptly, directly perceivedly learn the current state of macro definition, promote user experience.
Considering that the macro definition often fails the quality test verification when being added and the system generally records the initial state of the macro definition, if the test marking parameter of the macro definition is not changed, the prompt message can be output, so as to prevent the user from directly calling the macro definition which fails the quality test verification to cause unnecessary damage to the execution device or the terminal and the like under the condition of unconsciousness.
According to the technical scheme of the embodiment, the change state of the test marking parameters defined by the macro is determined through the storage path defined by the macro, whether the macro definition is tested or not can be simply, quickly and effectively determined, and when the test marking parameters defined by the macro are not changed, the prompt information is output, so that a warning can be automatically sent out, a user can be reminded, the state defined by the macro is effectively monitored, the safe calling of the macro definition is ensured, and the code management method is optimized.
Taking an application scenario in which a DVD function is added to a television as an example, a specific flow of a code management method applicable to this embodiment may be stated as follows: the manufacturer or the development engineer a considers that the client may have a requirement of a DVD function module built in the television, and the original code does not support the function, so the engineer a adds the function, and uses the macro definition CVT _ EN _ DVD to include the code segment for realizing the DVD function, and closes the macro definition by default, and the default macro definition value, i.e. the second macro definition value stored in advance, may be 0 or False at this time, so as to ensure that the code is not compiled under the default condition, and the function of other order software is not affected. However, the code segment in the macro definition is not tested by the quality part QA, and the untested macro definition is stored in the first header file Global _ Default _ draft.
Engineer B meets the requirement of client C1 to add a built-in DVD function module in the production software, and engineer B finds that a DVD function module controlled by macro CVT _ EN _ DVD already exists in the existing code, and then directly calls the macro definition CVT _ EN _ DVD when configuring the software, that is, directly opens the macro definition of CVT _ EN _ DVD, and using this function, the first macro definition value to be compiled of the acquired macro definition at this time can be 1 or True.
Since the macro definition is stored in the first header file Global _ Default _ draft.h, when software is recompiled, based on a draft _ check.sh detection script, it is detected that a first macro definition value of CVT _ EN _ DVD of production software to be compiled is inconsistent with a second macro definition value of CVT _ EN _ DVD registered and stored in the Global _ Default _ draft.h in advance, prompt information is output, an automatic alarm is given, and a software engineer B is prompted that the macro definition corresponding to the function is not tested and verified, if the macro definition is used in the production software, QA test verification must be submitted first.
And the engineer B submits the compiled software to special test verification of the DVD module according to the requirement of system prompt information. If a problem is found, the QA test validation requires that the software engineer B continue to modify and continue to submit test validations. After the final test verification is passed, the engineer B or the system automatically registers the macro definition CVT _ EN _ DVD in the Global _ Default _ draft.h file into the macro definition public configuration area, i.e., the second header file Global _ Default _ configuration.h, and deletes the macro definition CVT _ EN _ DVD in the Global _ Default _ draft.h file. If other clients need to use the DVD function, the macro definition is called directly from the Global _ Default _ Config.h.
It should be noted that, since the DVD function block in Global _ Default _ config.h has passed the test, the DVD function block can be directly used regardless of whether the first macro definition value of the macro definition in the macro definition call request is identical to the second macro definition value of the macro definition stored in the second header file (identical to the second macro definition of the macro definition stored in the first header file).
According to the scheme, the quality problem caused by direct use of the production software after different software engineers change unverified software is avoided, closed-loop quality control of software change is achieved through the code management method, code safety is guaranteed, communication cost is reduced, and efficiency is saved.
EXAMPLE III
Fig. 3 is a schematic structural diagram of a code management apparatus according to a third embodiment of the present invention, which may be implemented in a hardware and/or software manner, and generally may be implemented by a terminal and a server in cooperation with each other. As shown in fig. 3, the code management apparatus specifically includes: an acquisition module 310, a change status determination module 320, and a response module 330.
The obtaining module 310 is configured to obtain a first macro definition value to be compiled in the macro definition invoking request; a change state determination module 320, configured to determine a change state of the quiz mark parameter defined by the macro when it is detected that the first macro definition value is inconsistent with a second macro definition value of a pre-stored macro definition based on the detection script; and the response module 330 is configured to respond to the macro definition invoking request according to the determination result.
According to the technical scheme of the embodiment of the invention, when the fact that the first macro definition value to be compiled in the macro definition calling request is inconsistent with the second macro definition value of the pre-stored macro definition is detected, namely the macro definition is called and changed, the macro definition calling request is not directly responded, whether the macro definition is tested or not is determined by determining the change state of the test marking parameter of the macro definition, and then the macro definition calling request is responded according to the determination result, so that the safe calling of the macro definition can be effectively ensured.
On the basis of the above technical solution, the change state determination module may be configured to:
and carrying out non-test marking on the macro definition added for the first time, and if the macro definition is detected to have the non-test marking, determining that the test marking parameters of the macro definition are not changed.
On the basis of the above technical solutions, the change state determination module may be further configured to:
and determining the change state of the quiz mark parameters defined by the macro according to the storage path defined by the macro.
On the basis of the above technical solutions, the change state determination module may be specifically configured to:
and if the macro definition exists in the pre-created first header file, determining that the test marking parameters of the macro definition are unchanged.
On the basis of the above technical solutions, the response module may be configured to:
and if the macro definition is transferred from the first header file to the second header file, determining that the test marking parameters of the macro definition are changed.
On the basis of the above technical solutions, the response module may further be configured to:
and if the test marking parameters defined by the macro change, outputting prompt information.
The code management device and the mobile terminal provided in the above embodiments can execute the code management method provided in any embodiment of the present invention, and have corresponding functional modules and beneficial effects for executing the method. Technical details that are not described in detail in the above embodiments may be referred to a code management method provided in any embodiment of the present invention.
It is to be noted that the foregoing is only illustrative of the preferred embodiments of the present invention and the technical principles employed. It will be understood by those skilled in the art that the present invention is not limited to the particular embodiments described herein, but is capable of various obvious changes, rearrangements and substitutions as will now become apparent to those skilled in the art without departing from the scope of the invention. Therefore, although the present invention has been described in greater detail by the above embodiments, the present invention is not limited to the above embodiments, and may include other equivalent embodiments without departing from the spirit of the present invention, and the scope of the present invention is determined by the scope of the appended claims.
Claims (12)
1. A code management method, comprising:
acquiring a first macro definition value to be compiled in a macro definition call request;
when the first macro definition value is detected to be inconsistent with a second macro definition value of a pre-stored macro definition based on a detection script, determining a change state of a test marking parameter of the macro definition, wherein the change state of the test marking parameter is used for confirming whether the macro definition passes test verification or not; the second macro definition value of the macro definition is an initial value or a default value of the first macro definition value; the first macro definition value includes: defining one or more parameters in the code segment enclosed by the macro, or representing constants of the macro defining the switch state; if the test marking parameters of the macro definition are determined to be changed, determining that the macro definition passes test verification, and directly calling the macro definition;
and responding the macro definition call request according to the determined result.
2. The method of claim 1, wherein determining the change status of the quiz mark parameters defined by the macro comprises:
adding an untested mark to the macro definition added for the first time, and if the untested mark is detected to exist in the macro definition, determining that the test mark parameter of the macro definition is not changed.
3. The method of claim 1, wherein determining the change status of the quiz mark parameters defined by the macro comprises:
and determining the change state of the quiz mark parameters defined by the macro according to the storage path defined by the macro.
4. The method of claim 3, wherein determining the change status of the quiz mark parameters defined by the macro according to the macro-defined storage path comprises:
and if the macro definition exists in the pre-created first header file, determining that the test marking parameters of the macro definition are unchanged.
5. The method of claim 4, wherein responding to the macro definition invocation request according to the determination comprises:
and if the macro definition is transferred from the first header file to the second header file, determining that the test marking parameters of the macro definition are changed.
6. The method according to any of claims 1-4, wherein said responding to the macro definition invocation request based on the determination comprises:
and if the test marking parameters defined by the macro are not changed, outputting prompt information.
7. A code management apparatus, comprising:
the obtaining module is used for obtaining a first macro definition value to be compiled in the macro definition calling request;
a change state determination module, configured to determine a change state of a test marking parameter of the macro definition when it is detected that the first macro definition value is inconsistent with a second macro definition value of a pre-stored macro definition based on a detection script, where the change state of the test marking parameter is used to confirm whether the macro definition passes test verification; the second macro definition value of the macro definition is an initial value or a default value of the first macro definition value; the first macro definition value includes: defining one or more parameters in the code segment enclosed by the macro, or representing constants of the macro defining the switch state; if the test marking parameters of the macro definition are determined to be changed, determining that the macro definition passes test verification, and directly calling the macro definition;
and the response module is used for responding the macro definition call request according to the determination result.
8. The apparatus of claim 7, wherein the change status determination module is configured to:
adding an untested mark to the macro definition added for the first time, and if the untested mark is detected to exist in the macro definition, determining that the test mark parameter of the macro definition is not changed.
9. The apparatus of claim 7, wherein the change status determination module is configured to:
and determining the change state of the quiz mark parameters defined by the macro according to the storage path defined by the macro.
10. The apparatus of claim 9, wherein the change state determination module is specifically configured to:
and if the macro definition exists in the pre-created first header file, determining that the test marking parameters of the macro definition are unchanged.
11. The apparatus of claim 10, wherein the response module is configured to:
and if the macro definition is transferred from the first header file to the second header file, determining that the test marking parameters of the macro definition are changed.
12. The apparatus of any of claims 7-10, wherein the response module is further configured to:
and if the test marking parameters defined by the macro are not changed, outputting prompt information.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710165449.7A CN106940647B (en) | 2017-03-20 | 2017-03-20 | Code management method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710165449.7A CN106940647B (en) | 2017-03-20 | 2017-03-20 | Code management method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN106940647A CN106940647A (en) | 2017-07-11 |
| CN106940647B true CN106940647B (en) | 2020-09-04 |
Family
ID=59463295
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710165449.7A Active CN106940647B (en) | 2017-03-20 | 2017-03-20 | Code management method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN106940647B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109492204A (en) * | 2017-09-12 | 2019-03-19 | 北京国双科技有限公司 | File editing method and device |
| CN110569038B (en) * | 2019-09-06 | 2023-06-09 | 深圳忆联信息系统有限公司 | Random verification parameter design method, device, computer equipment and storage medium |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP1280056A1 (en) * | 2001-07-26 | 2003-01-29 | STMicroelectronics Limited | Generation of debugging information |
| CN101017458A (en) * | 2007-03-02 | 2007-08-15 | 北京邮电大学 | Software safety code analyzer based on static analysis of source code and testing method therefor |
| US20100186005A1 (en) * | 2009-01-20 | 2010-07-22 | Fujitsu Limited | Computer readable recording medium storing verification support program, information processing apparatus and verification support method |
| CN104156314A (en) * | 2014-08-14 | 2014-11-19 | 北京航空航天大学 | Code reuse method applied to test system |
| CN105511977A (en) * | 2015-12-04 | 2016-04-20 | 北京远特科技股份有限公司 | Vehicle-mounted navigation system testing method and device |
-
2017
- 2017-03-20 CN CN201710165449.7A patent/CN106940647B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP1280056A1 (en) * | 2001-07-26 | 2003-01-29 | STMicroelectronics Limited | Generation of debugging information |
| CN101017458A (en) * | 2007-03-02 | 2007-08-15 | 北京邮电大学 | Software safety code analyzer based on static analysis of source code and testing method therefor |
| US20100186005A1 (en) * | 2009-01-20 | 2010-07-22 | Fujitsu Limited | Computer readable recording medium storing verification support program, information processing apparatus and verification support method |
| CN104156314A (en) * | 2014-08-14 | 2014-11-19 | 北京航空航天大学 | Code reuse method applied to test system |
| CN105511977A (en) * | 2015-12-04 | 2016-04-20 | 北京远特科技股份有限公司 | Vehicle-mounted navigation system testing method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN106940647A (en) | 2017-07-11 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107193750B (en) | Script recording method and device | |
| CN107948744B (en) | Interface detection method, interface detection device, and computer-readable storage medium | |
| CN110908909B (en) | Automatic test method, device, storage medium and equipment | |
| CN108134708B (en) | Method and device for monitoring third-party interface | |
| CN110088744B (en) | Database maintenance method and system | |
| CN109165170B (en) | Method and system for automatic request test | |
| CN109218407B (en) | Code management and control method based on log monitoring technology and terminal equipment | |
| CN106126414B (en) | Application software testing method and system | |
| CN110063042B (en) | Database fault response method and terminal thereof | |
| CN115080398A (en) | Automatic interface test system and method | |
| CN106940647B (en) | Code management method and device | |
| CN111400167A (en) | Redfish service compliance verification method, device, equipment and medium | |
| US20230315620A1 (en) | System and Method for Diagnosing a Computing Device in Safe Mode | |
| CN113704117A (en) | Algorithm testing system, method and device | |
| CN107105100B (en) | Method and system for monitoring mobile terminal game | |
| CN109995931B (en) | Method and device for realizing automatic calling | |
| CN112241362A (en) | Test method, test device, server and storage medium | |
| CN105204989A (en) | Mobile terminal, server and system and method for detecting application | |
| CN111736893B (en) | Software package version verification method and related device | |
| CN110569046A (en) | Data processing method, device, equipment and storage medium | |
| CN114154169A (en) | Jenkins and JMeter-based automatic test method and device | |
| CN114625106A (en) | Vehicle diagnosis method and device, electronic equipment and storage medium | |
| CN110198249B (en) | Power distribution automation system testing method and system | |
| CN108845932B (en) | Unit testing method and device of network library, storage medium and terminal | |
| CN110855526A (en) | Method and device for detecting data source connection, storage medium and electronic equipment |
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 |