CN115827462A - Interface test method, terminal device and computer readable storage medium - Google Patents

Abstract

The interface testing method can generate a corresponding filing file according to role information to be tested, and modifies the configuration of the interface to be tested according to the filing file so as to test the modified interface to be tested, so that a tester can test the interface according to the role information to be tested, comprehensive coverage of a testing scene is guaranteed, and testing efficiency is improved.

Description

Interface test method, terminal device and computer readable storage medium

Technical Field

The present application relates to the field of software testing technologies, and in particular, to an interface testing method, a terminal device, and a computer-readable storage medium.

Background

In the field of computer technology, it is often necessary to test a system or an application. The traditional interface test scheme is that a tester manually tests an internal interface or automatically tests an internal interface through an interface tool, however, when the existing interface test method faces a service scene that the same interface is associated with multiple roles, because some roles relate to safety requirements, associated interface logs are unavailable, so that the associated interfaces cannot be tested, and the interface test has some omission of scenes.

Disclosure of Invention

In order to solve the technical problem, the application provides an interface testing method, a terminal device and a computer readable storage medium.

In order to solve the above problem, the present application provides an interface testing method, including: receiving an interface test request, wherein the interface test request comprises interface information and role information to be tested; acquiring an interface to be tested based on the interface information; generating a corresponding filing file based on the role information to be tested, and modifying the configuration of the interface to be tested based on the filing file; and testing the modified interface to be tested to obtain the test data of the interface to be tested.

The role information to be tested comprises a role account to be tested; the step of generating a corresponding archive file based on the role information to be tested and modifying the configuration of the interface to be tested based on the archive file comprises the following steps: acquiring the role account to be tested, and judging whether the role account to be tested is a preset account type or not; if the role account to be tested belongs to the preset account type, generating the archive file; and modifying the configuration of the interface to be tested according to the archived file so as to acquire the test data of the role account to be tested through the interface to be tested.

The preset account types at least comprise a first-level account and a second-level account, and the data encryption degree of the first-level account is greater than that of the second-level account.

The step of modifying the configuration of the interface to be tested according to the archive file so as to acquire the test data of the role account to be tested through the interface to be tested comprises the following steps of: acquiring a configuration file of the interface to be tested, wherein the configuration file comprises a first configuration file of a filter; and modifying the first configuration file based on the information of the role to be tested so as to obtain the access authority of the filter.

The interface to be tested comprises a first cut-in port and a second cut-in port, the interface to be tested is connected with a remote database through the first cut-in port, and the interface to be tested is connected with a third-party database through the second cut-in port; the step of modifying the first configuration file based on the information of the role to be tested to obtain the access right of the filter includes: according to the access authority, acquiring a second configuration file of the first cut-in port, or acquiring a third configuration file of the second cut-in port; modifying the second configuration file or modifying the third configuration file according to the interface type of the interface to be tested; and acquiring the connection authority of the interface to be tested and the remote database through the modified first cut-in, or acquiring the connection authority of the interface to be tested and the third-party database through the modified second cut-in.

The step of testing the modified interface to be tested to obtain the test data of the interface to be tested comprises the following steps: and testing the modified interface to be tested according to the connection authority and the access authority so as to obtain the test data.

The step of testing the modified interface to be tested to obtain the test data of the interface to be tested includes: testing the modified interface to be tested to obtain the test data; and storing the test data, the role information to be tested and the interface to be tested in a preset database.

After the step of testing the modified interface to be tested to obtain the test data of the interface to be tested, the interface testing method further includes: responding to a result return instruction of a test end, and inquiring a test result corresponding to the interface test request from the preset database; and returning the test result to the test end.

In order to solve the above problem, the present application provides a terminal device, including a processor and a memory connected to the processor, where the memory stores program data, and the processor retrieves the program data stored in the memory to execute the interface testing method.

To solve the above problems, the present application provides a computer-readable storage medium storing program instructions that are executed to implement the interface testing method as described above.

Different from the prior art, the interface testing method can generate the corresponding filing file according to the role information to be tested, and modifies the configuration of the interface to be tested according to the filing file so as to test the modified interface to be tested, so that a tester can test the interface according to the role information to be tested, comprehensive coverage of a testing scene is ensured, and the testing efficiency is improved.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts. Wherein:

fig. 1 is a schematic flowchart of a first embodiment of an interface testing method provided in the present application;

FIG. 2 is a schematic flowchart of a second embodiment of an interface testing method provided in the present application;

