CN111930579A - Test machine deployment permission verification method and device, computer equipment and storage medium - Google Patents

Test machine deployment permission verification method and device, computer equipment and storage medium Download PDF

Info

Publication number
CN111930579A
CN111930579A CN202010681657.4A CN202010681657A CN111930579A CN 111930579 A CN111930579 A CN 111930579A CN 202010681657 A CN202010681657 A CN 202010681657A CN 111930579 A CN111930579 A CN 111930579A
Authority
CN
China
Prior art keywords
information
testing machine
machine
current testing
script
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
Application number
CN202010681657.4A
Other languages
Chinese (zh)
Inventor
霍开源
王伟良
郭芳芳
蒋菲
石骁
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Shenzhen Union Memory Information System Co Ltd
Original Assignee
Shenzhen Union Memory Information System Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Shenzhen Union Memory Information System Co Ltd filed Critical Shenzhen Union Memory Information System Co Ltd
Priority to CN202010681657.4A priority Critical patent/CN111930579A/en
Publication of CN111930579A publication Critical patent/CN111930579A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/22Detection or location of defective computer hardware by testing during standby operation or during idle time, e.g. start-up testing
    • G06F11/2247Verification or detection of system hardware configuration
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/22Detection or location of defective computer hardware by testing during standby operation or during idle time, e.g. start-up testing
    • G06F11/2205Detection or location of defective computer hardware by testing during standby operation or during idle time, e.g. start-up testing using arrangements specific to the hardware being tested
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/22Detection or location of defective computer hardware by testing during standby operation or during idle time, e.g. start-up testing
    • G06F11/2273Test methods

