CN116361196A - Method, device and equipment for testing application flow and readable storage medium - Google Patents
Method, device and equipment for testing application flow and readable storage medium Download PDFInfo
- Publication number
- CN116361196A CN116361196A CN202310636357.8A CN202310636357A CN116361196A CN 116361196 A CN116361196 A CN 116361196A CN 202310636357 A CN202310636357 A CN 202310636357A CN 116361196 A CN116361196 A CN 116361196A
- Authority
- CN
- China
- Prior art keywords
- test
- data
- application
- configuration information
- report
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000012360 testing method Methods 0.000 title claims abstract description 309
- 238000000034 method Methods 0.000 title claims abstract description 114
- 238000003860 storage Methods 0.000 title claims abstract description 13
- 230000002159 abnormal effect Effects 0.000 claims abstract description 57
- 230000008569 process Effects 0.000 claims description 60
- 238000012795 verification Methods 0.000 claims description 31
- 238000012216 screening Methods 0.000 claims description 20
- 238000010511 deprotection reaction Methods 0.000 claims description 5
- 230000009191 jumping Effects 0.000 claims description 5
- 238000010998 test method Methods 0.000 claims description 5
- 238000004590 computer program Methods 0.000 claims description 3
- 230000000694 effects Effects 0.000 abstract description 6
- 230000006870 function Effects 0.000 description 23
- 238000004891 communication Methods 0.000 description 11
- 238000010586 diagram Methods 0.000 description 9
- 230000005856 abnormality Effects 0.000 description 7
- 238000013461 design Methods 0.000 description 6
- 238000001514 detection method Methods 0.000 description 4
- 230000009471 action Effects 0.000 description 3
- 238000013524 data verification Methods 0.000 description 3
- 238000004519 manufacturing process Methods 0.000 description 3
- 230000006399 behavior Effects 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000011664 signaling Effects 0.000 description 2
- 238000006467 substitution reaction Methods 0.000 description 2
- 230000003796 beauty Effects 0.000 description 1
- 238000011990 functional testing Methods 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 238000002372 labelling Methods 0.000 description 1
- 238000007726 management method Methods 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000004806 packaging method and process Methods 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 238000002360 preparation method Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3684—Test management for test design, e.g. generating new test cases
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3688—Test management for test execution, e.g. scheduling of test suites
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3692—Test management for test results analysis
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/08—Insurance
Abstract
The application provides a method, a device, equipment and a readable storage medium for testing an application flow, wherein the method comprises the steps of obtaining configuration information of an application product, wherein the configuration information comprises at least one of an application range, a factor affecting a rate, a payable strategy and a rate table; determining test data corresponding to factors affecting the rate in the configuration information; and checking the test data to obtain a test report of the test application flow, wherein the test report comprises a test result and abnormal data. The method can achieve the effect of accurately testing the application flow.
Description
Technical Field
The present application relates to the field of application flow testing, and in particular, to a method, apparatus, device, and readable storage medium for testing an application flow.
Background
At present, the testing method used in the testing and insuring process is mainly divided into functional testing, page design testing and interface automation testing, wherein the existing functional testing is manually performed, and the interface automation testing is mainly finished by data verification of a back-end interface.
The above-mentioned test method has a great limitation, and the existing functions are tested manually at a great cost, and the test error is easy to occur.
Therefore, how to accurately test the application flow is a technical problem to be solved.
Disclosure of Invention
The embodiment of the application aims to provide a method for testing an application flow, and the effect of accurately testing the application flow can be achieved through the technical scheme of the embodiment of the application.
In a first aspect, an embodiment of the present application provides a method for testing an application process, including obtaining configuration information of an application product, where the configuration information includes at least one of an applicable scope, a factor affecting a rate, a payable policy, and a rate table; determining test data corresponding to factors affecting the rate in the configuration information; and checking the test data to obtain a test report of the test application flow, wherein the test report comprises a test result and abnormal data.
In the embodiment, according to the configuration information of the insurance product, test data of some test insurance flows can be generated, and the test of the insurance flows through the configured test data can achieve the effect of accurately testing the insurance flows relative to the verification of the existing direct data of the back-end interface.
In some embodiments, determining test data corresponding to the rate influencing factor in the configuration information includes: collecting a plurality of combination data corresponding to different insurable ranges, payable strategies and tariffs in the historical insuring process; and screening data which influences the rate in the plurality of combined data to obtain test data.
In the embodiment, the configuration of different combinations can be performed on various configuration information to obtain different kinds of combination data, and the data with the influence on the rate in the combination data can be screened for testing the insurance process, so that the accuracy of the test result can be increased.
In some embodiments, verifying the test data to obtain a test report of the test application flow includes: reading test data and jumping to a corresponding login page; locating page elements within the landing page; in the process of application, detecting abnormal page elements in the page elements to obtain abnormal data; and generating a test report according to the abnormal data.
In the above embodiment, in the process of testing the application flow through the test data, the page element with the abnormal login page can be written into the detection report, and the function of detecting the abnormal data is added.
In some embodiments, verifying the test data to obtain a test report of the test application flow includes: reading the test data to complete the corresponding application flow; inquiring key inquiry data preset in the insurance application flow, wherein the key inquiry data comprises at least one of policy data, order data and payment plans; screening data which causes the application failure in the key query data to obtain abnormal data; and generating a test report according to the abnormal data.
In the above embodiment, in the process of testing the application flow through the test data, the application method can query the key data, actively test the abnormal data influencing the application flow, and add the function of detecting some key data.
In some embodiments, verifying the test data to obtain a test report of the test application flow includes: checking automatic renewal data in the test data, and performing one-time automatic renewal when the check is successful; when the verification fails, a test report is generated according to the reason of the failure.
In the above embodiment, when some test data of the automatic renewal are verified, the function of the automatic renewal can be realized or the reason that the automatic renewal cannot be performed is written into the report, so that the user can be notified of the reason for testing the abnormality.
In some embodiments, verifying the test data to obtain a test report of the test application flow includes: checking the manual renewal data in the test data, and performing deprotection on a successful preset number of users when the check is successful;
when the verification fails, a test report is generated according to the reason of the failure.
In the above embodiment, when some test data of the manual renewal are verified, the manual renewal function can be realized or the reason that the manual renewal cannot be performed is written into the report, so that the user can be notified of the reason that the abnormality is tested.
In some embodiments, verifying the test data to obtain a test report of the test application flow includes: screening second test data related to the insurable range in the test data; performing an application flow through the second test data to obtain payment information and application information; comparing the payment information and the application information with the expected payment information and the expected application information respectively to obtain a comparison result; screening abnormal data in the insurance application flow according to the comparison result;
and generating a test report according to the abnormal data.
In the above embodiment, the data related to the insurable range can be screened, the screened data is independently utilized to perform the test of the insurable process, the comparison can be performed according to the test result and the expected result, the screened abnormal data is written into the report, the function of detecting the abnormal data is increased, and the accuracy of the test of the insurable process is improved.
In a second aspect, an embodiment of the present application provides an apparatus for testing an application flow, including:
the system comprises an acquisition module, a verification module and a verification module, wherein the acquisition module is used for acquiring configuration information of an insurance application product, wherein the configuration information comprises at least one of an insurable range, a factor affecting a rate, a payable strategy and a rate table;
the determining module is used for determining test data corresponding to the factor affecting the rate in the configuration information;
and the verification test module is used for verifying the test data to obtain a test report of the test application flow, wherein the test report comprises a test result and abnormal data.
Optionally, the determining module is specifically configured to:
collecting a plurality of combination data corresponding to different insurable ranges, payable strategies and tariffs in the historical insuring process; and screening data which influences the rate in the plurality of combined data to obtain test data.
Optionally, the verification test module is specifically configured to:
reading test data and jumping to a corresponding login page; locating page elements within the landing page; in the process of application, detecting abnormal page elements in the page elements to obtain abnormal data; and generating a test report according to the abnormal data.
Optionally, the verification test module is specifically configured to:
reading the test data to complete the corresponding application flow; inquiring key inquiry data preset in the insurance application flow, wherein the key inquiry data comprises at least one of policy data, order data and payment plans; screening data which causes the application failure in the key query data to obtain abnormal data; and generating a test report according to the abnormal data.
Optionally, the verification test module is specifically configured to:
checking automatic renewal data in the test data, and performing one-time automatic renewal when the check is successful; when the verification fails, a test report is generated according to the reason of the failure.
Optionally, the verification test module is specifically configured to:
checking the manual renewal data in the test data, and performing deprotection on a successful preset number of users when the check is successful; when the verification fails, a test report is generated according to the reason of the failure.
Optionally, the verification test module is specifically configured to:
screening second test data related to the insurable range in the test data; performing an application flow through the second test data to obtain payment information and application information; comparing the payment information and the application information with the expected payment information and the expected application information respectively to obtain a comparison result; screening abnormal data in the insurance application flow according to the comparison result; and generating a test report according to the abnormal data.
In a third aspect, embodiments of the present application provide an electronic device comprising a processor and a memory storing computer readable instructions that, when executed by the processor, perform the steps of the method as provided in the first aspect above.
In a fourth aspect, embodiments of the present application provide a readable storage medium having stored thereon a computer program which when executed by a processor performs the steps of the method as provided in the first aspect above.
Additional features and advantages of the application will be set forth in the description which follows, and in part will be apparent from the description, or may be learned by practice of the embodiments of the application. The objectives and other advantages of the application will be realized and attained by the structure particularly pointed out in the written description and claims thereof as well as the appended drawings.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are needed in the embodiments of the present application will be briefly described below, it should be understood that the following drawings only illustrate some embodiments of the present application and should not be considered as limiting the scope, and other related drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a flow chart of a method for testing an application flow provided in an embodiment of the present application;
FIG. 2 is a flow chart of a method for implementing a test application flow provided in an embodiment of the present application;
FIG. 3 is a schematic block diagram of an apparatus for testing an application flow provided in an embodiment of the present application;
fig. 4 is a schematic structural diagram of an apparatus for testing an application flow according to an embodiment of the present application.
Detailed Description
The following description of the embodiments of the present application will be made clearly and completely with reference to the drawings in the embodiments of the present application, and it is apparent that the described embodiments are only some embodiments of the present application, not all embodiments. The components of the embodiments of the present application, as generally described and illustrated in the figures herein, may be arranged and designed in a wide variety of different configurations. Thus, the following detailed description of the embodiments of the present application, as provided in the accompanying drawings, is not intended to limit the scope of the application, as claimed, but is merely representative of selected embodiments of the application. All other embodiments, which can be made by those skilled in the art based on the embodiments of the present application without making any inventive effort, are intended to be within the scope of the present application.
It should be noted that: like reference numerals and letters denote like items in the following figures, and thus once an item is defined in one figure, no further definition or explanation thereof is necessary in the following figures. Meanwhile, in the description of the present application, the terms "first", "second", and the like are used only to distinguish the description, and are not to be construed as indicating or implying relative importance.
Some of the terms referred to in the embodiments of the present application will be described first to facilitate understanding by those skilled in the art.
Terminal equipment: the mobile terminal, stationary terminal or portable terminal may be, for example, a mobile handset, a site, a unit, a device, a multimedia computer, a multimedia tablet, an internet node, a communicator, a desktop computer, a laptop computer, a notebook computer, a netbook computer, a tablet computer, a personal communications system device, a personal navigation device, a personal digital assistant, an audio/video player, a digital camera/camcorder, a positioning device, a television receiver, a radio broadcast receiver, an electronic book device, a game device, or any combination thereof, including the accessories and peripherals of these devices, or any combination thereof. It is also contemplated that the terminal device can support any type of interface (e.g., wearable device) for the user, etc.
And (3) a server: the cloud server can be an independent physical server, a server cluster or a distributed system formed by a plurality of physical servers, and can also be a cloud server for providing cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, basic cloud computing services such as big data and artificial intelligent platforms and the like.
UI: the term "interface design" refers to the overall design of man-machine interaction, operation logic and interface beauty for software. UI designs are classified into entity UIs and virtual UIs, and UI designs commonly used in the internet are virtual UIs, i.e., short for User interfaces.
Sku: minimum Stock Keeping Unit (SKU), all known as Stock Keeping Unit, i.e., the base unit of inventory in and out metering, may be in units of pieces, boxes, trays, and the like. SKU is a necessary method for logistics management in large chain supermarkets DC (distribution center). Now, the product is called as a product unified numbering abbreviation, and each product is corresponding to a unique SKU number. Single product: a commodity may be referred to as a single product when any one of its brand, model, configuration, grade, suit, packaging capacity, unit, date of manufacture, shelf life, use, price, place of production, etc. is different from the other commodity.
The method and the device are applied to the scene of the application flow test, and the specific scene is that the test data are obtained by configuring configuration information of some application products, and the test of the application flow is completed according to the test data.
At present, the testing method used in the testing and insuring process is mainly divided into functional testing, page design (UI) testing and interface automation testing, wherein the existing functional testing is carried out manually, and the interface automation testing is mainly finished by data verification of a back-end interface. The above-mentioned test method has a great limitation, and the existing functions are tested manually at a great cost, and the test error is easy to occur.
For example, the functional test may be a test performed manually by a tester for business processes, boundary values, compatibility, availability, security, etc. UI automation mainly tests the directions of page interaction, jump, prompt, existing function regression and the like. The interface automation is mainly used for checking whether the rear-end interface is subjected to data checking, stability, robustness and interface monitoring.
For this purpose, the application obtains configuration information of the insurance product, wherein the configuration information comprises at least one of an insurable range, a factor affecting the rate, a payable strategy and a rate table; determining test data corresponding to factors affecting the rate in the configuration information; and checking the test data to obtain a test report of the test application flow, wherein the test report comprises a test result and abnormal data. According to configuration information of the insuring product, test data of some test insuring processes can be generated, and the effect of testing the insuring processes can be achieved accurately by testing the insuring processes through the configured test data relative to the existing direct verification of the data of the back-end interface.
In the embodiment of the present application, the execution body may be a test application flow device in a test application flow system, and in practical application, the test application flow device may be electronic devices such as a terminal device and a server, which is not limited herein.
The method of testing the application flow in the embodiment of the present application is described in detail below with reference to fig. 1.
Referring to fig. 1, fig. 1 is a flowchart of a method for testing an application flow according to an embodiment of the present application, where the method for testing an application flow shown in fig. 1 includes:
step 110: configuration information of the insurance product is obtained.
Wherein the configuration information includes at least one of an insurable scope, an influencing rate factor, a payable policy, and a rate table, and may further include information such as a number of insurable policies and insurable modes. The insurable range may include the age range, sex, presence or absence of social security, etc. of the insurable subject. The payment strategies include monthly payment, ji Fu and annual payment, etc. The rate table includes the rate at which the applicant pays for different insurance items and products, etc. Wherein the insurable range, the payable policy, and the tariff table may all be provided as rate-influencing phonemes, which may include any condition that can influence the rate, such as the applicant's age range, gender, and payment policy.
In one embodiment, obtaining configuration information for an application product includes: configuration information of the product is obtained according to a minimum stock keeping unit (Sku). The configuration information corresponding to the product can be obtained by taking the product as a unit.
Step 120: and determining test data corresponding to the factor affecting the rate in the configuration information.
The test data (case) may be any one or more data of the configuration information, or may be a combination data of different kinds of configuration information.
In some embodiments of the present application, determining test data corresponding to a factor affecting a rate in configuration information includes: collecting a plurality of combination data corresponding to different insurable ranges, payable strategies and tariffs in the historical insuring process; and screening data which influences the rate in the plurality of combined data to obtain test data.
In the process, different combinations of configuration information can be configured to obtain different kinds of combined data, and data with influences on the rate in the combined data can be screened for testing of the insurance application flow, so that the accuracy of a test result can be improved.
The combined data may be any two or more data combinations of the collected insurable range, the payable policy and the tariff table, or may be a combination of a plurality of data in one data of the collected insurable range, the payable policy and the tariff table. The test data includes some restrictive conditions input when the application flow is started, including condition information such as the applicable scope, the payable strategy and the rate.
Step 130: and checking the test data to obtain a test report of the test application flow.
Wherein the test report includes test results and exception data. The test results comprise the success of the application and the failure of the application, and the abnormal data comprise abnormal page elements of the login page, data which causes the failure of the application in the key inquiry data, data which causes the failure of the renewal in the automatic and manual renewal processes, any data which causes the failure of the application in the application process, and the like. In any test flow of insuring failure, the reasons of failure can be queried, the test data are rewritten and arranged according to the reasons of failure, and the test of the insuring flow is carried out again by utilizing the test data after arrangement.
In one embodiment, operation behaviors such as browsing, clicking and paying of a user can be simulated according to user behaviors in the process of testing the application flow, input test data is read, and the full-flow test of the business is performed through a system control true machine.
In some embodiments of the present application, verifying test data to obtain a test report of a test application flow includes: reading test data and jumping to a corresponding login page; locating page elements within the landing page; in the process of application, detecting abnormal page elements in the page elements to obtain abnormal data; and generating a test report according to the abnormal data.
In the process, in the process of testing the application flow through the test data, the page elements with the abnormal login page can be written into the detection report, and the function of detecting the abnormal data is added.
When the test data is read, the user jumps to the login page to complete the login process, and whether the login page is abnormal or not can be detected. The page elements may be some text, pictures, audio, animation, video, etc. in the landing page. Or executing script for displaying the above text pictures, audio, animation and video.
In some embodiments of the present application, verifying test data to obtain a test report of a test application flow includes: reading the test data to complete the corresponding application flow; inquiring key inquiry data preset in the insurance application flow, wherein the key inquiry data comprises at least one of policy data, order data and payment plans; screening data which causes the application failure in the key query data to obtain abnormal data; and generating a test report according to the abnormal data.
In the process, in the process of testing the application flow through the test data, the method can query the key data, actively test the abnormal data influencing the application flow, and increase the function of detecting some key data.
The key inquiry data can be set according to the requirements of the user and can be one or more of policy data, order data and payment plans.
In some embodiments of the present application, verifying test data to obtain a test report of a test application flow includes: checking automatic renewal data in the test data, and performing one-time automatic renewal when the check is successful; when the verification fails, a test report is generated according to the reason of the failure.
In the process, when some test data of the automatic renewal are verified, the function of the automatic renewal can be realized or the reasons incapable of being automatically renewed are written into the report, so that a user can be informed of testing the reasons of the abnormality.
The automatic fee renewal function can be realized or the reasons that the automatic fee renewal cannot be performed can be written into the report by checking some test data of the automatic fee renewal. After the data verification of the automatic renewal fee is passed, the automatic renewal fee can be automatically completed once. The method and the device can also set the deduction threshold, when the automatic renewal reaches a certain threshold, the deduction can be stopped, and the threshold can be set according to the user demand.
In some embodiments of the present application, verifying test data to obtain a test report of a test application flow includes: checking the manual renewal data in the test data, and performing deprotection on a successful preset number of users when the check is successful; when the verification fails, a test report is generated according to the reason of the failure.
In the process, when some test data of the manual renewal are verified, the manual renewal function can be realized or the reasons incapable of being manually renewed are written into the report, so that the user can be informed of testing the reasons of the abnormality.
The test data of the manual renewal can be verified, so that the manual renewal function can be realized or the reasons that the manual renewal cannot be performed can be written into the report. After the data of the manual renewal fee passes the verification, the user can be instructed to finish the manual renewal fee once. In addition, the corresponding flow test can be completed by simulating the flows of the user such as the disallowing and the refunding of the test data.
In some embodiments of the present application, verifying test data to obtain a test report of a test application flow includes: screening second test data related to the insurable range in the test data; performing an application flow through the second test data to obtain payment information and application information; comparing the payment information and the application information with the expected payment information and the expected application information respectively to obtain a comparison result; screening abnormal data in the insurance application flow according to the comparison result; and generating a test report according to the abnormal data.
According to the method and the device, in the process, the data related to the insurable range can be screened, the screened data is independently utilized to conduct the test of the insurable process, the comparison can be conducted according to the test result and the expected result, the screened abnormal data is written into the report, the function of abnormal data detection is increased, and the accuracy of the insurable process test is improved.
The second detection data may be range limitation data such as an insurance crowd, an insurance age, an insurance time, and an insurance gender. The payment information and the application information may be the result of the test and may include information such as success or failure of the payment, success or failure of the application, etc. The expected payment information and the expected application information may be compared to test results, and may also include information such as success or failure of payment, success or failure of application, and the like.
In the process shown in fig. 1, the present application obtains configuration information of an insurance product, where the configuration information includes at least one of an insurable range, a factor affecting a rate, a payable policy, and a rate table; determining test data corresponding to factors affecting the rate in the configuration information; and checking the test data to obtain a test report of the test application flow, wherein the test report comprises a test result and abnormal data. According to configuration information of the insuring product, test data of some test insuring processes can be generated, and the effect of testing the insuring processes can be achieved accurately by testing the insuring processes through the configured test data relative to the existing direct verification of the data of the back-end interface.
The following describes in detail the implementation method of the test application procedure according to the embodiment of the present application with reference to fig. 2.
Referring to fig. 2, fig. 2 is a flowchart of a method for implementing a test application process according to an embodiment of the present application, where the method for implementing a test application process shown in fig. 2 includes:
step 201: and (5) issuing a product.
Specific: a specific release product is selected.
Step 202: and judging the release environment.
Specific: judging the release environment of the current release product, if the release environment is the production environment, entering step 203, and if the release environment is the test environment, entering step 205.
Step 203: the test environment is compared with the on-line data configuration.
Specific: the configuration information in the test environment is compared with the configuration information stored on line, and the configuration information comprises information such as an insurable range, factors affecting the rate, payable strategies, rate tables and the like.
Step 204: and sending a data comparison report.
Specific: labeling the same and different parts obtained by comparison, and generating a corresponding comparison report to be fed back to the user.
Step 205: and obtaining product configuration information.
Specific: information such as the insurable range of the current insurable product, factors affecting the rate, payable strategies, rate tables and the like is obtained.
Step 206: test data is obtained.
Specific: and determining test data corresponding to the factor affecting the rate in the configuration information.
Step 207: the test data is read.
Specific: and inputting the read test data, and performing preparation work of the application flow test.
Step 208: and testing whether the flow is successful.
Specific: when the test flow is completed, the process proceeds to step 209, and when the test flow is not completed, the process proceeds to step 210.
Step 209: and performing corresponding insuring operation.
Specific: corresponding automatic and manual payment operation, renewal, refund, and deshield operation are performed.
Step 210: and outputting a test report.
Specific: writing the information such as the application abnormality, the data abnormality or the operation abnormality in the application flow into the test report.
In addition, the specific steps and methods shown in fig. 2 can refer to the methods shown in fig. 1, and are not described in detail herein.
The foregoing describes a method of testing an application flow through FIG. 1, and the apparatus of testing an application flow is described below in conjunction with FIGS. 3-4.
Referring to fig. 3, a schematic block diagram of an apparatus 300 for testing an application flow provided in an embodiment of the present application, where the apparatus 300 may be a module, a program segment, or code on an electronic device. The apparatus 300 corresponds to the embodiment of the method of fig. 1 described above, and is capable of performing the steps involved in the embodiment of the method of fig. 1. Specific functions of the apparatus 300 will be described below, and detailed descriptions thereof will be omitted herein as appropriate to avoid redundancy.
Optionally, the apparatus 300 includes:
an acquisition module 310 for acquiring configuration information of the insurance product, wherein the configuration information includes at least one of an insurable range, a factor affecting a rate, a payable policy, and a rate table;
a determining module 320, configured to determine test data corresponding to the factor affecting the rate in the configuration information;
and the verification test module 330 is configured to verify the test data to obtain a test report of the test application process, where the test report includes a test result and abnormal data.
Optionally, the determining module is specifically configured to:
collecting a plurality of combination data corresponding to different insurable ranges, payable strategies and tariffs in the historical insuring process; and screening data which influences the rate in the plurality of combined data to obtain test data.
Optionally, the verification test module is specifically configured to:
reading test data and jumping to a corresponding login page; locating page elements within the landing page; in the process of application, detecting abnormal page elements in the page elements to obtain abnormal data; and generating a test report according to the abnormal data.
Optionally, the verification test module is specifically configured to:
reading the test data to complete the corresponding application flow; inquiring key inquiry data preset in the insurance application flow, wherein the key inquiry data comprises at least one of policy data, order data and payment plans; screening data which causes the application failure in the key query data to obtain abnormal data; and generating a test report according to the abnormal data.
Optionally, the verification test module is specifically configured to:
checking automatic renewal data in the test data, and performing one-time automatic renewal when the check is successful; when the verification fails, a test report is generated according to the reason of the failure.
Optionally, the verification test module is specifically configured to:
checking the manual renewal data in the test data, and performing deprotection on a successful preset number of users when the check is successful; when the verification fails, a test report is generated according to the reason of the failure.
Optionally, the verification test module is specifically configured to:
screening second test data related to the insurable range in the test data; performing an application flow through the second test data to obtain payment information and application information; comparing the payment information and the application information with the expected payment information and the expected application information respectively to obtain a comparison result; screening abnormal data in the insurance application flow according to the comparison result; and generating a test report according to the abnormal data.
Referring to fig. 4, a schematic structural diagram of an apparatus for testing an application flow according to an embodiment of the present application may include a memory 410 and a processor 420. Optionally, the apparatus may further include: a communication interface 430 and a communication bus 440. The apparatus corresponds to the embodiment of the method of fig. 1 described above, and is capable of performing the steps involved in the embodiment of the method of fig. 1, and specific functions of the apparatus may be found in the following description.
In particular, the memory 410 is used to store computer readable instructions.
The processor 420, which processes the readable instructions stored in the memory, is capable of performing the various steps in the method of fig. 1.
A communication bus 440 for enabling direct connection communication of the above-described components.
The communication interface 430 of the device in the embodiment of the present application is used for performing signaling or data communication with other node devices. The memory 410 may be a high-speed RAM memory or a non-volatile memory (non-volatile memory), such as at least one disk memory. Memory 410 may also optionally be at least one storage device located remotely from the aforementioned processor. The memory 410 has stored therein computer readable instructions which, when executed by the processor 420, perform the method process described above in fig. 1. Processor 420 may be used on apparatus 300 and to perform the functions herein. By way of example, the processor 420 described above may be a general purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), an off-the-shelf programmable gate array (Field Programmable Gate Array, FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components, and the embodiments are not limited in this regard.
Embodiments of the present application also provide a readable storage medium, which when executed by a processor, performs a method process performed by an electronic device in the method embodiment shown in fig. 1.
It will be clear to those skilled in the art that, for convenience and brevity of description, reference may be made to the corresponding procedure in the foregoing method for the specific working procedure of the apparatus described above, and this will not be repeated here.
In summary, the embodiments of the present application provide a method, an apparatus, an electronic device, and a readable storage medium for testing an application process, where the method includes obtaining configuration information of an application product, where the configuration information includes at least one of an applicable range, a factor affecting a rate, a payable policy, and a rate table; determining test data corresponding to factors affecting the rate in the configuration information; and checking the test data to obtain a test report of the test application flow, wherein the test report comprises a test result and abnormal data. The method can achieve the effect of accurately testing the application flow.
In the several embodiments provided in this application, it should be understood that the disclosed apparatus and method may be implemented in other manners as well. The apparatus embodiments described above are merely illustrative, for example, flow diagrams and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of apparatus, methods and computer program products according to various embodiments of the present application. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
In addition, the functional modules in the embodiments of the present application may be integrated together to form a single part, or each module may exist alone, or two or more modules may be integrated to form a single part.
The functions, if implemented in the form of software functional modules and sold or used as a stand-alone product, may be stored in a computer-readable storage medium. Based on such understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution, in the form of a software product stored in a storage medium, including several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), a magnetic disk, or an optical disk, or other various media capable of storing program codes.
The foregoing is merely exemplary embodiments of the present application and is not intended to limit the scope of the present application, and various modifications and variations may be suggested to one skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principles of the present application should be included in the protection scope of the present application. It should be noted that: like reference numerals and letters denote like items in the following figures, and thus once an item is defined in one figure, no further definition or explanation thereof is necessary in the following figures.
The foregoing is merely specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily think about changes or substitutions within the technical scope of the present application, and the changes and substitutions are intended to be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.
It is noted that relational terms such as first and second, and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Moreover, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
Claims (10)
1. A method of testing an application process, comprising:
acquiring configuration information of an insurance product, wherein the configuration information comprises at least one of an insurable range, a factor affecting a rate, a payable strategy and a rate table;
determining test data corresponding to the factor affecting the rate in the configuration information;
and verifying the test data to obtain a test report of the test application flow, wherein the test report comprises a test result and abnormal data.
2. The method of claim 1, wherein determining test data corresponding to the rate-affecting factor in the configuration information comprises:
collecting a plurality of different combined data corresponding to the insurable range, the payable policy and the tariff table in a historical insuring process;
and screening data which influences the rate in the plurality of combined data to obtain the test data.
3. The method according to claim 1 or 2, wherein the verifying the test data to obtain a test report of a test application process includes:
reading the test data and jumping to a corresponding login page;
positioning page elements in the login page;
in the process of application, detecting abnormal page elements in the page elements to obtain the abnormal data;
and generating the test report according to the abnormal data.
4. The method according to claim 1 or 2, wherein the verifying the test data to obtain a test report of a test application process includes:
reading the test data to complete a corresponding application flow;
inquiring key inquiry data preset in the insurance application flow, wherein the key inquiry data comprises at least one of insurance policy data, order data and payment plans;
screening data which causes the application failure in the key query data to obtain the abnormal data;
and generating the test report according to the abnormal data.
5. The method according to claim 1 or 2, wherein the verifying the test data to obtain a test report of a test application process includes:
checking the automatic renewal data in the test data, and performing one-time automatic renewal when the check is successful;
and when the verification fails, generating the test report according to the reason of the failure.
6. The method according to claim 1 or 2, wherein the verifying the test data to obtain a test report of a test application process includes:
checking the manual renewal data in the test data, and performing deprotection on a preset number of successful users when the check is successful;
and when the verification fails, generating the test report according to the reason of the failure.
7. The method according to claim 1 or 2, wherein the verifying the test data to obtain a test report of a test application process includes:
screening second test data related to the insurable range in the test data;
performing an application flow through the second test data to obtain payment information and application information;
comparing the payment information and the application information with expected payment information and expected application information respectively to obtain a comparison result;
screening the abnormal data appearing in the application process according to the comparison result;
and generating the test report according to the abnormal data.
8. An apparatus for testing an application process, comprising:
the system comprises an acquisition module, a verification module and a verification module, wherein the acquisition module is used for acquiring configuration information of an insurance application product, wherein the configuration information comprises at least one of an insurable range, a factor affecting a rate, a payable strategy and a rate table;
the determining module is used for determining test data corresponding to the factor affecting the rate in the configuration information;
and the verification test module is used for verifying the test data to obtain a test report of the test application flow, wherein the test report comprises a test result and abnormal data.
9. An electronic device, comprising:
a memory and a processor, the memory storing computer readable instructions that, when executed by the processor, perform the steps in the method of any of claims 1-7.
10. A computer-readable storage medium, comprising:
computer program which, when run on a computer, causes the computer to perform the method according to any of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310636357.8A CN116361196A (en) | 2023-06-01 | 2023-06-01 | Method, device and equipment for testing application flow and readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310636357.8A CN116361196A (en) | 2023-06-01 | 2023-06-01 | Method, device and equipment for testing application flow and readable storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN116361196A true CN116361196A (en) | 2023-06-30 |
Family
ID=86905328
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310636357.8A Pending CN116361196A (en) | 2023-06-01 | 2023-06-01 | Method, device and equipment for testing application flow and readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116361196A (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9037919B1 (en) * | 2014-04-18 | 2015-05-19 | State Farm Mutual Automobile Insurance Company | Systems and methods for supporting a testing environment for a website |
| CN107704396A (en) * | 2017-10-20 | 2018-02-16 | 平安科技（深圳）有限公司 | The method of testing and device of application program |
| CN113609011A (en) * | 2021-07-30 | 2021-11-05 | 建信金融科技有限责任公司 | Method, device, medium and equipment for testing insurance product factory |
| CN114170032A (en) * | 2022-02-11 | 2022-03-11 | 北京优全智汇信息技术有限公司 | Insurance product online method and device, electronic equipment and storage medium |
| CN115373976A (en) * | 2022-01-18 | 2022-11-22 | 平安健康保险股份有限公司 | Insurance testing method and device, computer equipment and storage medium |
-
2023
- 2023-06-01 CN CN202310636357.8A patent/CN116361196A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9037919B1 (en) * | 2014-04-18 | 2015-05-19 | State Farm Mutual Automobile Insurance Company | Systems and methods for supporting a testing environment for a website |
| CN107704396A (en) * | 2017-10-20 | 2018-02-16 | 平安科技（深圳）有限公司 | The method of testing and device of application program |
| CN113609011A (en) * | 2021-07-30 | 2021-11-05 | 建信金融科技有限责任公司 | Method, device, medium and equipment for testing insurance product factory |
| CN115373976A (en) * | 2022-01-18 | 2022-11-22 | 平安健康保险股份有限公司 | Insurance testing method and device, computer equipment and storage medium |
| CN114170032A (en) * | 2022-02-11 | 2022-03-11 | 北京优全智汇信息技术有限公司 | Insurance product online method and device, electronic equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US7730123B1 (en) | Software application implemented using services from a services repository generated using a target services roadmap | |
| CN112100052B (en) | Playback method and device of interface test scene | |
| CN109726105A (en) | Test data building method, device, equipment and storage medium | |
| CN111126019B (en) | Report generation method and device based on mode customization and electronic equipment | |
| US9804916B2 (en) | Integrated production support | |
| CN106487603A (en) | A kind of response test method and device | |
| CN110990274A (en) | Data processing method, device and system for generating test case | |
| CN104579909A (en) | Method and equipment for classifying user information and acquiring user grouping information | |
| CN115328759A (en) | Form verification method and device | |
| US11928100B2 (en) | Method and system for creating a unified data repository | |
| US20210026616A1 (en) | Automated bucket policy management arrangements | |
| CN110018819B (en) | Data checking script generation method, device and equipment | |
| CN112286790B (en) | Full link testing method, device, equipment and storage medium | |
| Royer | Software testing management: life on the critical path | |
| CN113408254A (en) | Page form information filling method, device, equipment and readable medium | |
| US20140012830A1 (en) | Data verification system | |
| CN116361196A (en) | Method, device and equipment for testing application flow and readable storage medium | |
| CN111144987A (en) | Abnormal shopping behavior limiting method, limiting assembly and shopping system | |
| CN110059087A (en) | Data attribute identification method, device and equipment in a kind of piece of chain type account book | |
| CN109857450A (en) | A kind of verification service orchestration method and device | |
| CN112230938B (en) | Method and device for configuring rental products of industrial Internet | |
| TW201423620A (en) | System and method for checking patent fees | |
| CN107992749A (en) | A kind of method and device for detecting patch packet conflict | |
| CN112860722A (en) | Data checking method and device, electronic equipment and readable storage medium | |
| CN115437903A (en) | Interface test method, device, apparatus, storage medium, and program |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20230630 |
|
| RJ01 | Rejection of invention patent application after publication |