FIG. 3 is a schematic flow chart diagram illustrating a third embodiment of an interface testing method provided in the present application;

FIG. 4 is a schematic flow chart diagram illustrating a fourth embodiment of an interface testing method provided in the present application;

FIG. 5 is a block diagram of an embodiment of a terminal device provided herein;

fig. 6 is a schematic diagram of a framework of another embodiment of a terminal device provided by the present application;

FIG. 7 is a block diagram of an embodiment of a computer-readable storage medium provided herein.

Detailed Description

The technical solutions in the embodiments of the present application will be described clearly and completely with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only some embodiments of the present application, and not all embodiments. All other embodiments, which can be obtained by a person skilled in the art without making any inventive step based on the embodiments in the present application, are within the scope of protection of the present application.

It should be noted that if directional indications (such as upper, lower, left, right, front, rear, 8230; \8230;) are referred to in the embodiments of the present application, the directional indications are only used for explaining the relative positional relationship between the components in a specific posture (as shown in the attached drawings), the motion situation, etc., and if the specific posture is changed, the directional indications are correspondingly changed.

In addition, if there is a description of "first", "second", etc. in the embodiments of the present application, the description of "first", "second", etc. is for descriptive purposes only and is not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one such feature. In addition, technical solutions between the embodiments may be combined with each other, but must be based on the realization of the technical solutions by a person skilled in the art, and when the technical solutions are contradictory to each other or cannot be realized, such a combination should not be considered to exist, and is not within the protection scope claimed in the present application.

In a conventional interface test scheme, a tester usually performs manual test on an internal interface, for example, the tester performs manual test entry on the interface through a test platform such as JMeter; alternatively, the tester may also use an Interface Programming Interface (API) to perform the test automatically. However, when the existing interface testing method faces a service scenario in which a plurality of roles are associated with the same interface, for example, in internal staff software of a bank, roles related to a plurality of bank staff, interfaces accessed when each type of roles logs in the bank software are different, and logs of the interfaces associated with some roles are also unavailable when the interfaces are related to security, so that a corresponding testing scenario cannot be set for the interfaces or the types of roles, and the comprehensive coverage of the testing scenario cannot be realized.

In view of this, the present application first proposes an interface testing method, which is applied to a terminal device and applied to the technical field of software testing. Specifically, the interface testing method can test the interface to be tested based on the role information to be tested, and can be used for automatically testing the interfaces of an application program, a computer system and the like so as to check the exchange, transmission and control management processes of data and the relation of mutual logic dependence, ensure the functions and performances of the application program and the computer system, and improve the stability and safety of the application program and the computer system. When the interface testing method is applied to financial science and technology, the interface testing method can be applied to business scenes such as electronic commerce, electronic payment, securities, electronic banking, tax transaction, credit card, online shopping, insurance and the like, and is not particularly limited.

The terminal equipment of the application can be a server, and can also be a system in which the server and a local terminal are matched with each other. Accordingly, each part, such as each unit, sub-unit, module, and sub-module, included in the terminal device may be entirely disposed in the server, or may be disposed in the server and the local terminal, respectively.

Further, the server may be hardware or software. When the server is hardware, it may be implemented as a distributed server cluster formed by multiple servers, or may be implemented as a single server. When the server is software, it may be implemented as a plurality of software or software modules, for example, software or software modules for providing distributed servers, or as a single software or software module, and is not limited herein. In some possible implementations, the interface testing method of the embodiments of the present application may be implemented by a processor calling a computer readable instruction stored in a memory.

Referring to fig. 1, fig. 1 is a schematic flowchart illustrating a first embodiment of an interface testing method provided in the present application. As shown in fig. 1, in this embodiment, the interface testing method includes the following steps:

step S11: and receiving an interface test request, wherein the interface test request comprises interface information and role information to be tested.

Specifically, the interface test request may be sent by a test end where the tester is located, the terminal device establishes a communication connection with the test end, for example, the tester sends a test instruction at the test end, the test end responds to the test instruction, sends the interface test request to the terminal device, and the terminal device receives the interface test request, where the interface test request at least includes interface information to be tested and role information to be tested.

For example, in an embodiment, a tester selects a test interface at a test end, and the test end generates the role information to be tested according to the interface information and the associated role information of the interface to be tested; or, in another embodiment, the tester selects the interface and the role of the test at the test end, so that the test end generates the corresponding interface information and the role information to be tested.

Step S12: and acquiring the interface to be tested based on the interface information.

And acquiring the corresponding interface to be tested based on the interface information of the interface test request.

