Multi-channel platform product testing method and device, electronic equipment and storage medium

Abstract

The application discloses a multi-channel platform product testing method and device, electronic equipment and a storage medium, and relates to the technical field of product testing. The multi-channel platform product testing method comprises the following steps: determining a target testing strategy of a platform product according to a system architecture type of the platform product, wherein the system architecture type is used to represent the corresponding relationship between a business application and a channel in the platform product; and testing the platform product through the target testing strategy to obtain a testing result. According to the technical scheme, the unified testing strategy can be determined according to the system architecture type of the multi-channel platform product, so that the mistakes and omissions of the testing items can be avoided, and the accuracy and comprehensiveness of the testing result are improved.

Description

Technical Field

[0001] This application relates to the field of product testing technology, and in particular to a multi-channel platform product testing method, apparatus, electronic device, and computer-readable storage medium. Background Technology

[0002] In today's era of rapid development in internet applications, platform-layer business products with multiple connection channels are becoming increasingly widely used due to their strong adaptability and rich functionality. However, these multi-channel platform products often encounter some problems during actual testing. Specifically, there is a lack of clear and unified guidelines on which connection channels among the various connection channels of the platform product need to be tested and verified, and how to formulate test plans. The formulation of these test plans is often greatly influenced by the subjective factors of the product owner and the test owner, resulting in a low degree of objectivity in the test plans and making it easy for errors and omissions to be found in certain test items, ultimately affecting the accuracy and comprehensiveness of the test results. Summary of the Invention

[0003] The main purpose of this application is to provide a testing method, apparatus, electronic device and readable storage medium for multi-channel platform products, aiming to solve the technical problem of low accuracy and comprehensiveness of existing test results for multi-channel platform products.

[0004] To achieve the above objectives, this application provides a multi-channel platform product testing method, which includes: Based on the system architecture type of the platform product, determine the target testing strategy for the platform product, wherein the system architecture type is used to characterize the correspondence between business applications and channels in the platform product; The platform product is tested using the target testing strategy to obtain test results.

[0005] Optionally, the system architecture type includes a first system architecture type, the platform product corresponding to the first system architecture type includes a business application, and the business application corresponds to multiple channels; The step of testing the platform product using the target testing strategy and obtaining test results includes: When the system architecture type of the platform product is the first system architecture type, all channels of the platform product are tested separately to obtain the test results corresponding to each channel.

[0006] Optionally, the system architecture type includes a second system architecture type, and the platform product corresponding to the second system architecture type includes multiple business applications with different priorities and multiple corresponding channels; The step of testing the platform product using the target testing strategy and obtaining test results includes: When the system architecture type of the platform product is the second system architecture type, determine whether the message types and structures of each channel corresponding to the platform product are the same; If all are the same, then test each of the randomly selected channels separately to obtain the test results for each channel. If they are all different, then all channels of the platform product will be tested separately to obtain the test results corresponding to each channel.

[0007] Optionally, the system architecture type includes a third system architecture type, and the platform product corresponding to the third system architecture type includes multiple business applications and channels corresponding to each of the business applications; The step of testing the platform product using the target testing strategy and obtaining test results includes: When the system architecture type of the platform product is the third system architecture type, the corresponding first channel is determined according to the first interface where the platform product is currently located; The first channel is tested, and the test results corresponding to the first channel are obtained.

[0008] Optionally, the test results include interface test results and API test results; The step of testing the platform product using the target testing strategy and obtaining test results includes: Based on the target testing strategy, determine the channels to be tested; A business request is initiated from the channel to be tested, the business request is processed through the platform product, and the corresponding response result is output. Obtain preset test rules, analyze the response results using the preset test rules, and obtain the interface test results corresponding to the platform product; The robustness, business logic, and interface flow of the interface corresponding to the channel to be tested are tested respectively to obtain the interface test results corresponding to the platform product.

[0009] Optionally, the interface test results include at least robustness test results, business logic test results, and process test results; The step of testing the robustness, business logic, and interface flow of the interface corresponding to the channel to be tested, and obtaining the interface test results corresponding to the platform product, includes: By using preset robustness testing rules, the legal characters, field types, required fields, field lengths, and security policies in the interface of the channel under test are verified to obtain robustness test results. The preset business logic is converted into corresponding test data, and the interface of the channel to be tested is tested using the test data to obtain the business logic test results.

[0010] Optionally, the test results may also include database test results, which may include at least a first database test result and a second database test result; The multi-channel platform product testing method also includes: During the interface testing process, the first database test result is generated by comparing the elements entered on the front end with the corresponding content in the database table. During the interface testing process, a second database test result is generated by comparing the interface request message with the corresponding database table content.