Landscapes

  • Engineering & Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Hardware Design (AREA)
  • Quality & Reliability (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Debugging And Monitoring (AREA)

Abstract

The application relates to a method and a device for verifying deployment permission of a tester, computer equipment and a storage medium, wherein the method comprises the following steps: before the WINPE is started through a network, a script and a check file for executing the deployment permission check are packaged into the WINPE; after the script and the check file are packaged, starting WINPE from a network and calling the script; the script reads information preset in the verification file in advance, and compares the information with information of a current testing machine to judge whether matching is successful; if the matching is successful, judging that the current testing machine is an authorized machine type and executing subsequent system deployment; if the matching fails, the current testing machine is judged to be an unauthorized machine type, and the current testing machine is forced to enter a dead loop so as to ensure the safety of data. The invention realizes that only authorized models are deployed according to actual requirements in the system deployment process.

Description

Test machine deployment permission verification method and device, computer equipment and storage medium
Technical Field
The invention relates to the technical field of computer testing, in particular to a deployment permission verification method and device of a testing machine, computer equipment and a storage medium.
Background
With the development of computer technology, computers have become the most powerful practical tools for people to generate, and the safety and stability of computers are essential guarantees for people to work with computers, so that the performance of computers needs to be tested in all directions through test scripts before the computers leave factories.
At present, in the prior art, in a system deployment process, a tester is generally deployed directly through a network, and in the deployment process through the network, some unauthorized testers may perform system deployment or some faulty operation deployment may occur on the testers, which may cause deployment errors and further cause some unnecessary losses.
Disclosure of Invention
Therefore, it is necessary to provide a method, an apparatus, a computer device, and a storage medium for verifying a deployment permission of a tester that can implement a deployment service only for authorized models, in order to solve the above technical problems.
A method for verifying deployment permission of a testing machine, the method comprising:
before the WINPE is started through a network, a script and a check file for executing the deployment permission check are packaged into the WINPE;
after the script and the check file are packaged, starting WINPE from a network and calling the script;
the script reads information preset in the verification file in advance, and compares the information with information of a current testing machine to judge whether matching is successful;
if the matching is successful, judging that the current testing machine is an authorized machine type and executing subsequent system deployment;
if the matching fails, the current testing machine is judged to be an unauthorized machine type, and the current testing machine is forced to enter a dead loop so as to ensure the safety of data.
In one embodiment, the step of reading information preset in the verification file by the script, and comparing the information with information of the current test machine to determine whether matching is successful includes:
the script reads information preset in advance in the verification file, wherein the information comprises a machine type, a CPU (Central processing Unit) type, a hard disk type and a machine unique identification code;
sequentially comparing the information with information corresponding to the current testing machine one by one;
if all the information is consistent, judging the machine type of the current testing machine as an authorized machine type;
and if the information is inconsistent, judging that the model of the current testing machine is an unauthorized model.
In one embodiment, after the step of determining that the model of the current test machine is an unauthorized model if there is inconsistency in information, the method further includes:
and if the model of the current testing machine is judged to be an unauthorized model, a bounce prompt window is used for reminding a user and forcing the current testing machine to enter a dead cycle until the user forcibly restarts to ensure the safety of data.
In one embodiment, after the step of determining that the model of the current testing machine is the authorized model if all the information is consistent, the method further includes:
and if the model of the current testing machine is judged to be an authorized model, the testing system is led into the solid state disk and started from the solid state disk.
A deployment authority checking apparatus of a tester, the apparatus comprising:
the packaging module is used for packaging a script and a check file for executing the deployment permission check into the WINPE before the WINPE is started through a network;
the starting module is used for starting WINPE from a network and calling the script after the script and the check file are packaged;
the comparison module is used for reading information preset in the check file by the script and comparing the information with the information of the current testing machine to judge whether the matching is successful or not;
the first execution module is used for judging that the current testing machine is an authorized machine type and executing subsequent system deployment if the matching is successful;
and the second execution module is used for judging that the current testing machine is an unauthorized machine type and forcing the current testing machine to enter a dead loop to ensure the safety of data if the matching fails.
In one embodiment, the alignment module is further configured to:
the script reads information preset in advance in the verification file, wherein the information comprises a machine type, a CPU (Central processing Unit) type, a hard disk type and a machine unique identification code;
sequentially comparing the information with information corresponding to the current testing machine one by one;
if all the information is consistent, judging the machine type of the current testing machine as an authorized machine type;
and if the information is inconsistent, judging that the model of the current testing machine is an unauthorized model.
In one embodiment, the second execution module is further configured to:
and if the model of the current testing machine is judged to be an unauthorized model, the user is reminded of the bounce prompt window and the current testing machine is forced to enter a dead cycle until the user is forced to restart so as to ensure the safety of data.
In one embodiment, the first execution module is further configured to:
and if the model of the current testing machine is judged to be an authorized model, the testing system is led into the solid state disk and started from the solid state disk.
A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the steps of any of the above methods when executing the computer program.
A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the steps of any of the methods described above.
Before the WINPE is started through a network, a script and a check file for executing the deployment permission check are packaged into the WINPE; after the script and the check file are packaged, starting WINPE from a network and calling the script; the script reads information preset in the verification file in advance, and compares the information with information of a current testing machine to judge whether matching is successful; if the matching is successful, judging that the current testing machine is an authorized machine type and executing subsequent system deployment; if the matching fails, the current testing machine is judged to be an unauthorized machine type, and the current testing machine is forced to enter a dead loop so as to ensure the safety of data. In the invention, the customized script is added in the process of system deployment through the network, and whether the current testing machine is authorized or not can be checked according to the check file by running the customized script, so that only authorized machine types are deployed according to actual requirements in the system deployment process, the unauthorized testing machines are prevented from being deployed, and the loss caused by wrong deployment is effectively reduced.
Drawings
FIG. 1 is a schematic flow chart illustrating a test machine system deployment in the prior art;
FIG. 2 is a schematic flow chart of the test machine system deployment according to the present invention;
FIG. 3 is a flowchart illustrating a method for verifying deployment permissions of a tester in an embodiment;
FIG. 4 is a flowchart illustrating a method for verifying deployment permission of a tester in another embodiment;
FIG. 5 is a block diagram showing the structure of a device for checking the deployment authority of a tester in one embodiment;
FIG. 6 is a diagram illustrating an internal structure of a computer device according to an embodiment.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the present application is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application.
At present, in the prior art, in a system deployment process, the system deployment of the tester is generally performed directly through a network, and specifically, the system deployment process shown in fig. 1 may be referred to. Firstly, network starts WINPE, namely Windows PE (Windows Preinstallation Environment), then the system is led into the solid state disk and started from the solid state disk, and finally the system is modified and tested. Therefore, in the existing system deployment process, some unauthorized testers may perform system deployment or some faulty operation deployment on the testers, which may cause deployment errors and further cause some unnecessary losses.
Based on this, the invention provides a method for verifying deployment permission of a test machine, and specifically, the method can refer to a system deployment flow shown in fig. 2.
In one embodiment, as shown in fig. 3, a method for verifying deployment permission of a tester is provided, where the method includes:
step 302, before the WINPE is started through the network, a script for executing the deployment permission check and a check file are packed into the WINPE;
step 304, after the script and the check file are packaged, starting WINPE from the network and calling the script;
step 306, reading information preset in advance in the verification file by the script, and comparing the information with the information of the current testing machine to judge whether the matching is successful;
step 308, if the matching is successful, judging that the current testing machine is an authorized machine type and executing subsequent system deployment;
and 310, if the matching fails, judging that the current testing machine is an unauthorized machine type and forcing the current testing machine to enter a dead loop so as to ensure the safety of data.
In this embodiment, a method for verifying deployment permission of a test machine is provided, where a deployment permission check is added in a system deployment process, and a machine type that does not meet a rule will not be authorized to be deployed, and a specific implementation process includes the following steps:
firstly, before the WINPE network is started, a script to be executed and a check file are packaged into the WINPE, and specifically, a configuration file can be modified according to actual needs. Corresponding identification information such as machine type, CPU type, hard disk type or machine global unique identification code can be set in the check file in advance.
Next, WINPE is started from the network, at which point the required program or file is in memory. After WINPE starts, the packaged script is called, the script can read information such as the type, the CPU type, the hard disk type or the global unique identification code of the machine and the like which are set in advance in the check file, and then the information is compared with the information of the testing machine.
If the comparison is successful, the authorization is successful and the subsequent steps of system deployment are executed. If the comparison fails, if the information, such as the model, the CPU model, the hard disk model, the global unique identification code of the machine, is found to be inconsistent, the current testing machine is judged to be an unauthorized model and forced to enter a dead cycle, and at the moment, the deployment system does not operate the computer hard disk for tasks, so that the data security is ensured.
In this embodiment, before the WINPE is started through a network, a script for executing deployment permission check and a check file are packed into the WINPE; after the script and the check file are packaged, starting WINPE from a network and calling the script; the script reads information preset in the verification file in advance, and compares the information with information of a current testing machine to judge whether matching is successful; if the matching is successful, judging that the current testing machine is an authorized machine type and executing subsequent system deployment; if the matching fails, the current testing machine is judged to be an unauthorized machine type, and the current testing machine is forced to enter a dead loop so as to ensure the safety of data. According to the scheme, the customized script is added in the process of system deployment through the network, whether the current testing machine is authorized or not can be checked according to the check file by running the customized script, the fact that only authorized machine types are deployed according to actual requirements in the process of system deployment is achieved, deployment of some unauthorized testing machines is avoided, and loss caused by wrong deployment is effectively reduced.
In an embodiment, as shown in fig. 4, a deployment permission verification method for a tester is provided, in which a script reads information preset in a verification file in advance, and compares the information with information of a current tester to determine whether matching is successful includes:
step 402, reading information preset in advance in a verification file by a script, wherein the information comprises a machine type, a CPU (Central processing Unit) type, a hard disk type and a machine unique identification code;
step 404, comparing the information with the information corresponding to the current testing machine one by one in sequence;
step 406, if all the information is consistent, judging the model of the current testing machine to be an authorized model;
and step 408, if the information is inconsistent, judging that the model of the current testing machine is an unauthorized model.
In one embodiment, after the step of determining that the model of the current test machine is an unauthorized model if there is inconsistency in information, the method further includes:
and if the model of the current testing machine is judged to be an unauthorized model, a bounce prompt window is used for reminding a user and forcing the current testing machine to enter a dead cycle until the user forcibly restarts to ensure the safety of data.
In one embodiment, if all the information is consistent, the step of determining that the model of the current test machine is an authorized model further includes:
and if the model of the current testing machine is judged to be the authorized model, the testing system is led into the solid state disk and is started from the solid state disk.
In this embodiment, a complete method for verifying deployment permission of a tester is provided, where the method mainly includes:
1. before the WINPE network is started, the script to be executed and the check file are packaged into the WINPE, and the method can be realized by modifying the configuration file.
2. WINPE is started from the network, and the required program or file is in the memory at this time.
3. After WINPE starts, firstly, the packaged scripts are called, the scripts can read information (such as the type, the CPU type, the hard disk type, the unique global identification code of the machine and the like) set in advance in the check file, then the information is compared with the information of the machine, if the comparison is successful, authorization is successful, the next step is continued, otherwise, a popup prompt window is used for prompting a user, and the computer is in a dead cycle until the user forcibly restarts the computer, at the moment, the deployment system does not perform task operation on the hard disk of the computer, and the safety of data is guaranteed.
4. And importing the test system into the solid state disk.
5. The test system is started from the solid state disk.
It should be understood that although the various steps in the flow charts of fig. 2-4 are shown in order as indicated by the arrows, the steps are not necessarily performed in order as indicated by the arrows. The steps are not performed in the exact order shown and described, and may be performed in other orders, unless explicitly stated otherwise. Moreover, at least some of the steps in fig. 2-4 may include multiple sub-steps or multiple stages that are not necessarily performed at the same time, but may be performed at different times, and the order of performance of the sub-steps or stages is not necessarily sequential, but may be performed in turn or alternating with other steps or at least some of the sub-steps or stages of other steps.
In one embodiment, as shown in fig. 5, there is provided a deployment authority checking apparatus 500 of a tester, the apparatus including:
a packaging module 501, configured to package a script and a check file for performing deployment permission check into a WINPE before the WINPE is started over a network;
a starting module 502, configured to start the WINPE from the network and call the script after the script and the check file are packaged;
a comparison module 503, configured to read, by the script, information preset in the check file in advance, and compare the information with information of a current test machine to determine whether matching is successful;
a first executing module 504, configured to determine that the current testing machine is an authorized machine type and execute subsequent system deployment if matching is successful;
and a second executing module 505, configured to determine that the current test machine is an unauthorized machine type if the matching fails, and force the current test machine to enter a dead loop to ensure data security.
In one embodiment, the alignment module 503 is further configured to:
the script reads information preset in advance in the verification file, wherein the information comprises a machine type, a CPU (Central processing Unit) type, a hard disk type and a machine unique identification code;
sequentially comparing the information with information corresponding to the current testing machine one by one;
if all the information is consistent, judging the machine type of the current testing machine as an authorized machine type;
and if the information is inconsistent, judging that the model of the current testing machine is an unauthorized model.
In one embodiment, the second execution module 505 is further configured to:
and if the model of the current testing machine is judged to be an unauthorized model, the user is reminded of the bounce prompt window and the current testing machine is forced to enter a dead cycle until the user is forced to restart so as to ensure the safety of data.
In one embodiment, the first execution module 504 is further configured to:
and if the model of the current testing machine is judged to be an authorized model, the testing system is led into the solid state disk and started from the solid state disk.
For specific limitations of the deployment permission verification device of the tester, reference may be made to the above limitations of the deployment permission verification method of the tester, and details are not described here.
In one embodiment, a computer device is provided, the internal structure of which may be as shown in FIG. 6. The computer apparatus includes a processor, a memory, and a network interface connected by a device bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device comprises a nonvolatile storage medium and an internal memory. The nonvolatile storage medium stores an operating device, a computer program, and a database. The internal memory provides an environment for the operation device in the nonvolatile storage medium and the execution of the computer program. The network interface of the computer device is used for communicating with an external terminal through a network connection. The computer program is executed by a processor to implement a method for testing machine deployment authority verification.
Those skilled in the art will appreciate that the architecture shown in fig. 6 is merely a block diagram of some of the structures associated with the disclosed aspects and is not intended to limit the computing devices to which the disclosed aspects apply, as particular computing devices may include more or less components than those shown, or may combine certain components, or have a different arrangement of components.
In one embodiment, a computer device is provided, comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the steps of the above method embodiments when executing the computer program.
In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the above respective method embodiments.
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by hardware instructions of a computer program, which can be stored in a non-volatile computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. Any reference to memory, storage, database, or other medium used in the embodiments provided herein may include non-volatile and/or volatile memory, among others. Non-volatile memory can include read-only memory (ROM), Programmable ROM (PROM), Electrically Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), or flash memory. Volatile memory can include Random Access Memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms such as Static RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDRSDRAM), Enhanced SDRAM (ESDRAM), Synchronous Link DRAM (SLDRAM), Rambus Direct RAM (RDRAM), direct bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).
The technical features of the above embodiments can be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the above embodiments are not described, but should be considered as the scope of the present specification as long as there is no contradiction between the combinations of the technical features.
The above-mentioned embodiments only express several embodiments of the present application, and the description thereof is more specific and detailed, but not construed as limiting the scope of the invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the concept of the present application, which falls within the scope of protection of the present application. Therefore, the protection scope of the present patent shall be subject to the appended claims.