Step S13: and generating a corresponding filing file based on the role information to be tested, and modifying the configuration of the interface to be tested based on the filing file.

And generating a corresponding filing file based on the role information to be detected. Specifically, the ARchive file is used to modify a class file of the interface to be tested, and in a specific embodiment, the ARchive file is a server configuration modification file generated by using a Java agent framework, and the format of the ARchive file includes, but is not limited to jar (Java ARchive). The role information to be tested may include a plurality of preset role types, for example, in internal employee software of a bank, role types related to a plurality of bank employees, and a corresponding archive file is generated for each role type.

Step S14: and testing the modified interface to be tested to obtain the test data of the interface to be tested.

After the configuration of the interface to be tested is modified by using the archive file, the modified interface to be tested can be tested through the role information to be tested. Illustratively, when the role information to be tested is an employee role related to security, for example, when the role information to be tested is a salesperson who grasps privacy data of a client, the configuration of the interface to be tested is modified through the corresponding archive file, so that originally unavailable log permissions are modified to be acquirable by the archive file, and the modified interface to be tested is tested and test data is obtained.

In this embodiment, the interface testing method can generate a corresponding archive file according to the role information to be tested, and modify the configuration of the interface to be tested according to the archive file, so as to test the modified interface to be tested, so that a tester can test the interface according to the role information to be tested, thereby ensuring comprehensive coverage of a test scene and improving the testing efficiency.

In an embodiment, please refer to fig. 2, and fig. 2 is a schematic flowchart of a second embodiment of an interface testing method provided in the present application. As shown in fig. 2, in this embodiment, the information of the role to be tested includes a role account to be tested, and the step S13 includes the following steps:

step S21: and acquiring the role account to be tested, and judging whether the role account to be tested is a preset account type.

Specifically, multiple account types can be set according to account security, for example, in a bank employee, a confidential account and a non-confidential account can be set, and since the confidential account has requirements such as service privacy, an interface associated with the confidential account is provided with security measures, so that the corresponding interface cannot acquire an interface log.

When the role account to be tested is obtained, whether the role account to be tested is a preset account type is judged, wherein the preset account type comprises but is not limited to a secret account.

Step S22: and if the role account to be tested belongs to the preset account type, generating an archive file.

If the role account to be tested of the interface test request belongs to the preset account type, for example, when the role account belongs to a secret account, a filing file of the secret account is generated, and the filing file can modify the security measures of the secret account so as to obtain corresponding test data when the associated interface of the secret account is tested.

Step S23: and modifying the configuration of the interface to be tested according to the archived file so as to acquire the test data of the role account to be tested through the interface to be tested.

And after acquiring the archive file of the preset account type, modifying the configuration of the interface to be tested according to the archive file. The configuration of the interface to be tested includes server configuration, for example, when the terminal device is deployed in the Tomcat server, the file under the Tomcat directory may be modified by the archive file, and a relevant configuration for dynamically obtaining the test data is added.

In this embodiment, the interface testing method can generate a corresponding archive file according to the role information to be tested, and modify the configuration of the interface to be tested according to the archive file so as to test the modified interface to be tested, so that a tester can test the interface according to the role information to be tested, thereby ensuring the comprehensive coverage of a test scene and improving the testing efficiency.

In an embodiment, the preset account types at least include a first-level account and a second-level account, and the data encryption degree of the first-level account is greater than that of the second-level account.

Specifically, the confidential accounts comprise a first-level account and a second-level account, the data encryption degree of the first-level account is larger than that of the second-level account, the first-level account corresponds to the first archive file, the second-level account corresponds to the second archive file, and when the configuration of the interface to be tested is modified through the first archive file and the second archive file, the modification range of the first archive file is larger than that of the second archive file, so that a tester can test the interface according to the confidential account level.

For example, in internal employee software of a bank, a first-level account includes employee accounts of positions such as managers and officers, a second-level account includes employee accounts of positions such as financial consultants and sales, and the data encryption degree of the first-level account is greater than that of the second-level account.

In one embodiment, step S23 includes the steps of: acquiring a configuration file of an interface to be tested, wherein the configuration file comprises a first configuration file of a filter; and modifying the first configuration file based on the role information to be tested so as to obtain the access authority of the filter.

Specifically, the filter is configured to filter an interface test request of the terminal device, for example, the filter is configured to determine whether a role account to be tested is logged when the interface test request is sent, and the filter intercepts an interface test request that is not logged successfully, so as to prevent information leakage. Therefore, when the configuration of the interface to be tested is modified through the archive file, the first configuration file needs to be modified through the archive file, so that the interface test request sent by the test end can obtain the access authority of the filter.