[0011] This application also provides a multi-channel platform product testing device, which is applied to a multi-channel platform product testing equipment, and the multi-channel platform product testing device includes: The strategy determination module is used to determine the target testing strategy of the platform product based on the system architecture type of the platform product, wherein the system architecture type is used to characterize the correspondence between business applications and channels in the platform product; The product testing module is used to test the platform product using the target testing strategy and obtain test results.

[0012] This application also provides an electronic device, which is a physical device, comprising: a memory, a processor, and a program of the multi-channel platform product testing method stored in the memory and executable on the processor. When the program of the multi-channel platform product testing method is executed by the processor, it can implement the steps of the multi-channel platform product testing method as described above.

[0013] This application also provides a computer-readable storage medium storing a program for implementing a multi-channel platform product testing method, wherein when the program for the multi-channel platform product testing method is executed by a processor, it implements the steps of the multi-channel platform product testing method as described above.

[0014] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the steps of the multi-channel platform product testing method described above.

[0015] This application provides a multi-channel platform product testing method, apparatus, electronic device, and computer-readable storage medium. First, based on the system architecture type of the platform product, a target testing strategy is determined. The system architecture type characterizes the correspondence between business applications and channels within the platform product. Then, the platform product is tested using the target testing strategy to obtain test results. This application's technical solution determines a unified testing strategy based on the system architecture type of the multi-channel platform product, enabling comprehensive and accurate testing of platform products with different system architecture types. This effectively avoids errors and omissions in test items due to subjective factors of testers, resulting in more accurate and comprehensive test results.

[0016] Furthermore, the technical solution of this application provides a unified testing strategy by formulating unified testing plans for platform products across multiple channels. These plans and strategies can form clear and unified guidelines for staff to refer to during testing, facilitating the efficient promotion and implementation of various platform products. Attached Figure Description

[0017] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0018] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, for those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0019] Figure 1 This is a flowchart illustrating the first embodiment of the multi-channel platform product testing method of this application; Figure 2 This is a schematic diagram of the system architecture corresponding to the platform product of the first system architecture type in the first embodiment of the multi-channel platform product testing method of this application; Figure 3 This is a schematic diagram of the system architecture corresponding to the platform product of the second system architecture type in the first embodiment of the multi-channel platform product testing method of this application; Figure 4 This is a schematic diagram of the system architecture corresponding to the platform product of the third system architecture type in the first embodiment of the multi-channel platform product testing method of this application; Figure 5 This is a schematic diagram illustrating the structure between different testing dimensions of the platform product in the second embodiment of the multi-channel platform product testing method of this application. Figure 6This is a schematic diagram of the layered testing architecture of the platform product for different testing dimensions in the second embodiment of the multi-channel platform product testing method of this application; Figure 7 This is a schematic diagram of the composition structure of the multi-channel platform product testing device in the embodiments of this application; Figure 8 This is a schematic diagram of the hardware operating environment involved in the multi-channel platform product testing method in this application embodiment.

[0020] The purpose, features, and advantages of this application will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. Detailed Implementation

[0021] To make the above-mentioned objectives, features, and advantages of this application more apparent and understandable, the technical solutions in the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are merely some embodiments of this application, and not all embodiments. Based on the embodiments in this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0022] Example 1 This application provides a multi-channel platform product testing method. In the first embodiment of this application's multi-channel platform product testing method, refer to... Figure 1 The multi-channel platform product testing method includes: Step S10: Determine the target testing strategy for the platform product based on the system architecture type of the platform product, wherein the system architecture type is used to characterize the correspondence between business applications and channels in the platform product; In this embodiment, it is first necessary to analyze the system architecture type of the platform product, and then formulate an appropriate testing strategy based on the system architecture type. When the system architecture type of the platform product is different, the number and corresponding relationship of the business applications and channels are different. Therefore, it is necessary to execute different testing strategies (extraction testing or coverage testing) for each channel according to different system architecture types, so as to avoid the negative impact of coupling between different channels on the test results.

[0023] In one feasible implementation, when analyzing a multi-channel platform product, the system architecture analysis of the product is performed first. Specifically, a platform product can be broken down into a bottom core layer, a middle product layer (the product layer can be further layered according to the actual product situation), a top channel layer, and external input and output layers on the left and right sides. The multi-channel platform product formed by combining these layers typically has three architecture types: "multiple channels + a single business application," "multiple channels + business applications with different priorities," and "multiple channels + one-to-one mapped business applications." Among these three system architecture types, refer to... Figure 2 Platform products with a system architecture of "multiple channels + single business application" correspond to one external input and one external output and are supported by an underlying core system. Moreover, the platform product includes a front-end, business applications, and basic applications. The business applications have multiple corresponding channels (A, B, C) for customers or operations personnel to initiate transaction and query requests, etc. The coupling between different channels is high. When the interface of the platform product changes (i.e., the channel changes), the response of the platform product is also different. Coverage testing is required for different channels. Therefore, the target testing strategy for this type of platform product is coverage testing.

