WO2019178967A1 - Procédé et appareil de test de contrainte basés sur jmeter, et dispositif et support de stockage - Google Patents

Procédé et appareil de test de contrainte basés sur jmeter, et dispositif et support de stockage Download PDF

Info

Publication number
WO2019178967A1
WO2019178967A1 PCT/CN2018/092636 CN2018092636W WO2019178967A1 WO 2019178967 A1 WO2019178967 A1 WO 2019178967A1 CN 2018092636 W CN2018092636 W CN 2018092636W WO 2019178967 A1 WO2019178967 A1 WO 2019178967A1
Authority
WO
WIPO (PCT)
Prior art keywords
target
custom function
stress test
function
original data
Prior art date
Application number
PCT/CN2018/092636
Other languages
English (en)
Chinese (zh)
Inventor
蔡良
Original Assignee
平安科技（深圳）有限公司
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 平安科技（深圳）有限公司 filed Critical 平安科技（深圳）有限公司
Publication of WO2019178967A1 publication Critical patent/WO2019178967A1/fr

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/36—Preventing errors by testing or debugging software
    • G06F11/3668—Software testing
    • G06F11/3672—Test management
    • G06F11/3684—Test management for test design, e.g. generating new test cases
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/36—Preventing errors by testing or debugging software
    • G06F11/3668—Software testing
    • G06F11/3672—Test management
    • G06F11/3688—Test management for test execution, e.g. scheduling of test suites