In an embodiment, please refer to fig. 3, and fig. 3 is a schematic flowchart of a third embodiment of an interface testing method provided in the present application. As shown in fig. 3, in this embodiment, the interface to be tested includes a first cut-in port and a second cut-in port, the interface to be tested is connected to the remote database through the first cut-in port, and the interface to be tested is connected to the third-party database through the second cut-in port; step S13 includes the steps of:

step S31: and acquiring a second configuration file of the first cut-in port or acquiring a third configuration file of the second cut-in port according to the access authority.

Specifically, the interface to be tested comprises a first cut-in port and a second cut-in port, the first cut-in port is a cut-in port used for carrying out remote service calling, and the remote service is used for establishing connection between a local database and a remote database so as to obtain data of the remote database; the second cut-in is a cut-in used for calling a third-party Protocol, the third-party Protocol includes but is not limited to hypertext Transfer Protocol (HTTP), and the first cut-in and the second cut-in are used for acquiring data of different databases and ensuring authenticity of test data.

Step S32: and modifying the second configuration file or modifying the third configuration file according to the interface type of the interface to be tested.

When the terminal equipment receives the interface test request, a request object (an interface to be tested) needs to be bound into the thread according to the interface test request, and the thread calls the first cut-in or the second cut-in to execute according to the interface type of the interface to be tested so as to modify the second configuration file or the third configuration file.

Step S33: and acquiring the connection authority of the interface to be tested and the remote database through the modified first cut-in, or acquiring the connection authority of the interface to be tested and the third-party database through the modified second cut-in.

And the terminal equipment modifies the second configuration file according to the interface type of the interface to be tested and acquires the connection authority of the interface to be tested and the remote database through the modified first cut-in, or modifies the third configuration file according to the interface type of the interface to be tested and acquires the connection authority of the interface to be tested and the third-party database through the modified second cut-in.

In this embodiment, the interface test method can select and call different cut-in ports according to the interface type of the interface to be tested to obtain corresponding test data, ensure the truth and effectiveness of the test data, and improve the reliability of the interface test.

In an embodiment, please refer to fig. 4, where fig. 4 is a schematic flowchart of a fourth embodiment of an interface testing method provided in the present application. As shown in fig. 4, step S14 includes the steps of: and testing the modified interface to be tested according to the connection authority and the access authority so as to obtain test data.

Specifically, a first configuration file of the filter is modified according to the archive file to obtain the access authority of the filter, and a second configuration file or a third configuration file is modified according to the archive file to obtain the connection authority of the access point. Wherein archive files (jar files) are used to replace classes (classes) for configuration files.

And testing the modified interface to be tested according to the access authority and the connection authority, so that the test data of the interface to be tested can be acquired when the role information to be tested is a confidential account, the comprehensive coverage of a test scene is ensured, the test efficiency is improved, and the reliability of the interface test is improved.

In one embodiment, step S14 includes the steps of: testing the modified interface to be tested to obtain test data; and storing the test data, the role information to be tested and the interface to be tested in a preset database.

Specifically, as shown in fig. 4, the preset database is a database for storing test data, information of roles to be tested, and interfaces to be tested, and the preset database includes, but is not limited to, an embedded database or an independent database server. All role information of the software can be stored in the preset database in advance, or the role information of all secret accounts can be stored in the preset database in advance, and the stored contents include but are not limited to account numbers, names, associated interfaces and the like. When the terminal device obtains the interface test request, the role account to be tested according to the interface test request is matched with the preset database, so that whether the role account to be tested is of the preset account type or not is judged.

After the modified interface to be tested is tested and test data is obtained, the test data, the corresponding role information to be tested and the interface to be tested are stored in a preset database, so that a tester can obtain the corresponding test data through the preset database.

In an embodiment, after step S14, the interface testing method of this embodiment further includes the following steps: responding to a result return instruction of the test end, and inquiring a test result corresponding to the interface test request from a preset database; and returning the test result to the test end.

Specifically, the test result may include test data, role information to be tested, and an interface to be tested, and the terminal device directly returns the generated test data to the test end; or, the terminal device generates a corresponding test conclusion based on the test data, for example, the test conclusion may include evaluation statements such as coverage, test effect, and the like, and returns the test data and the test conclusion as test results to the test end, so that a tester performs test verification. In this embodiment, the test end can only obtain test data corresponding to the interface to be tested, but cannot directly access the preset database, so that the data security of the interface to be tested is ensured.