[0024] On the other hand, refer to Figure 3 The "multiple channels + business applications of different priorities" architecture can include a high-priority business application and a low-priority business application, as well as an external input and an external output, supported by the underlying core system. The channels corresponding to the business applications of different priorities are different, which may be one-to-one or one-to-many. In this type of platform product architecture, there is a certain degree of coupling between different channels, which requires further analysis: if the message types and interfaces of different channels are the same, then different channels can be sampled for testing; if the message types and interfaces of different channels are different, then all channels need to be covered for testing.

[0025] Furthermore, refer to Figure 4 The system architecture type of "multiple channels + one-to-one mapping business application" corresponds to one external input and one external output and is supported by the underlying core system. Moreover, the platform product includes front-end, business application and basic application, where business application A corresponds to channel A, business application B corresponds to channel B and business application C corresponds to channel C. In this type of system architecture platform product, different channels are completely decoupled. If the interface of the platform product changes, it is only necessary to analyze which channel the current interface corresponds to and test for that channel.

[0026] Step S20: Test the platform product using the target testing strategy to obtain test results.

[0027] In this embodiment of the application, it should be noted that after the target testing strategy corresponding to the system architecture of the platform product has been determined, the corresponding testing steps can be performed on the platform product according to the target testing strategy to obtain the test results corresponding to the platform product. The test results need to be evaluated based on the expected functions of the platform product and the checklist to evaluate the response results of the platform product to each test item, and finally obtain the final test results of the platform product.

[0028] In one feasible embodiment, reference is made to Figure 5 While testing each channel of the platform product separately, the testing dimensions can be divided into three parts: interface testing, user interface testing, and database testing. This yields multi-layered test results and avoids incomplete testing or omissions in test items. It's important to note that interface and user interface testing are relatively independent, while database testing, as a lower-level testing dimension, is performed concurrently with interface and user interface testing because the database can support both.

[0029] For example, in the process of testing business processes and functions, the test chain is usually end-to-end testing, and different test organization forms can be selected.

[0030] Optionally, the first test organization form may include business requests initiated by the corresponding testers of each channel, follow-up processing by the platform product testers, and the expected results checked by the product platform. Its advantage is that each participant performs its own duties, with clear responsibilities, and conducts testing in their respective familiar areas, resulting in high testing efficiency. However, its disadvantage is that incomplete or insufficient testing coverage may occur at system boundaries or in ambiguous areas.

[0031] Optionally, the second testing organization form may include each channel's corresponding tester initiating a business request, the platform product tester handling the follow-up processing, and the platform product provider providing a checklist for the platform product, followed by the channel tester checking the expected results. Its advantage lies in that each party performs its own duties, with clear responsibilities, and conducts testing in their respective areas of expertise, resulting in high testing efficiency and reducing the testing pressure on the platform product provider. However, its disadvantages include the possibility of incomplete or insufficient testing coverage at system boundaries or in ambiguous areas, and the channel testers' insufficient knowledge of the platform product, leading to low accuracy in checking the expected results.

[0032] Optionally, the third form of test organization may include each channel's corresponding tester initiating a business request and performing follow-up processing, and then checking the expected results according to the platform product checklist provided by the platform product provider. Its advantage is that the channel test room can perform complete end-to-end testing without any breaks in the middle, eliminating the possibility of incomplete or insufficient test coverage. Its disadvantage is that the channel testers do not have enough knowledge of the platform product and the accuracy of the expected results check is not high.

[0033] Optionally, the fourth form of test organization may include the platform product tester initiating business from various channels and carrying out follow-up processing, followed by checking the expected results. Its advantage is that the platform product tester can perform complete end-to-end testing without any breaks in the middle, eliminating situations where the test is not covered or the coverage is insufficient. However, the disadvantage is that this will put more pressure on the platform product tester to connect with the testing, and since the platform product involves many channels, it is necessary for upstream channels to provide operation manuals or channel support personnel, which will affect the efficiency of the initial testing to a certain extent.

[0034] In specific implementations, project managers can choose one or more of the above-mentioned test organization forms to conduct separate tests on each channel of the platform product according to actual needs, so as to improve test efficiency, test accuracy and comprehensiveness as much as possible.

[0035] In this embodiment of the application, it should be noted that, during interface testing, the optional testing methods include: manual testing, such as manual testing by project team members or manual testing by recruited testers; and automated interface testing, such as automated testing of web interfaces, automated testing of client interfaces, and automated testing of app interfaces. During API testing, the optional testing methods include: tool testing (such as Postman, API testing tools); and automated API testing, such as open-source or self-developed automated API testing tools. During database testing, the optional testing methods include: The testing methods include manual comparison, comparison using software or tools, and automated comparison. Project managers can choose one or more of these methods to test the platform product based on actual needs.