Claims (10)

1. A deployment permission verification method of a testing machine is characterized by comprising the following steps:
before the WINPE is started through a network, a script and a check file for executing the deployment permission check are packaged into the WINPE;
after the script and the check file are packaged, starting WINPE from a network and calling the script;
the script reads information preset in the verification file in advance, and compares the information with information of a current testing machine to judge whether matching is successful;
if the matching is successful, judging that the current testing machine is an authorized machine type and executing subsequent system deployment;
if the matching fails, the current testing machine is judged to be an unauthorized machine type, and the current testing machine is forced to enter a dead loop so as to ensure the safety of data.
2. The method for verifying the deployment permission of the test machine according to claim 1, wherein the step of reading information preset in advance in the verification file by the script and comparing the information with the information of the current test machine to judge whether the matching is successful comprises:
the script reads information preset in advance in the verification file, wherein the information comprises a machine type, a CPU (Central processing Unit) type, a hard disk type and a machine unique identification code;
sequentially comparing the information with information corresponding to the current testing machine one by one;
if all the information is consistent, judging the machine type of the current testing machine as an authorized machine type;
and if the information is inconsistent, judging that the model of the current testing machine is an unauthorized model.
3. The method for verifying the deployment permission of the test machine according to claim 2, wherein after the step of determining that the current model of the test machine is an unauthorized model if the information is inconsistent, the method further comprises:
and if the model of the current testing machine is judged to be an unauthorized model, a bounce prompt window is used for reminding a user and forcing the current testing machine to enter a dead cycle until the user forcibly restarts to ensure the safety of data.
4. The method for verifying the deployment permission of the test machine according to claim 2, wherein after the step of determining that the current machine type of the test machine is an authorized machine type if all the information is consistent, the method further comprises:
and if the model of the current testing machine is judged to be an authorized model, the testing system is led into the solid state disk and started from the solid state disk.
5. A deployment authority verification apparatus for a tester, the apparatus comprising:
the packaging module is used for packaging a script and a check file for executing the deployment permission check into the WINPE before the WINPE is started through a network;
the starting module is used for starting WINPE from a network and calling the script after the script and the check file are packaged;
the comparison module is used for reading information preset in the check file by the script and comparing the information with the information of the current testing machine to judge whether the matching is successful or not;
the first execution module is used for judging that the current testing machine is an authorized machine type and executing subsequent system deployment if the matching is successful;
and the second execution module is used for judging that the current testing machine is an unauthorized machine type and forcing the current testing machine to enter a dead loop to ensure the safety of data if the matching fails.
6. The deployment permission verification apparatus of a testing machine according to claim 5, wherein the comparison module is further configured to:
the script reads information preset in advance in the verification file, wherein the information comprises a machine type, a CPU (Central processing Unit) type, a hard disk type and a machine unique identification code;
sequentially comparing the information with information corresponding to the current testing machine one by one;
if all the information is consistent, judging the machine type of the current testing machine as an authorized machine type;
and if the information is inconsistent, judging that the model of the current testing machine is an unauthorized model.
7. The deployment permission verification apparatus of a testing machine according to claim 6, wherein the second execution module is further configured to:
and if the model of the current testing machine is judged to be an unauthorized model, the user is reminded of the bounce prompt window and the current testing machine is forced to enter a dead cycle until the user is forced to restart so as to ensure the safety of data.
8. The deployment permission verification apparatus of a testing machine according to claim 6, wherein the first execution module is further configured to:
and if the model of the current testing machine is judged to be an authorized model, the testing system is led into the solid state disk and started from the solid state disk.
9. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the steps of the method of any of claims 1 to 4 are implemented when the computer program is executed by the processor.
10. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the method of any one of claims 1 to 4.
CN202010681657.4A 2020-07-15 2020-07-15 Test machine deployment permission verification method and device, computer equipment and storage medium Pending CN111930579A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202010681657.4A CN111930579A (en) 2020-07-15 2020-07-15 Test machine deployment permission verification method and device, computer equipment and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202010681657.4A CN111930579A (en) 2020-07-15 2020-07-15 Test machine deployment permission verification method and device, computer equipment and storage medium