In an optional embodiment, both the interface test request and the result return instruction can be sent out through a test end where a tester is located, the terminal device and the test end establish communication connection, and after the tester sends out the test instruction at the test end, the terminal device receives the interface test request transmitted by the test end to test the interface to be tested; and after the test is finished, responding to a result return instruction generated by a tester, inquiring a corresponding test result from a preset database by the terminal equipment, and returning the test result to the test end. In other embodiments, the result returning instruction is generated within a preset time of the test instruction, for example, after the tester sends the test instruction at the test end, the test end generates the result returning instruction within the preset time, so as to automatically obtain the test result. The manner of generating the test result and the result return instruction is not particularly limited.

Referring to fig. 5, fig. 5 is a schematic frame diagram of a terminal device according to an embodiment of the present disclosure. As shown in fig. 5, the terminal device 100 includes a processor 101 and a memory 102 connected to the processor 101, wherein the memory 102 stores program data, and the processor 101 retrieves the program data stored in the memory 102 to execute the interface testing method.

Optionally, in an embodiment, the processor 101 is configured to execute the sequence data to implement the following method: receiving an interface test request, wherein the interface test request comprises interface information and role information to be tested; acquiring an interface to be tested based on the interface information; generating a corresponding filing file based on the role information to be detected, and modifying the configuration of the interface to be detected based on the filing file; and testing the modified interface to be tested to obtain the test data of the interface to be tested.

The processor 101 may also be referred to as a Central Processing Unit (CPU). The processor 101 may be an electronic chip having signal processing capabilities. The processor 101 may also be a general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.

The storage 102 may be a memory bank, a TF card, etc., and may store all information in the terminal device 100, including input raw data, computer programs, intermediate operation results, and final operation results, all stored in the storage 102. Which stores and retrieves information based on the location specified by the processor 101. With the memory 102, the terminal device 100 has a memory function to ensure normal operation. The storage 102 of the terminal device 100 may be classified into a main storage (internal storage) and a sub storage (external storage) according to the purpose, and there is a classification method into an external storage and an internal storage. The external memory is usually a magnetic medium, an optical disk, or the like, and can store information for a long period of time. The memory refers to a storage component on the main board, which is used for storing data and programs currently being executed, but is only used for temporarily storing the programs and the data, and the data is lost when the power is turned off or the power is cut off.

Referring to fig. 6, fig. 6 is a schematic frame diagram of another embodiment of a terminal device provided in the present application. As shown in fig. 6, the present application also provides another terminal device 100, where the terminal device 100 includes a receiving module 103, an obtaining module 104, a modifying module 105, and a testing module 106.

The receiving module 103 is configured to receive an interface test request, where the interface test request includes interface information and role information to be tested; the obtaining module 104 is configured to obtain an interface to be tested based on the interface information; the modification module 105 is configured to generate a corresponding archive file based on the role information to be tested, and modify the configuration of the interface to be tested based on the archive file; the test module 106 is configured to test the modified interface to be tested to obtain test data of the interface to be tested.

In an embodiment of the present application, each module in the terminal device 100 may be respectively or completely combined into one or several units to form the unit, or some unit(s) may be further split into multiple sub-units with smaller functions, which may implement the same operation without affecting implementation of technical effects of the embodiment of the present application. The modules are divided based on logic functions, and in practical application, the functions of one module can be realized by a plurality of units, or the functions of a plurality of modules can be realized by one unit.

Referring to fig. 7, fig. 7 is a block diagram of an embodiment of a computer-readable storage medium provided in the present application. As shown in fig. 7, the computer readable storage medium 110 has stored therein program instructions 111 that are capable of implementing all of the methods described above.

The unit in which the functional units in the embodiments of the present application are integrated may be stored in the computer-readable storage medium 110 if it is implemented in the form of a software functional unit and sold or used as a separate product. Based on such understanding, the technical solution of the present application may be substantially implemented or contribute to the prior art, or all or part of the technical solution may be embodied in the form of a software product, and the computer-readable storage medium 110 includes several instructions in a program instruction 111 to enable a computer device (which may be a personal computer, a system server, or a network device, etc.), an electronic device (for example, MP3, MP4, etc., and may also be a mobile terminal such as a mobile phone, a tablet computer, a wearable device, etc., or a desktop computer, etc.), or a processor (processor) to execute all or part of the steps of the method of the embodiments of the present application.