[0036] Further, the system architecture type includes a first system architecture type, the platform product corresponding to the first system architecture type includes a business application, and the business application corresponds to multiple channels; the step of testing the platform product through the target testing strategy and obtaining test results may include: Step S21: When the system architecture type of the platform product is the first system architecture type, all channels of the platform product are tested separately to obtain the test results corresponding to each channel.

[0037] In this embodiment, it should be noted that the first system architecture type is "multiple channels + single business application". In this case, the business application of the platform product has multiple corresponding channels. Since these channels all correspond to the same business application, the coupling between different channels is high. When the interface of the platform product changes (i.e., the channel changes), the response of the platform product is also different. Therefore, coverage testing is required for different channels. Thus, the target testing strategy for the platform product of this system architecture type is coverage testing. When executing this target testing strategy, all channels of the platform product need to be tested separately to obtain the test results corresponding to each channel.

[0038] On the other hand, the system architecture type includes a second system architecture type, and the platform product corresponding to the second system architecture type includes multiple business applications with different priorities and multiple corresponding channels; the step of testing the platform product through the target testing strategy and obtaining test results may include: Step S22: When the system architecture type of the platform product is the second system architecture type, determine whether the message types and structures of each channel corresponding to the platform product are the same; Step S23: If all are the same, then test the randomly selected channels separately to obtain the test results corresponding to each channel. Step S24: If all are different, then test all channels of the platform product separately to obtain the test results corresponding to each channel.

[0039] In this embodiment, the second system architecture type is "multiple channels + business applications with different priorities." As an example, it includes one high-priority business application and one low-priority business application. The high-priority application corresponds to one channel, and the low-priority application corresponds to two channels. In this case, there is a certain degree of coupling between the channels of the platform product. Therefore, it is necessary to further determine whether the message types and interfaces between the channels are the same. If they are all the same, one or more channels are randomly selected from the multiple channels with the same message type and interface for sampling testing. If they are all different, multiple channels with different message types and interfaces are tested separately, thereby achieving coverage testing of channels with each message type and interface.

[0040] On the other hand, the system architecture type includes a third system architecture type, and the platform product corresponding to the third system architecture type includes multiple business applications and channels corresponding to each business application; the step of testing the platform product through the target testing strategy and obtaining test results includes: Step S25: When the system architecture type of the platform product is the third system architecture type, determine the corresponding first channel based on the first interface where the platform product is currently located; Step S26: Test the first channel and obtain the test results corresponding to the first channel.

[0041] In this embodiment, the third system architecture type is "multiple channels + one-to-one mapping business applications." As an example, the platform product includes multiple business applications, and each business application has a separate corresponding channel. In this case, the channels are completely decoupled. Therefore, it is only necessary to detect and confirm the changes to the platform product's interface and test the interface of the first channel corresponding to the changes.

[0042] This application provides a multi-channel platform product testing method. First, based on the system architecture type of the platform product, a target testing strategy is determined. The system architecture type is used to characterize the correspondence between business applications and channels in the platform product. Then, the platform product is tested using the target testing strategy to obtain test results. The technical solution of this application determines a unified testing strategy by using the system architecture type of the multi-channel platform product, thereby enabling platform products with different system architecture types to undergo comprehensive and accurate testing. This effectively avoids errors and omissions in test items due to the influence of subjective factors of testers, and outputs test results with higher accuracy and comprehensiveness.

[0043] Furthermore, the technical solutions of this application provide a unified testing strategy by uniformly formulating testing plans for multi-channel platform products. These plans and strategies can form clear and unified guidelines for testing work, facilitating efficient promotion and implementation across various platform products.

[0044] Example 2 Furthermore, based on the first embodiment of this application, in another embodiment of this application, the content that is the same as or similar to that in Embodiment 1 above can be referred to the above description and will not be repeated hereafter. Based on this, after determining the target testing strategy steps corresponding to the platform product, the method may further include: Step A10: Based on the target testing strategy, determine the channel to be tested; Step A20: Initiate a business request from the channel to be tested, process the business request through the platform product, and output the corresponding response result; Step A30: Obtain preset test rules, analyze the response results using the preset test rules, and obtain the interface test results corresponding to the platform product; Step A40: Test the robustness, business logic, and interface flow of the interface corresponding to the channel to be tested, and obtain the interface test results corresponding to the platform product.

[0045] In this embodiment, it should be noted that after determining the target testing strategy and testing channels based on the system architecture type of the platform product, the testing layers of the platform product can be further divided to obtain the interface testing results and API testing results. Optionally, during the testing of the platform product's interface and API, the data supporting the interface and API testing can also be tested to obtain database testing results.