Publications (1)

Publication Number Publication Date
CN111930579A true CN111930579A (en) 2020-11-13

Family

ID=73313756

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202010681657.4A Pending CN111930579A (en) 2020-07-15 2020-07-15 Test machine deployment permission verification method and device, computer equipment and storage medium

Country Status (1)

Country Link
CN (1) CN111930579A (en)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112255531A (en) * 2020-12-23 2021-01-22 上海伟测半导体科技股份有限公司 Test machine matching system and matching method thereof
CN112987689A (en) * 2021-02-24 2021-06-18 上海东普信息科技有限公司 Safe starting method, device, equipment and storage medium of unmanned aerial vehicle

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112255531A (en) * 2020-12-23 2021-01-22 上海伟测半导体科技股份有限公司 Test machine matching system and matching method thereof
CN112987689A (en) * 2021-02-24 2021-06-18 上海东普信息科技有限公司 Safe starting method, device, equipment and storage medium of unmanned aerial vehicle

Similar Documents

Publication Publication Date Title
CN109032611B (en) Script deployment method and device, computer equipment and storage medium
CN110928653B (en) Cross-cluster task execution method and device, computer equipment and storage medium
CN110704304B (en) Application program testing method and device, storage medium and server
CN109669859B (en) Service testing method, device, computer equipment and storage medium
CN111930579A (en) Test machine deployment permission verification method and device, computer equipment and storage medium
CN109408261B (en) Application program crash processing method and device, computer equipment and storage medium
CN112395202B (en) Interface automation test method and device, computer equipment and storage medium
CN109324961B (en) System automatic test method, device, computer equipment and storage medium
CN110704312A (en) Pressure testing method and device, computer equipment and storage medium
CN111258591A (en) Program deployment task execution method and device, computer equipment and storage medium
CN113282513B (en) Interface test case generation method and device, computer equipment and storage medium
CN112540916A (en) Automatic rerun method and device for failed case, computer equipment and storage medium
CN111277476A (en) Gateway controller function verification method, gateway controller function verification device, computer equipment and storage medium
CN110309057B (en) Automatic script-based flow project testing method and related equipment
CN115328814B (en) Fault injection method, device, equipment and storage medium based on mirror pair
CN109753788B (en) Integrity checking method and computer readable storage medium during kernel operation
CN115659296A (en) File verification method, device and equipment and readable storage medium
CN111985010A (en) Interception verification method and device for notebook hard disk, computer equipment and storage medium
CN114553764B (en) Automobile gateway route configuration system
CN114880179A (en) Server virtualization pressure testing method, device, equipment and storage medium
CN113760623A (en) Method and device for testing TCG (trusted computing group) protocol function of solid state disk and computer equipment
CN111597101B (en) SDK access state detection method, computer equipment and computer readable storage medium
CN112015648A (en) Test method, device, computer equipment and medium based on automation script
CN112817611B (en) Interception method and device for system test abnormal environment, computer equipment and storage medium
CN113407438B (en) Module testing method, computer device, and storage medium

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