Definitions

  • the present application relates to the field of software testing, and in particular, to a Jmeter-based stress testing method, apparatus, device, and storage medium.
  • Jmeter is one of the more highly recommended stress testing tools. Jmeter can be used to simulate large loads on servers, networks, or objects, testing their strength from different stress classes to analyze overall performance. When using Jmeter for stress testing, it is usually necessary to write a program for auxiliary testing.
  • the main programming methods are BeanShell and JSR223 scripts (Groovy and Javascript). However, no matter how it is programmed, there is often a system crash in stress testing. Traditionally, it is believed that due to memory leaks in BeanShell's Interpreter, conventional methods cannot support system crashes caused by prolonged stress tests.
  • the embodiment of the present application provides a JMET-based stress testing method, apparatus, device, and storage medium to solve the problem that the terminal/system throughput rate is not high during the stress testing process.
  • an embodiment of the present application provides a JMET-based stress testing method, including:
  • the target stress test request including at least one original data identifier
  • the embodiment of the present application provides a Jmeter-based pressure testing device, including:
  • a target stress test request obtaining module configured to acquire a target stress test request, where the target stress test request includes at least one original data identifier
  • a target custom function obtaining module configured to acquire a corresponding target custom function based on at least one of the original data identifiers, wherein the target custom function is a function that is not encapsulated by a class;
  • a target custom function encapsulation module configured to encapsulate the target custom function into a BeanShell script file
  • An initialization module configured to initialize the BeanShell script file
  • the stress test module is used to invoke the target custom function encapsulated in the BeanShell script file for stress testing.
  • an embodiment of the present application provides a computer device, including a memory, a processor, and computer readable instructions stored in the memory and executable on the processor, where the processor executes the computer The following steps are implemented when reading the instruction:
  • the target stress test request including at least one original data identifier
  • the embodiment of the present application provides one or more non-volatile readable storage media storing computer readable instructions, when the computer readable instructions are executed by one or more processors, such that the one or Multiple processors perform the following steps:
  • the target stress test request including at least one original data identifier
  • Embodiment 1 is a flow chart of a Jmeter-based stress testing method in Embodiment 1 of the present application;
  • step S20 of FIG. 1 is a flow chart of a specific embodiment of step S20 of FIG. 1;
  • FIG. 3 is a flow chart of a specific embodiment of step S30 of Figure 1;
  • step S31 in FIG. 3 is a flow chart of a specific embodiment of step S31 in FIG. 3;
  • FIG. 5 is a flow chart of a specific embodiment of step S50 of Figure 1;
  • FIG. 6 is a schematic diagram of a Jmeter-based pressure testing device in Embodiment 2 of the present application.
  • Figure 7 is a schematic diagram of a computer device in Embodiment 4 of the present application.
  • Jmeter is a Java-based stress testing tool developed by the Apache organization for stress testing software.
  • Jmeter can be used to test static and dynamic resources such as static files, Java servlets, CGI scripts, Java objects, databases or FTP servers.
  • Jmeter can be used to simulate large loads on servers, networks, or objects, testing their strength from different stress classes to analyze overall performance.
  • Fig. 1 shows a flow chart of a Jmeter-based stress test method in this embodiment.
  • the Jmeter-based stress test method can be applied to various terminals or systems to solve the problem that the terminal/system throughput rate is not high during the stress test.
  • the Jmeter-based stress test method includes the following steps:
  • S10 Acquire a target stress test request, where the target stress test request includes at least one original data identifier.
  • the stress test is a test process that simulates the software and hardware environment of the actual application and the system load of the user's use process, and runs the test software for a long time or a large load to test the performance, reliability or stability of the system under test.
  • a target stress test request is a request for initiation of a stress test.
  • the original data identifier refers to an identifier that distinguishes the data type of the original data that needs to be imported in the stress test.
  • the data type of the original data may be a GPS message, a CAN message, or an HTTP message.
  • the original data identifier assigns different identifiers to the original data according to the type of the original data.
  • S20 Acquire a corresponding target custom function based on the at least one original data identifier, where the target custom function is a function that is not encapsulated by the class.
  • On-Board Diagnostic is a mobile device with communication capabilities.
  • the OBD is installed in the car, and can collect various data in the driving process of the car in real time, and send it to the background through the communication module.
  • the computing platform in the background will calculate various data of the car (such as fuel consumption information, battery voltage, intake pipe temperature, current The vehicle speed, engine water temperature, engine speed, etc. are calculated.
  • the data packets sent by OBD to the background mainly include: time point, latitude and longitude, speed, current fuel consumption and current mileage.
  • OBD sends packets of the car's driving process through the TCP protocol, so it will contain multiple data packets in one flight mileage, and the time of each data packet increases linearly, and its latitude, longitude, speed and fuel consumption need to change dynamically. Therefore, time, latitude, longitude, latitude, speed, fuel consumption and mileage need to be programmed during the stress test of the Internet of Vehicles.
  • a custom function for generating data such as time point, latitude and longitude data, speed, mileage, fuel consumption, etc. is needed to pass in time point, latitude and longitude, mileage, fuel consumption and the like according to the standard message format, and then call the corresponding java program. Synthesize hexadecimal transmission messages.
  • the corresponding custom function needs to be written according to the data type of the original data to ensure that the original data can be smoothly imported into the Jmeter test tool.
  • the corresponding target custom function is obtained based on at least one original data identifier in the target stress test request.
  • the number of the original data identifiers is consistent with the number of categories of the data types of the original data in the target stress test request.
  • a corresponding custom function has been written according to the commonly used or already tested data type, and is saved in the corresponding terminal. Therefore, in this step, at least one original data identifier in the target stress test request may be directly obtained to obtain a corresponding target custom function.
  • the target custom function is specifically a function that is not encapsulated by a class.
  • Class encapsulation refers to encapsulating data and operations into an organic whole. Since private members in the class are hidden and only provide a limited interface to the outside, internal cohesion and low coupling with the outside can be guaranteed. Users don't have to know the specific implementation details, but just use the external interface to use the members of the class with specific access rights, which can enhance security and simplify programming.
  • the target custom function at this step is a function that is not encapsulated by the class.
  • BeanShell is a small and free JAVA source code interpreter that supports object-oriented scripting language features. It can also be embedded in JAVA source code. It can dynamically execute JAVA source code and extend some features of the scripting language.
  • BeanShell will interpret the scripted function (BSHMethod) into the cache cache, which is stored in NameSpace.methods.
  • NameSpace.methods is a HashTable object. For function names (without parameters, return values), value is a Vector list (value is a list, because Java has overloaded functions), and Vector is a BSHMethod object.
  • BeanShell interprets the data type (Scripted Class, BSHType) in the script and puts it into the cache, which is stored in NameSpace.classManager.listeners (class path listener list, because the class needs to search in the class path), listeners are a The Vector list, the BSHType object wrapped in the WeakReference in the Vector, when a script containing the function is executed repeatedly using a unique interpreter, it will continuously store the data type BSHType referenced by the function to the Vector list represented by the listeners, which will also cause Memory leaks.
  • BSHType scripted Class
  • listeners are a The Vector list, the BSHType object wrapped in the WeakReference in the Vector, when a script containing the function is executed repeatedly using a unique interpreter, it will continuously store the data type BSHType referenced by the function to the Vector list represented by the listeners, which will also cause Memory leaks.
  • the same function as the java class can be implemented by using method declarations and methods in the BeanShell script file, and the methods in the BeanShell script file can have dynamic (loose) parameters and return types. Therefore, in this step, you choose to encapsulate the target custom function into a BeanShell script file.
  • the BeanShell script file is initialized. Specifically, the pre-processor in Jmeter can be used to initialize the BeanShell script file.
  • BeanShell.PreProcessor is a preprocessor in Jmeter that executes an algorithm and stores the result in a parameter.
  • the target custom function in the BeanShell script file can be interpreted in advance.
  • the BeanShell script file can be initialized in the jmeter.properties file.
  • the initialization of the BeanShell script file is as follows:
  • Beanshell.preprocessor.init XX/YY/ZZ/chushihua.bsh;
  • the BeanShell script file is initialized. In this way, in the subsequent stress test process, the required target custom function can be directly called directly, that is, the technical effect of the repeated interpretation can be achieved, and the memory leakage is not easily caused, thereby improving the throughput of the terminal/system. rate.
  • BeanShell script file After the BeanShell script file is initialized, you can call the target custom function encapsulated in the BeanShell script file for stress testing in the corresponding interface.
  • the target custom function encapsulated in the BeanShell script file is invoked for stress testing, and the stress test is performed by calling a corresponding target custom function encapsulated in the BeanShell script file based on the test parameters.
  • the test parameters refer to the parameters that need to be tested in the stress test project. Different test parameters will be imported through the corresponding target custom function to select the corresponding raw data. In different stress test items or types, the test methods may vary due to different test parameters or test requirements. Therefore, during the stress test, not all target custom functions need to be called. In this step, based on the test parameters, the required target custom function is called from the target custom function encapsulated in the BeanShell script file for stress testing. Since the target custom function has been explained in the initialization of the script file, even if the target custom function is called multiple times during the stress test, the target custom function will not be interpreted repeatedly, thus avoiding the memory. Give way.
  • the corresponding target custom function is obtained based on the original data identifier in the target stress test request, and the function writing is not required to be repeated, thereby improving the efficiency of the test.
  • the target custom function is a function that is not encapsulated by the class, and the target custom function is encapsulated into a BeanShell script file, and the BeanShell script file is initialized to ensure that the required target can be directly in the subsequent stress test process.
  • the custom function can be called, and the effect of repeated interpretation and repeated calling can be realized, and the throughput of the terminal/system is improved under the premise of avoiding thread blocking.
  • the corresponding target custom function is obtained based on the at least one original data identifier, as shown in FIG. 2, including the following steps:
  • the custom function list is a table for associating data identifiers and custom functions.
  • the list of custom functions includes data identifiers and custom functions (as shown in Table 1). After obtaining the original data identifier, the data identifier corresponding to the original data identifier is queried in the custom function list based on the original data identifier, so that the corresponding custom function is obtained as the target custom function.
  • the corresponding custom function cannot be obtained in the custom function list, indicating that the custom function corresponding to the original data identifier is not stored in the terminal/system. For example (see Table 1): If the original data in the target stress test request is identified as B, C, and D. For the original data identifiers B and C, the corresponding target custom functions Y and Z can be obtained in the list of custom functions. For the original data identifier D, there is no corresponding custom function in the custom function list.
  • the terminal/system will send a prompt message to remind the user that there is no corresponding custom function in the terminal/system for the original data identifier.
  • the prompt message includes an original data identifier of the corresponding custom function that is not obtained in the custom function list, so as to better remind the user.
  • the user After seeing the prompt message sent by the terminal, the user needs to write a corresponding new custom function according to the original data identifier. After the system obtains the newly added custom function, the new custom function is used as the corresponding The target custom function for the raw data identification.
  • the corresponding target custom function is obtained through the custom function list, the data acquisition efficiency is improved, and when there is no corresponding custom function, a prompt message is sent to guide the user to write a corresponding new custom. Function to ensure the smooth progress of the stress test.
  • the Jmeter-based stress test method further includes: adding a new custom function and corresponding original data identifier. Associate and save to a list of custom functions.
  • the newly added custom function is associated with the corresponding original data identifier, and saved to the custom function list to ensure real-time update of the custom function list.
  • the corresponding target custom function can be directly obtained, thereby improving the efficiency of the stress test.
  • the target custom function is packaged into a BeanShell script file, as shown in FIG. 3, including the following steps:
  • S31 Acquire an existing stress test item, and obtain an average number of calls per target custom function based on the existing stress test item.
  • the existing stress test project refers to the stress test project that has been completed.
  • the number of calls for each custom function is different, so you can get the target custom function by querying the call of the corresponding custom function in the existing stress test project. The number of calls.
  • the average number of calls per target custom function can be obtained by obtaining the number of calls of each target custom function in each existing stress test item and summing the number of these calls. .
  • S32 Encapsulate the target custom function with the average number of calls greater than the preset number into a BeanShell script file.
  • a preset number of times can be set to determine which of the custom functions used in the existing stress test items, which custom functions have an average number of calls in the existing stress test items greater than a preset number of times, and this part of the custom function
  • the target custom function is encapsulated into a BeanShell script file.
  • the preset number of times can be set according to historical test results or actual needs.
  • the average number of calls of each target custom function is obtained by obtaining and calculating the number of calls of each target custom function in the existing stress test item, and then the average number of calls is greater than the preset number of times.
  • the target custom function is packaged into a BeanShell script file, which reduces the burden on the terminal/system and further improves the throughput.
  • the target stress test request also includes a target stress test type.
  • the target stress test type refers to the test type corresponding to the target stress test request.
  • an existing stress test item is obtained, including: obtaining an existing stress test item of the same type of stress test item as the target stress test.
  • the stress test project can be divided into different types according to different test conditions and test requirements.
  • the test process of the same type of stress test project is relatively similar.
  • the accuracy of the data is improved by obtaining the existing stress test items of the same type as the target stress test type and obtaining the average number of calls per target custom function based on the existing stress test items of the same type as the target stress test type.
  • the average number of calls of the target custom function is calculated by acquiring an existing pressure test item having the same type as the target stress test in the existing stress test item, thereby ensuring the accuracy of the data.
  • the existing stress test items include existing stress test types.
  • existing stress test items can be classified according to different types, and different types of existing stress test items can be distinguished by existing stress test types.
  • the average number of calls per target custom function is counted based on the existing stress test item, as shown in FIG. 4, including the following steps:
  • the number of calls of each target custom function in each existing stress test item is obtained by querying the call of the corresponding custom function in the existing stress test item.
  • S312 Set a corresponding weight for each existing stress test item based on the correlation between the existing stress test type and the target stress test type.
  • the stress test project can be divided into different types according to different test conditions and test requirements.
  • the test process of the same type of stress test project is relatively similar. Therefore, a corresponding weight can be set for each existing stress test item based on the correlation between the existing stress test type and the target stress test type. The higher the relevance, the higher the corresponding weight.
  • the weight of the existing stress test item of the same type as the target pressure test type can be set to a, and the weight of the existing stress test item of the other type different from the target stress test type is set to 0.5a. .
  • S313 weighting and summing the number of calls of each target custom function in different existing stress test items based on the weight of each existing stress test item, and obtaining an average of each target custom function. The number of calls.
  • each target custom function After obtaining the number of calls for each target custom function in each existing stress test item, and according to the weights set for each existing stress test item, each target custom function is different.
  • the number of calls in the stress test project is weighted and averaged, that is, the average number of calls per target custom function is obtained.
  • a corresponding weight is set for each existing stress test item according to the correlation between the existing stress test type and the target stress test type, and each target is calculated according to the set weight value.
  • the average number of calls to the custom function further ensures the accuracy of the data.
  • the target custom function encapsulated in the BeanShell script file is invoked for stress testing, as shown in FIG. 5, and the following steps are also included:
  • the number of iterations of the target custom function during the stress test is counted by starting the counter in the Jmeter.
  • the counter allows the user to create a counter that can be referenced within the thread group. This counter allows the user to configure a starting point, a maximum value and a corresponding number of increments, after which the counter starts at the starting point and continues to the maximum value according to the number of increments. Then, start over and continue to cycle until the end of the stress test. Therefore, during the stress test, the corresponding counter can be configured for each target custom function to count the number of iterations of the target custom function during the stress test.
  • the counter counts the number of iterations of each target custom function during the stress test. If the number of iterations of any target custom function is greater than the iteration threshold, the interpreter is reset to free memory and avoid memory leaks.
  • the number of iterations of each target custom function is counted by using a counter. If the number of iterations of any target custom function is greater than the iteration threshold, the interpreter is reset to avoid memory leakage and further avoid thread blocking. Improve the throughput of the terminal/system.
  • Fig. 6 is a block diagram showing the principle of a Jmeter-based pressure testing device corresponding to the Jmeter-based pressure testing method in the first embodiment.
  • the Jmeter-based stress testing device includes a target stress test request acquisition module 10, a target custom function acquisition module 20, a target custom function packaging module 30, an initialization module 40, and a stress test module 50.
  • the implementation functions of the target stress test request acquisition module 10, the target custom function acquisition module 20, the target custom function encapsulation module 30, the initialization module 40, and the stress test module 50 correspond to the Jmeter-based stress test method in Embodiment 1.
  • the steps are one-to-one correspondence, and the details are not described in detail in order to avoid redundancy.
  • the target stress test request acquisition module 10 is configured to obtain a target stress test request, and the target stress test request includes at least one original data identifier.
  • the target custom function obtaining module 20 is configured to obtain a corresponding target custom function based on the at least one original data identifier, wherein the target custom function is a function that is not encapsulated by the class.
  • the target custom function encapsulation module 30 is configured to encapsulate the target custom function into a BeanShell script file.
  • the initialization module 40 is configured to initialize the BeanShell script file.
  • the stress test module 50 is configured to invoke a target custom function encapsulated in the BeanShell script file for stress testing.
  • the target custom function acquisition module 20 includes a target custom function acquisition unit 21, a prompt message transmission unit 22, and a new custom function acquisition unit 23.
  • the target custom function obtaining unit 21 is configured to obtain, according to the at least one original data identifier, a custom function corresponding to the original data identifier in the custom function list as the target custom function.
  • the prompt message sending unit 22 is configured to send a prompt message if any original function is not obtained in the custom function list if any original data identifier exists.
  • a new custom function obtaining unit 23 is configured to obtain a newly added custom function input by the user as a target custom function.
  • the target custom function obtaining module 20 further includes a new custom function associating unit 24.
  • a new custom function association unit 24 is added to associate the newly added custom function with the corresponding original data identifier and save it to the custom function list.
  • the target custom function encapsulation module 30 includes an average call count acquisition unit 31 and a target custom function encapsulation unit 32.
  • the average call count obtaining unit 31 is configured to acquire an existing stress test item, and obtain an average number of calls of each target custom function based on the existing stress test item.
  • the target custom function encapsulating unit 32 is configured to encapsulate the target custom function whose average number of calls is greater than the preset number of times into a BeanShell script file.
  • the target stress test request further includes a target stress test type.
  • the average call count obtaining unit 31 is further configured to acquire an existing stress test item of the same type of the target stress test in the existing stress test item.
  • the average call count acquisition unit 31 includes a call count count sub-unit 311, a weight value setting sub-unit 312, and an average call count acquisition sub-unit 313.
  • the call count statistics sub-unit 311 is configured to count the number of calls of each target custom function in each existing stress test item.
  • the weight setting sub-unit 312 is configured to set a corresponding weight for each existing stress test item based on the correlation between the existing stress test type and the target stress test type.
  • the average call count acquisition sub-unit 313 is configured to perform weighted summation and average the call times of each target custom function in different existing stress test items based on the weight of each existing stress test item, and obtain an average value The average number of calls per target custom function.
  • the stress test module 50 includes an iteration count statistic unit 51 and an interpreter reset unit 52.
  • the iteration count statistic unit 51 is configured to start a counter and count the number of iterations of the target custom function.
  • the interpreter reset unit 52 is configured to reset the interpreter if the number of iterations of any of the target custom functions is greater than an iteration threshold.
  • the embodiment provides one or more non-volatile readable storage media having computer readable instructions that, when executed by one or more processors, cause the one or more processors to execute The steps of the Jmeter-based stress test method in Embodiment 1 are not repeated here to avoid repetition.
  • the computer readable instructions are executed by one or more processors, causing the one or more processors to implement the functions of the modules/units in the Jmeter based stress testing device of Embodiment 2, to avoid duplication, I won't go into details here.
  • non-volatile readable storage medium may include any entity or device capable of carrying the computer readable instruction code, a recording medium, a USB flash drive, a mobile hard disk, a magnetic disk, an optical disk, a computer memory, only Read-Only Memory (ROM), Random Access Memory (RAM), electrical carrier signals, and telecommunications signals.
  • ROM Read-Only Memory
  • RAM Random Access Memory
  • FIG. 7 is a schematic diagram of a computer device according to an embodiment of the present application.
  • computer device 60 of this embodiment includes a processor 61, a memory 62, and computer readable instructions 63 stored in memory 62 and executable on processor 61.
  • the processor 61 performs the steps of the Jmeter-based stress test method of Embodiment 1 described above when executing the computer readable instructions 63, such as steps S10 to S50 shown in FIG.
  • the processor 61 executes the computer readable instructions 63
  • the functions of the modules/units in the foregoing device embodiments are implemented, such as the target stress test request acquisition module 10, the target custom function acquisition module 20, and the target self shown in FIG.
  • the functions of function encapsulation module 30, initialization module 40, and stress test module 50 are defined.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Hardware Design (AREA)
  • Quality & Reliability (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Investigating Strength Of Materials By Application Of Mechanical Stress (AREA)
  • Stored Programmes (AREA)

Abstract

L'invention concerne un procédé et un appareil de test de contrainte basés sur JMeter, ainsi qu'un dispositif et un support de stockage. Le procédé de test de contrainte basé sur JMeter comprend les étapes suivantes : obtention d'une demande de test de contrainte cible, la demande de test de contrainte cible comprenant au moins un identifiant de données d'origine ; obtention d'une fonction auto-définie cible correspondante sur la base du ou des identifiants de données d'origine, la fonction auto-définie cible étant une fonction qui n'est pas encapsulée par une classe ; encapsulation de la fonction auto-définie cible sous forme de fichier de script BeanShell ; initialisation du fichier de script BeanShell ; et appel de la fonction auto-définie cible encapsulée dans le fichier de script BeanShell pour effectuer un test de contrainte. Selon le procédé de test de contrainte basé sur Jmeter, dans un processus de test de contrainte, une fonction auto-définie cible souhaitée peut être directement appelée, ce qui permet d'obtenir l'effet technique d'une interprétation et d'appels répétés, et d'améliorer le débit d'un terminal/système tout en évitant un blocage de fil.
PCT/CN2018/092636 2018-03-22 2018-06-25 Procédé et appareil de test de contrainte basés sur jmeter, et dispositif et support de stockage WO2019178967A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810239745.1 2018-03-22
CN201810239745.1A CN108572916B (zh) 2018-03-22 2018-03-22 基于Jmeter的压力测试方法、装置、设备及存储介质

Publications (1)

Publication Number Publication Date
WO2019178967A1 true WO2019178967A1 (fr) 2019-09-26

Family

ID=63574571

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/092636 WO2019178967A1 (fr) 2018-03-22 2018-06-25 Procédé et appareil de test de contrainte basés sur jmeter, et dispositif et support de stockage

Country Status (2)

Country Link
CN (1) CN108572916B (fr)
WO (1) WO2019178967A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112069078A (zh) * 2020-09-15 2020-12-11 平安银行股份有限公司 Esa接口压力测试方法、装置、测试设备及存储介质
CN113671929A (zh) * 2021-07-09 2021-11-19 江铃汽车股份有限公司 一种用于基于can通讯的汽车故障数据记录装置及方法
CN114077449A (zh) * 2020-08-20 2022-02-22 网联清算有限公司 数据库服务器的测试方法、装置、电子设备和存储介质

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109542770A (zh) * 2018-10-26 2019-03-29 大唐微电子技术有限公司 一种函数调用的方法、装置、计算机存储介质及终端
CN109582303B (zh) * 2018-10-31 2024-05-03 平安科技（深圳）有限公司 通用组件调用方法、装置、计算机设备及存储介质
CN109656791B (zh) * 2018-11-01 2022-07-12 奇安信科技集团股份有限公司 一种基于Jmeter的gRPC性能测试方法及装置
CN110175131A (zh) * 2019-04-29 2019-08-27 合肥移瑞通信技术有限公司 一种基于PyQt工具包的脚本管理方法及系统
CN111290896B (zh) * 2020-02-12 2024-05-10 广州酷狗计算机科技有限公司 服务器压力的测试方法、装置、设备及介质
CN111427793A (zh) * 2020-04-01 2020-07-17 中电万维信息技术有限责任公司 一种Jmeter脚本自动生成方法

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103399814A (zh) * 2013-07-16 2013-11-20 西安Tcl软件开发有限公司 自动化测试的方法及装置
CN105204849A (zh) * 2015-08-27 2015-12-30 努比亚技术有限公司 压力测试系统及其实现方法
CN107608901A (zh) * 2017-10-20 2018-01-19 北京京东金融科技控股有限公司 基于Jmteter的测试方法及装置、存储介质、电子设备

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102521120B (zh) * 2011-11-16 2014-11-12 中国民航信息网络股份有限公司 一种软件自动化测试系统及方法
CN103729361A (zh) * 2012-10-12 2014-04-16 百度在线网络技术（北京）有限公司 一种数据库性能测试方法及装置
US20150113331A1 (en) * 2013-10-17 2015-04-23 Wipro Limited Systems and methods for improved software testing project execution
CN106201862B (zh) * 2015-05-25 2019-03-15 阿里巴巴集团控股有限公司 web服务压力测试方法及装置
CN106815142A (zh) * 2015-12-02 2017-06-09 北京奇虎科技有限公司 一种软件测试方法和系统
US10387656B2 (en) * 2016-03-21 2019-08-20 Checkmarx Ltd. Integrated interactive application security testing
CN107092559A (zh) * 2017-04-18 2017-08-25 携程旅游信息技术（上海）有限公司 基于Jmeter的测试平台中间件、测试系统及方法
CN107102947B (zh) * 2017-05-12 2020-08-04 中国工商银行股份有限公司 Atm交易流程测试装置及方法
CN107704568B (zh) * 2017-09-29 2019-03-26 马上消费金融股份有限公司 一种测试数据添加的方法及装置

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103399814A (zh) * 2013-07-16 2013-11-20 西安Tcl软件开发有限公司 自动化测试的方法及装置
CN105204849A (zh) * 2015-08-27 2015-12-30 努比亚技术有限公司 压力测试系统及其实现方法
CN107608901A (zh) * 2017-10-20 2018-01-19 北京京东金融科技控股有限公司 基于Jmteter的测试方法及装置、存储介质、电子设备

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114077449A (zh) * 2020-08-20 2022-02-22 网联清算有限公司 数据库服务器的测试方法、装置、电子设备和存储介质
CN114077449B (zh) * 2020-08-20 2023-08-01 网联清算有限公司 数据库服务器的测试方法、装置、电子设备和存储介质
CN112069078A (zh) * 2020-09-15 2020-12-11 平安银行股份有限公司 Esa接口压力测试方法、装置、测试设备及存储介质
CN112069078B (zh) * 2020-09-15 2024-03-19 平安银行股份有限公司 Esa接口压力测试方法、装置、测试设备及存储介质
CN113671929A (zh) * 2021-07-09 2021-11-19 江铃汽车股份有限公司 一种用于基于can通讯的汽车故障数据记录装置及方法
CN113671929B (zh) * 2021-07-09 2022-09-23 江铃汽车股份有限公司 一种用于基于can通讯的汽车故障数据记录装置及方法

Also Published As

Publication number Publication date
CN108572916B (zh) 2021-09-28
CN108572916A (zh) 2018-09-25

Similar Documents

Publication Publication Date Title
WO2019178967A1 (fr) Procédé et appareil de test de contrainte basés sur jmeter, et dispositif et support de stockage
US20190324772A1 (en) Method and device for processing smart contracts
US7469362B2 (en) Using a call stack hash to record the state of a process
CN110059068B (zh) 一种分布式存储系统中的数据校验方法及数据校验系统
US11379260B2 (en) Automated semantic tagging
CN111897724A (zh) 一种适用于云平台的自动化测试方法及装置
US20240121261A1 (en) Automated Security Analysis of Software Libraries
WO2019075994A1 (fr) Procédé, dispositif et système de données fictives à une extrémité ios et support d'informations
Panigrahi et al. An approach to prioritize the regression test cases of object-oriented programs
CN110413442A (zh) 参数校验方法和装置
US9442818B1 (en) System and method for dynamic data collection
CN111221721B (zh) 一种单元测试案例自动化录制和执行方法及装置
CN108427634A (zh) 电子装置、测试的方法及计算机可读存储介质
CN113127314B (zh) 一种检测程序性能瓶颈的方法、装置及计算机设备
CN111008153B (zh) 一种单元测试方法及系统
KR102132449B1 (ko) 자바스크립트 파일 재작성을 통한 자바스크립트 해석 엔진 테스트 방법 및 장치
CN110147313A (zh) 一种日志输出方法及装置
CN109460215A (zh) 应用控制方法及装置
CN105930260A (zh) 一种系统可用性测试方法及装置
CN114443337A (zh) 一种基于js的日志分析方法、装置、电子设备和介质
CN109308256B (zh) 一种java程序动态分析方法、设备和存储介质
CN112667490A (zh) 基于钩子函数的性能测试方法与装置
CN110442508A (zh) 测试任务处理方法、装置、设备和介质
CN110633214A (zh) 一种内部测试报文的配置方法及装置
CN116010112B (zh) 钩子函数的调用方法、装置、计算机设备及可读存储介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18910305

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18910305

Country of ref document: EP

Kind code of ref document: A1