[0046] For example, refer to Figure 6 The platform product testing is divided into three levels: interface, API, and database. Interface testing includes business process testing and business function testing, while API testing includes API robustness testing, API business logic testing, and API process testing. This application's embodiment, by providing the above-mentioned hierarchical division scheme for platform product testing, standardizes the guidelines for platform product testing, which is more conducive to the promotion and implementation of platform products. It also avoids errors and omissions in test items and insufficient standardization of test results due to subjective factors of project leaders or testers.

[0047] Additionally, it should be noted that after obtaining the target testing strategy for the platform product, the corresponding channels to be tested can be determined. For example, when the system architecture type of the platform product is "multiple channels + a single business application", the corresponding target testing strategy is coverage testing, meaning all channels are to be tested. When the system architecture type of the platform product is "multiple channels + business applications with different priorities", the corresponding target testing strategy is to first determine whether the channel interfaces and message types are the same. If they are the same, sampling testing is performed, meaning the channels to be tested are randomly selected. If they are different, coverage testing is performed, meaning all channels are to be tested. When the system architecture type of the platform product is "multiple channels + one-to-one mapped business applications", the corresponding target testing strategy is to test the channels with changing interfaces.

[0048] Furthermore, the business requests refer to various business requests involved in the actual use scenarios of the platform product, such as transaction requests or query requests. After the business request is input through the channel to be tested, the platform product will process the business request accordingly, call the data in the corresponding database, and output the corresponding response result. After obtaining the response result, the result can be analyzed and verified according to the preset test rules (checklist) to determine whether the response result meets expectations, thereby obtaining the corresponding interface test result. On the other hand, when testing the interface, the corresponding interface of the platform product can be called, and preset test data can be input to obtain the corresponding response result. Similarly, the result can be analyzed according to the preset test rules to obtain the corresponding interface test result.

[0049] Furthermore, the interface test results include at least robustness test results, business logic test results, and process test results; the step of testing the robustness, business logic, and interface process of the interface corresponding to the channel to be tested to obtain the interface test results corresponding to the platform product may further include: Step A41: The robustness test results are obtained by verifying the legal characters, field types, required fields, field lengths, and security policies in the interface of the channel to be tested through preset robustness test rules. Step A42: Convert the preset business logic into corresponding test data, and use the test data to perform business logic testing on the interface of the channel to be tested, and obtain the business logic test results; Step A43: Combine multiple process property interfaces to obtain a process interface group; Step A44: Perform business logic testing on the process interface group to obtain the process test results.

[0050] This application provides a detailed execution step for testing the interface of a platform product, specifically including testing the robustness, business logic, and process of the interface. The preset robustness testing rules include specifications for various dimensions of the fields in the interface of the channel to be tested, as well as specifications for security policies. These rules are used to determine whether the characters in the interface are valid, whether the types are correct, whether required fields are filled, whether the field lengths meet the specifications, and whether the security policies comply with the specifications. The robustness test result of the interface is then obtained by comprehensively evaluating the results of these various dimensions.

[0051] It should also be noted that the preset business logic refers to the platform product's functionalities and the internal operating logic assigned to it during development. This includes outputting a certain response result according to preset procedures upon receiving certain data, reflecting whether the platform product's business functions are normal. In the specific testing process, test data conforming to the business logic can be set according to the actual application scenario and input into the interface. After the test data is transmitted to the corresponding business application, a corresponding response result is returned. The response result is then verified according to the preset business logic to determine whether it meets expectations, thereby obtaining the business logic test result of the interface.

[0052] On the other hand, in platform products, there are some complex interfaces or interfaces with process characteristics. These interfaces need to be combined to test the business logic, so as to test whether the process is normal. This is a business logic test that combines multiple interfaces. Specifically, it involves first combining interfaces with the characteristics of sequential process, and then testing them according to the execution steps of business logic test to obtain the process test results corresponding to the process.

[0053] Furthermore, the test results also include database test results, which at least include first database test results and second database test results; the multi-channel platform product testing method may also include: Step A50: During the interface testing process, the first database test result is generated by comparing the front-end input elements with the corresponding database table content. Step A60: During the interface testing process, a second database test result is generated by comparing the interface request message with the corresponding database table content.

[0054] In this embodiment of the application, it should be noted that step A50 is executed simultaneously with step A20 or A30, and step A60 is executed simultaneously with step A40. This is because the role of the database in the platform product includes providing data retrieval and data storage for interface testing and API testing. Therefore, while interface testing and API testing are being conducted, the database is also performing data querying, retrieval, table creation, and storage processes. Thus, database testing can be performed simultaneously.

[0055] The database testing process specifically includes comparing the front-end input elements with the database table content during interface testing. When the front-end input elements and the corresponding database table content are consistent, it indicates that the database input of the front-end input elements is normal. During interface testing, the interface request message is compared with the database table content at that time. When the interface request message and the corresponding database table content are consistent, it indicates that the database input of the interface request message is normal.