As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-readable storage media 110 (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the application. It is to be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by the computer-readable storage medium 110. These computer-readable storage media 110 may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the program instructions 111, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer-readable storage media 110 may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the program instructions 111 stored in the computer-readable storage media 110 produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer-readable storage media 110 may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the program instructions 111 that execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

Any process or method descriptions in flow charts or otherwise described herein may be understood as representing modules, segments, or portions of code which include one or more executable instructions for implementing specific logical functions or steps of the process, and the scope of the preferred embodiments of the present application includes other implementations in which functions may be executed out of order from that shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved, as would be understood by those reasonably skilled in the art of the present application.

The logic and/or steps represented in the flowcharts or otherwise described herein, such as an ordered listing of executable instructions that can be viewed as implementing logical functions, can be embodied in any computer-readable medium for use by or in connection with an instruction execution system, apparatus, or device (e.g., a personal computer, server, network device, or other system that can fetch the instructions from the instruction execution system, apparatus, or device and execute the instructions).

The above description is only for the purpose of illustrating embodiments of the present application and is not intended to limit the scope of the present application, and all modifications of equivalent structures and equivalent processes, which are made by the contents of the specification and the drawings of the present application or are directly or indirectly applied to other related technical fields, are also included in the scope of the present application.

Claims (10)

1. An interface testing method, comprising:

receiving an interface test request, wherein the interface test request comprises interface information and role information to be tested;

acquiring an interface to be tested based on the interface information;

generating a corresponding filing file based on the role information to be tested, and modifying the configuration of the interface to be tested based on the filing file;

and testing the modified interface to be tested to obtain the test data of the interface to be tested.

2. The interface testing method according to claim 1, wherein the role information to be tested includes a role account to be tested; the step of generating a corresponding archive file based on the role information to be tested and modifying the configuration of the interface to be tested based on the archive file comprises the following steps:

acquiring the role account to be tested, and judging whether the role account to be tested is a preset account type or not;

if the role account to be tested belongs to the preset account type, generating the archive file;

and modifying the configuration of the interface to be tested according to the archived file so as to acquire the test data of the role account to be tested through the interface to be tested.

3. The interface testing method according to claim 2, wherein the predetermined account types include at least a first-level account and a second-level account, and the data encryption degree of the first-level account is greater than that of the second-level account.

4. The interface testing method according to claim 2, wherein the step of modifying the configuration of the interface to be tested according to the archive file to obtain the test data of the role account to be tested through the interface to be tested comprises:

acquiring a configuration file of the interface to be tested, wherein the configuration file comprises a first configuration file of a filter;

and modifying the first configuration file based on the role information to be tested so as to obtain the access authority of the filter.

5. The interface testing method according to claim 4, wherein the interface to be tested includes a first cut-in port and a second cut-in port, the interface to be tested is connected with a remote database through the first cut-in port, and the interface to be tested is connected with a third-party database through the second cut-in port;

the step of modifying the first configuration file based on the information of the role to be tested to obtain the access right of the filter includes:

according to the access authority, acquiring a second configuration file of the first cut-in port, or acquiring a third configuration file of the second cut-in port;

modifying the second configuration file or modifying the third configuration file according to the interface type of the interface to be tested;

and acquiring the connection authority of the interface to be tested and the remote database through the modified first cut-in, or acquiring the connection authority of the interface to be tested and the third-party database through the modified second cut-in.

6. The interface testing method according to claim 5, wherein the step of testing the modified interface to be tested to obtain the test data of the interface to be tested comprises:

and testing the modified interface to be tested according to the connection authority and the access authority so as to obtain the test data.

7. The interface testing method according to claim 1, wherein the step of testing the modified interface to be tested to obtain the test data of the interface to be tested comprises:

testing the modified interface to be tested to obtain the test data;

and storing the test data, the role information to be tested and the interface to be tested in a preset database.

8. The interface testing method according to claim 7, wherein after the step of testing the modified interface to be tested to obtain the test data of the interface to be tested, the interface testing method further comprises:

responding to a result return instruction of a test end, and inquiring a test result corresponding to the interface test request from the preset database;

and returning the test result to the test end.

9. A terminal device, comprising a processor and a memory connected to the processor, wherein the memory stores program data, and the processor retrieves the program data stored in the memory to execute the interface testing method according to any one of claims 1 to 8.

10. A computer-readable storage medium, in which program instructions are stored, the program instructions being executed to implement the interface testing method according to any one of claims 1 to 8.

Images