[0056] This application provides a method for layered execution of the testing process in platform product testing. First, based on the target testing strategy, the channel to be tested is determined. A business request is initiated from the channel to be tested, and the platform product processes the business request, outputting a corresponding response result. Preset testing rules are obtained, and the response result is analyzed using the preset testing rules to obtain the interface test results corresponding to the platform product. The robustness, business logic, and interface flow of the interface corresponding to the channel to be tested are tested separately to obtain the interface test results corresponding to the platform product. The technical solution of this application provides the above-mentioned layered division scheme for platform product testing, unifying and standardizing the guidance specifications for platform product testing, which is more conducive to the promotion and implementation of platform products. It also avoids errors and omissions in test items and insufficient standardization of test results due to subjective factors of project leaders or testers, improving the accuracy and comprehensiveness of platform product test results.

[0057] Example 3 This application also provides a multi-channel platform product testing device, which is applied to multi-channel platform product testing equipment, as described above. Figure 7 The multi-channel platform product testing device includes: The strategy determination module 10 is used to determine the target testing strategy of the platform product based on the system architecture type of the platform product, wherein the system architecture type is used to characterize the correspondence between business applications and channels in the platform product; Product testing module 20 is used to test the platform product through the target testing strategy and obtain test results.

[0058] Optionally, the system architecture type includes a first system architecture type, the platform product corresponding to the first system architecture type includes a business application, and the business application corresponds to multiple channels; The product testing module 20 is also used for: When the system architecture type of the platform product is the first system architecture type, all channels of the platform product are tested separately to obtain the test results corresponding to each channel.

[0059] Optionally, the system architecture type includes a second system architecture type, and the platform product corresponding to the second system architecture type includes multiple business applications with different priorities and multiple corresponding channels; The product testing module 20 is also used for: When the system architecture type of the platform product is the second system architecture type, determine whether the message types and structures of each channel corresponding to the platform product are the same; If all are the same, then test each of the randomly selected channels separately to obtain the test results for each channel. If they are all different, then all channels of the platform product will be tested separately to obtain the test results corresponding to each channel.

[0060] Optionally, the system architecture type includes a third system architecture type, and the platform product corresponding to the third system architecture type includes multiple business applications and channels corresponding to each of the business applications; The product testing module 20 is also used for: When the system architecture type of the platform product is the third system architecture type, the corresponding first channel is determined according to the first interface where the platform product is currently located; The first channel is tested, and the test results corresponding to the first channel are obtained.

[0061] Optionally, the test results include interface test results and API test results; The product testing module 20 is also used for: Based on the target testing strategy, determine the channels to be tested; A business request is initiated from the channel to be tested, the business request is processed through the platform product, and the corresponding response result is output. Obtain preset test rules, analyze the response results using the preset test rules, and obtain the interface test results corresponding to the platform product; The robustness, business logic, and interface flow of the interface corresponding to the channel to be tested are tested respectively to obtain the interface test results corresponding to the platform product.

[0062] Optionally, the interface test results include at least robustness test results, business logic test results, and process test results; The product testing module 20 is also used for: By using preset robustness testing rules, the legal characters, field types, required fields, field lengths, and security policies in the interface of the channel under test are verified to obtain robustness test results. The preset business logic is converted into corresponding test data, and the interface of the channel to be tested is tested using the test data to obtain the business logic test results. Multiple process-related interfaces are combined to obtain a process interface group; The business logic of the process interface group is tested to obtain the process test results.

[0063] Optionally, the test results may also include database test results, which may include at least a first database test result and a second database test result; The product testing module 20 is also used for: During the interface testing process, the first database test result is generated by comparing the elements entered on the front end with the corresponding content in the database table. During the interface testing process, a second database test result is generated by comparing the interface request message with the corresponding database table content.

[0064] The multi-channel platform product testing device provided in this application adopts the multi-channel platform product testing method in the above embodiments, solving the technical problem of low accuracy and comprehensiveness of existing multi-channel platform product testing results. Compared with the prior art, the beneficial effects of the multi-channel platform product testing device provided in this application are the same as those of the multi-channel platform product testing method provided in the above embodiments, and other technical features in this multi-channel platform product testing device are the same as those disclosed in the previous embodiment method, and will not be repeated here.

[0065] Example 4 This application provides an electronic device, which includes: at least one processor; and a memory communicatively linked to the at least one processor; wherein the memory stores instructions executable by the at least one processor, which are executed by the at least one processor to enable the at least one processor to perform the multi-channel platform product testing method in Embodiment 1 above.

[0066] The following is for reference. Figure 8 The diagram illustrates a structural schematic of an electronic device suitable for implementing embodiments of the present disclosure. The electronic devices in the embodiments of the present disclosure may include, but are not limited to, mobile terminals such as mobile phones, laptops, digital broadcast receivers, PDAs (personal digital assistants), PADs (tablet computers), PMPs (portable media players), in-vehicle terminals (e.g., in-vehicle navigation terminals), and fixed terminals such as digital TVs and desktop computers. Figure 8 The electronic device shown is merely an example and should not be construed as limiting the functionality and scope of the embodiments disclosed herein.

[0067] like Figure 8As shown, the electronic device may include a processing unit 1001 (e.g., a central processing unit, a graphics processor, etc.), which can perform various appropriate actions and processes according to a program stored in a read-only memory 1002 (ROM) or a program loaded from a storage device 1003 into a random access memory 1004 (RAM). The RAM 1004 also stores various programs and data required for the operation of the electronic device. The processing unit 1004, ROM 1002, and RAM 1004 are interconnected via a bus 1005. An input / output (I / O) interface 1006 is also linked to the bus 1005.

[0068] Typically, the following systems can be linked to I / O interface 1006: input devices 1007 including, for example, touchscreens, touchpads, keyboards, mice, image sensors, microphones, accelerometers, gyroscopes, etc.; output devices 1008 including, for example, liquid crystal displays (LCDs), speakers, vibrators, etc.; storage devices 1003 including, for example, magnetic tapes, hard disks, etc.; and communication devices 1009. Communication device 1009 allows the electronic device to communicate wirelessly or wiredly with other devices to exchange data. Although electronic devices with various systems are shown in the figures, it should be understood that it is not required to implement or possess all the systems shown. More or fewer systems may be implemented alternatively.

[0069] In particular, according to embodiments of this disclosure, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments of this disclosure include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via a communication device, or installed from a storage device, or installed from a ROM. When the computer program is executed by a processing device, it performs the functions defined above in the methods of embodiments of this disclosure.

[0070] The electronic device provided in this application employs the multi-channel platform product testing method described in the above embodiments, thus solving the technical problem of low accuracy and comprehensiveness of existing multi-channel platform product testing results. Compared with the prior art, the beneficial effects of the electronic device provided in this application are the same as those of the multi-channel platform product testing method provided in Embodiment 1 above, and other technical features of this electronic device are the same as those disclosed in the previous embodiment method, and will not be repeated here.

[0071] It should be understood that various parts of this disclosure can be implemented using hardware, software, firmware, or a combination thereof. In the description of the above embodiments, specific features, structures, materials, or characteristics may be combined in any suitable manner in one or more embodiments or examples.

[0072] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

[0073] Example 5 This embodiment provides a computer-readable storage medium having computer-readable program instructions stored thereon, which are used to execute the multi-channel platform product testing method in Embodiment 1 above.

[0074] The computer-readable storage medium provided in this application embodiment may be, for example, a USB flash drive, but is not limited to, electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices, or any combination thereof. More specific examples of computer-readable storage media may include, but are not limited to: electrical links having one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM, or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof. In this embodiment, the computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, system, or device. The program code contained on the computer-readable storage medium may be transmitted using any suitable medium, including but not limited to: wires, optical cables, RF (radio frequency), etc., or any suitable combination thereof.

[0075] The aforementioned computer-readable storage medium may be included in an electronic device or may exist independently without being assembled into an electronic device.

[0076] The aforementioned computer-readable storage medium carries one or more programs. When the aforementioned one or more programs are executed by an electronic device, the electronic device: determines a target testing strategy for the platform product based on the system architecture type of the platform product, wherein the system architecture type is used to characterize the correspondence between business applications and channels in the platform product; and tests the platform product through the target testing strategy to obtain test results.

[0077] Computer program code for performing the operations of this disclosure can be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, and C++, and conventional procedural programming languages ​​such as the "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be linked to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or can be linked to an external computer (e.g., via the Internet using an Internet service provider).

[0078] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this application. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0079] The modules described in the embodiments of this disclosure can be implemented in software or hardware. The names of the modules do not necessarily limit the functionality of the unit itself.

[0080] The computer-readable storage medium provided in this application stores computer-readable program instructions for executing the above-described multi-channel platform product testing method, thus solving the technical problem of low accuracy and comprehensiveness of existing multi-channel platform product test results. Compared with the prior art, the beneficial effects of the computer-readable storage medium provided in this application are the same as the beneficial effects of the multi-channel platform product testing method provided in the above-described embodiments, and will not be repeated here.

[0081] Example 6 This application also provides a computer program product, including a computer program that, when executed by a processor, implements the steps of the multi-channel platform product testing method described above.

[0082] The computer program product provided in this application solves the technical problem of low accuracy and comprehensiveness of test results in existing multi-channel platform products. Compared with the prior art, the beneficial effects of the computer program product provided in this application are the same as those of the multi-channel platform product testing method provided in the above embodiments, and will not be repeated here.

[0083] The above are merely preferred embodiments of this application and do not limit the patent scope of this application. Any equivalent structural or procedural transformations made using the content of this application's specification and drawings, or direct or indirect applications in other related technical fields, are similarly included within the patent scope of this application.

Claims

1. A product testing method for a multi-channel platform, characterized in that, The multi-channel platform product testing method includes: Based on the system architecture type of the platform product, determine the target testing strategy for the platform product, wherein the system architecture type is used to characterize the correspondence between business applications and channels in the platform product; The platform product is tested using the target testing strategy to obtain test results; The system architecture type includes a second system architecture type, and the platform products corresponding to the second system architecture type include multiple business applications with different priorities and multiple corresponding channels. The step of testing the platform product using the target testing strategy and obtaining test results includes: When the system architecture type of the platform product is the second system architecture type, determine whether the message types and structures of each channel corresponding to the platform product are the same; If all are the same, then test each of the randomly selected channels separately to obtain the test results for each channel. If they are all different, then all channels of the platform product will be tested separately to obtain the test results corresponding to each channel.

2. The multi-channel platform product testing method as described in claim 1, characterized in that, The system architecture type includes a first system architecture type, and the platform product corresponding to the first system architecture type includes a business application, and the business application corresponds to multiple channels; The step of testing the platform product using the target testing strategy and obtaining test results includes: When the system architecture type of the platform product is the first system architecture type, all channels of the platform product are tested separately to obtain the test results corresponding to each channel.

3. The multi-channel platform product testing method as described in claim 1, characterized in that, The system architecture type includes a third system architecture type, and the platform product corresponding to the third system architecture type includes multiple business applications and channels corresponding to each of the business applications. The step of testing the platform product using the target testing strategy and obtaining test results includes: When the system architecture type of the platform product is the third system architecture type, the corresponding first channel is determined according to the first interface where the platform product is currently located; The first channel is tested, and the test results corresponding to the first channel are obtained.

4. The multi-channel platform product testing method as described in any one of claims 1-3, characterized in that, The test results include interface test results and API test results; The step of testing the platform product using the target testing strategy and obtaining test results includes: Based on the target testing strategy, determine the channels to be tested; A business request is initiated from the channel to be tested, the business request is processed through the platform product, and the corresponding response result is output. Obtain preset test rules, analyze the response results using the preset test rules, and obtain the interface test results corresponding to the platform product; The robustness, business logic, and interface flow of the interface corresponding to the channel to be tested are tested respectively to obtain the interface test results corresponding to the platform product.

5. The multi-channel platform product testing method as described in claim 4, characterized in that, The interface test results shall include at least robustness test results, business logic test results, and process test results; The step of testing the robustness, business logic, and interface flow of the interface corresponding to the channel to be tested, and obtaining the interface test results corresponding to the platform product, includes: By using preset robustness testing rules, the legal characters, field types, required fields, field lengths, and security policies in the interface of the channel under test are verified to obtain robustness test results. The preset business logic is converted into corresponding test data, and the interface of the channel to be tested is tested using the test data to obtain the business logic test results. Multiple process-related interfaces are combined to obtain a process interface group; The business logic of the process interface group is tested to obtain the process test results.

6. The multi-channel platform product testing method as described in claim 4, characterized in that, The test results also include database test results, which include at least the first database test results and the second database test results; The multi-channel platform product testing method also includes: During the interface testing process, the first database test result is generated by comparing the elements entered on the front end with the corresponding content in the database table. During the interface testing process, a second database test result is generated by comparing the interface request message with the corresponding database table content.

7. A multi-channel platform product testing device, the multi-channel platform product testing device comprising: The strategy determination module is used to determine the target testing strategy of the platform product based on the system architecture type of the platform product, wherein the system architecture type is used to characterize the correspondence between business applications and channels in the platform product; The product testing module is used to test the platform product using the target testing strategy and obtain test results. The product testing module is further configured to, when the system architecture type of the platform product is the second system architecture type, determine whether the message types and structures of each channel corresponding to the platform product are the same; if they are the same, test each of the randomly selected channels to obtain the test results corresponding to each channel; if they are different, test all channels of the platform product to obtain the test results corresponding to each channel. The system architecture type includes the second system architecture type, and the platform product corresponding to the second system architecture type includes multiple business applications with different priorities and multiple corresponding channels.

8. An electronic device, characterized in that, The electronic device includes: At least one processor; and, A memory communicatively linked to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor to enable the at least one processor to perform the steps of the multi-channel platform product testing method according to any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a program for implementing a multi-channel platform product testing method, the program for implementing the multi-channel platform product testing method being executed by a processor to implement the steps of the multi-channel platform product testing method as described in any one of claims 1 to 6.

Images