CN112380113A - Software testing method and system - Google Patents
Software testing method and system Download PDFInfo
- Publication number
- CN112380113A CN112380113A CN202011104218.3A CN202011104218A CN112380113A CN 112380113 A CN112380113 A CN 112380113A CN 202011104218 A CN202011104218 A CN 202011104218A CN 112380113 A CN112380113 A CN 112380113A
- Authority
- CN
- China
- Prior art keywords
- data
- interface
- province
- database
- json
- 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.)
- Granted
Links
- 238000013522 software testing Methods 0.000 title claims abstract description 45
- 238000000034 method Methods 0.000 title claims abstract description 33
- 238000012360 testing method Methods 0.000 claims abstract description 38
- 230000009471 action Effects 0.000 claims description 7
- 230000008569 process Effects 0.000 claims description 3
- 230000004044 response Effects 0.000 claims description 3
- 230000006870 function Effects 0.000 description 3
- 238000010586 diagram Methods 0.000 description 2
- 230000000694 effects Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000004088 simulation Methods 0.000 description 1
- 238000010998 test 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/3664—Environments for testing or debugging software
-
- 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
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
- G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
- G06F3/0484—Interaction techniques based on graphical user interfaces [GUI] for the control of specific functions or operations, e.g. selecting or manipulating an object, an image or a displayed text element, setting a parameter value or selecting a range
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Human Computer Interaction (AREA)
- Debugging And Monitoring (AREA)
Abstract
The invention discloses a software testing method and a system, wherein the software testing method comprises the following steps: acquiring json file data of a map graphical interface; acquiring data returned by a back-end database through an interface call request; and comparing the json file data of the map graphical interface with data returned from the back-end database, and judging whether the json file data are matched with the data returned from the back-end database to obtain a test result. The software testing method and the software testing system provided by the invention can improve the testing efficiency and the testing accuracy and ensure the correctness and the accuracy of data display.
Description
Technical Field
The invention belongs to the technical field of software testing, relates to a testing system, and particularly relates to a software testing method and system.
Background
In a software project, in order to ensure the correctness of data display in software, the correctness of the displayed data needs to be ensured by combining a front end with database data in a test environment, and the correctness and consistency of the data play a crucial role in the work of the whole big data display system.
And manually clicking the map data displayed in the software to check the accuracy of the map province level data jump. In general, existing software testing needs a large number of testers to complete, data in a map has strong logic and a hierarchical relationship, front-end UI display needs to correspond to a back-end database one by one, and the efficiency of the manual testing method is low. And the data volume in the provincial and urban areas is very large, so that the missing test risk exists in the manual work, and the test accuracy cannot be ensured.
In view of the above, there is a need to design a new software testing method to overcome at least some of the above-mentioned shortcomings of the existing software testing methods.
Disclosure of Invention
The invention provides a software testing method and system, which can improve the testing efficiency and the testing accuracy and ensure the correctness and the accuracy of data display.
In order to solve the technical problem, according to one aspect of the present invention, the following technical solutions are adopted:
a software testing method, the software testing method comprising:
step S1, adding an HTTP request nationwide interface in a test tool, extracting all provinces in a return value of a background by using a regular expression in a post processor, adding a response assertion in the assertion to judge whether a province with a first identifier of 0 exists, wherein the province with the first identifier of 0 is error data in a database; then adding assertion to judge whether the total number of the elevators is 0, wherein the data with the total number of the elevators of 0 represents that no equipment is used in the region;
step S2, when province data is requested, a circular logic controller in the logic controller is used, a province json file interface is added under the logic controller, and first identifications of all provinces extracted from national interface return values are used as json parameters of the request to carry out circular traversal;
adding http request province interface data, and performing interface request by using a first identifier of province in national return data as a request parameter; extracting all market background data in the return value of the background by using a regular expression in a post processor, and judging and finding out data with a first identifier of 0 and data with a total number of elevators of 0;
step S3, when city data is requested, a circular logic controller in the logic controller is used, a city json file interface is added under the logic controller, and first identifications of all cities extracted from province interface return values are used as json parameters of the request to be circularly traversed;
adding http request city interface data, and using a first identifier in city in provincial interface return data as a request parameter to carry out interface request; extracting all background data assertions in the return value of the background by using a regular expression in a post processor, and judging to find out data with a first identifier of 0 and data with a total number of elevators of 0;
step S4, when the data in the area is requested, a circular logic controller in the logic controller is used, an area json file interface is added under the logic controller, and the first identifications of all areas extracted from the city interface return value are used as the json parameters of the request to be circularly traversed;
step S5, after zone data are obtained, elevator information to be tested is obtained through street selection, cell selection and elevator individual selection in sequence;
and step S6, displaying the corresponding data content according to the selected elevator.
According to another aspect of the invention, the following technical scheme is adopted: a software testing method, the software testing method comprising:
acquiring file data of a map graphical interface;
acquiring data returned by a back-end database through an interface call request; and
and comparing the file data of the map graphical interface with the data returned from the back-end database, and judging whether the file data is matched with the data returned from the back-end database to obtain a test result.
As an implementation mode of the invention, the data returned by the back-end database is acquired by requesting the back-end interface data through simulating the manual click interface operation.
As an embodiment of the present invention, the step of obtaining data returned by the back-end database through the interface call request includes:
requesting a national interface; extracting province first identifications from return values of national interfaces from a background database to serve as first identifications of json files of an interface UI map, and calling and traversing all the json files of provinces through json file interfaces, so that clicking actions on the UI map are manually operated in an interface request mode;
requesting a provincial interface; traversing the first identifications of the province, obtaining first identifications of the cities from the return values, and calling json files for traversing all the cities through json file interfaces;
requesting a city interface; and traversing the first identifications of the cities, obtaining the first identifications of the regions from the return values, and calling json files traversing all the counties through json file interfaces.
As an embodiment of the present invention, the test method further includes: an interface testing step; and adding a post extractor regular expression to extract all return values, and then adding a circulating logic controller to perform logic traversal on all the extracted return values, namely, traversing all cities contained in each province in the database and all areas contained in all cities in the province, so as to realize logic traversal of data.
As an embodiment of the present invention, the step of comparing comprises: corresponding data of a json file on the UI map by data returned by a back-end database, adding assertions in each interface needing to extract the first identifier, wherein the assertions comprise assertions of which the first identifier is not 0, and checking error data in the database; and if the interface request reports an error, namely the data returned by the back-end database is not matched with the map data displayed by the front-end map graphical interface, generating a test report, and reporting the detailed direction of the positioned bug.
According to another aspect of the invention, the following technical scheme is adopted: a software testing system, the software testing system comprising:
the map graphical interface data acquisition module is used for acquiring file data of a map graphical interface;
the database data acquisition module is used for acquiring data returned by the back-end database through an interface call request; and
and the comparison module is used for comparing the file data of the map graphical interface with the data returned from the back-end database, judging whether the file data is matched with the data, and obtaining a test result.
As an embodiment of the present invention, the database data obtaining module includes an interface request unit, configured to implement the following processes:
requesting a national interface; extracting province first identifications from return values of national interfaces from a background database to serve as first identifications of json files of an interface UI map, and calling and traversing all the json files of provinces through json file interfaces, so that clicking actions on the UI map are manually operated in an interface request mode;
requesting a provincial interface; traversing the first identifications of the province, obtaining first identifications of the cities from the return values, and calling json files for traversing all the cities through json file interfaces;
requesting a city interface; and traversing the first identifications of the cities, obtaining the first identifications of the regions from the return values, and calling json files traversing all the counties through json file interfaces.
As an embodiment of the present invention, the database data acquisition module includes an interface test unit, which is used to add a post-extractor regular expression to extract all return values, and then add a circular logic controller to perform a logical traversal on all the extracted return values, that is, to traverse all cities included in each province in the database, and all regions included in all cities in the province, so as to implement a logical traversal of data.
As an implementation manner of the present invention, the comparison module is configured to correspond to data of a json file on a UI map through data returned by a back-end database, and add an assertion to each interface that needs to extract a first identifier, where the assertion includes an assertion that the first identifier is not 0, to check error data in the database; and if the interface request reports an error, namely the data returned by the back-end database is not matched with the map data displayed by the front-end map graphical interface, generating a test report, and reporting the detailed direction of the positioned bug.
The invention has the beneficial effects that: the software testing method and the software testing system provided by the invention can improve the testing efficiency and the testing accuracy and ensure the correctness and the accuracy of data display.
Drawings
FIG. 1 is a flowchart illustrating a software testing method according to an embodiment of the present invention.
FIG. 2 is a flowchart illustrating a software testing method according to an embodiment of the present invention.
FIG. 3 is a block diagram of a software testing system according to an embodiment of the present invention.
Detailed Description
Preferred embodiments of the present invention will be described in detail below with reference to the accompanying drawings.
For a further understanding of the invention, reference will now be made to the preferred embodiments of the invention by way of example, and it is to be understood that the description is intended to further illustrate features and advantages of the invention, and not to limit the scope of the claims.
The description in this section is for several exemplary embodiments only, and the present invention is not limited only to the scope of the embodiments described. It is within the scope of the present disclosure and protection that the same or similar prior art means and some features of the embodiments may be interchanged.
The steps in the embodiments in the specification are only expressed for convenience of description, and the implementation manner of the present application is not limited by the order of implementation of the steps.
The invention discloses a software testing method, and FIG. 1 is a flow chart of the software testing method according to an embodiment of the invention; referring to fig. 1, the software testing method includes:
step 1, acquiring file data of a map graphical interface;
and 3, comparing the file data of the map graphical interface with the data returned from the back-end database, and judging whether the file data is matched with the data returned from the back-end database to obtain a test result.
The invention uses a testing tool to realize that the manual click interface circularly traverses all data of national provincial regions by connecting single provincial region interfaces in series and combining a circular (foreach) logic circulator.
In one embodiment, the file data may be json file data, which may contain the name of the province and city of the whole country, the number of elevators, and the first identification code. The code of the province and the city is unique and is not 0, and the assertion is used for judging that the code in the database cannot be 0; when the code is 0, it is described that the data has a problem as erroneous data.
In an embodiment of the present invention, in step 2, a request is made for the data of the back-end interface by simulating a manual click interface operation, so as to obtain the data returned by the back-end database. In one embodiment, the request simulation front end simulates a corresponding click action of the display data on the map graphical interface through the interface call.
In an embodiment of the present invention, the step of obtaining the data returned by the back-end database through the interface call request includes:
requesting a national interface; extracting a province first identification code from a return value of a national interface from a background database to serve as a first identification code of a json file of an interface UI map, and calling and traversing json files of all provinces through the json file interface so as to realize a click action on a manually operated UI map in an interface request mode;
requesting a provincial interface; traversing the province codes, obtaining codes of cities from return values, and calling json files traversing all cities through json file interfaces;
requesting a city interface; and traversing the code of the city, obtaining the code of the city from the return value, and calling json files traversing all the counties through a json file interface.
In an embodiment of the present invention, the testing method further includes: an interface testing step; and adding a post extractor regular expression to extract all return values, and then adding a circulation (foreach) logic controller to perform logic traversal on all the extracted return values, namely, traversing all cities contained in each province in a database and all areas contained in all cities in the province, so as to realize logic traversal of data.
In an embodiment of the present invention, step 3 further includes: corresponding data of a json file on the UI map by data returned by a back-end database, adding assertions in each interface needing extracting the code, wherein the assertions comprise assertions of which the code is not 0, and checking error data in the database; and if the interface request reports errors, namely the data returned by the back-end database is not matched with the map data displayed by the front-end map graphical interface, generating a test report, and positioning the direction of errors (bugs) in detail in the report.
FIG. 2 is a flowchart of a software testing method according to an embodiment of the present invention; referring to fig. 2, in an embodiment of the invention, the software testing method includes:
step S1, adding an HTTP request nationwide interface in a meter (test tool), extracting all provinces in a return value of a background by using a regular expression in a post processor, and judging whether a province with code 0 exists by adding response assertion in an assertion, wherein the province with code 0 is error data in a database; then adding assertion to judge whether the total number count of the elevators is 0 or not, wherein the data of the total number count of the elevators which is 0 represents that no equipment is used in the area;
step S2, when province data is requested, a circular logic controller in the logic controller is used, a province json file interface is added under the logic controller, and all province codes extracted from the national interface return value are used as json parameters of the request to be circularly traversed;
adding http request province interface data, and performing interface request by using province codes in national return data as request parameters; extracting all market background data in the return value of the background by using a regular expression in a post processor, and judging and finding out data with a code of 0 and data with a total number count of 0 of the elevator;
step S3, when city data is requested, adding a city json file interface under a logic controller by using a circulating logic controller in the logic controller, and circularly traversing all city codes extracted from provincial interface return values as requested json parameters;
adding http request city interface data, and using city code in province interface return data as a request parameter to carry out interface request; extracting all background data assertions in the return value of the background by using a regular expression in a post processor, judging and finding out data with code of 0 and data with the total number of elevators of 0;
and step S4, when the region data is requested, adding a region json file interface under the logic controller by using a circulating logic controller in the logic controller, and circularly traversing all region codes extracted from city interface return values as the json parameters of the request.
And step S5, after zone data are obtained, the elevator information to be tested is obtained through street selection, cell selection and elevator individual selection in sequence.
And step S6, displaying the corresponding data content according to the selected elevator.
In one embodiment of the present invention, the selection of the elevator level may be performed in other manners, and does not necessarily need to be performed in a manner of administrative division.
FIG. 3 is a schematic diagram illustrating a software testing system according to an embodiment of the present invention; referring to fig. 3, the software testing system includes: the map graphic interface data acquisition module 1, the database data acquisition module 2 and the comparison module 3.
The map graphical interface data acquisition module 1 is used for acquiring file data of a map graphical interface; the database data acquisition module 2 is used for acquiring data returned by the back-end database through an interface call request; the comparison module 3 is used for comparing the json file data of the map graphical interface with the data returned from the back-end database, judging whether the json file data is matched with the data returned from the back-end database, and obtaining a test result.
In an embodiment, the database data obtaining module 2 requests the backend interface data by simulating a manual click interface operation, and obtains data returned by the backend database.
In an embodiment of the present invention, the database data obtaining module 2 includes an interface request unit, configured to implement the following processes:
requesting a national interface; extracting province codes from return values of national interfaces from a background database to serve as json file codes of an interface UI map, calling and traversing json files of all provinces through the json file interfaces, and achieving clicking actions on the UI map manually in an interface request mode;
requesting a provincial interface; traversing the province codes, obtaining codes of cities from return values, and calling json files traversing all cities through json file interfaces;
requesting a city interface; and traversing the code of the city, obtaining the code of the city from the return value, and calling json files traversing all the counties through a json file interface.
In an embodiment of the present invention, the database data obtaining module 2 includes an interface testing unit, configured to add a post-extractor regular expression to extract all return values, and add a circular logic controller to perform a logical traversal on all the extracted return values, that is, to traverse all cities included in each province in the database and all regions included in all cities in the province, so as to implement a logical traversal of data.
In an embodiment of the present invention, the comparison module 3 is configured to correspond to data of a json file on a UI map through data returned by a back-end database, and add an assertion to each interface that needs to extract a code, where the assertion includes an assertion that the code is not 0, to check for erroneous data in the database; and if the interface request reports an error, namely the data returned by the back-end database is not matched with the map data displayed by the front-end map graphical interface, generating a test report, and reporting the detailed direction of the positioned bug.
In one embodiment, the software testing system may include an elevator information display module to display the setting information for the selected elevator. The selected elevator can pass through the country, province, city, district, street (or village), residence committee (or village), and cell in sequence, so as to obtain the corresponding elevator.
In summary, the software testing method and system provided by the invention can improve the testing efficiency and the testing accuracy, and ensure the correctness and accuracy of data display.
It should be noted that the present application may be implemented in software and/or a combination of software and hardware; for example, it may be implemented using Application Specific Integrated Circuits (ASICs), general purpose computers, or any other similar hardware devices. In some embodiments, the software programs of the present application may be executed by a processor to implement the above steps or functions. As such, the software programs (including associated data structures) of the present application can be stored in a computer-readable recording medium; such as RAM memory, magnetic or optical drives or diskettes, and the like. In addition, some steps or functions of the present application may be implemented using hardware; for example, as circuitry that cooperates with the processor to perform various steps or functions.
The technical features of the embodiments described above may be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the embodiments described above are not described, but should be considered as being within the scope of the present specification as long as there is no contradiction between the combinations of the technical features.
The description and applications of the invention herein are illustrative and are not intended to limit the scope of the invention to the embodiments described above. Effects or advantages referred to in the embodiments may not be reflected in the embodiments due to interference of various factors, and the description of the effects or advantages is not intended to limit the embodiments. Variations and modifications of the embodiments disclosed herein are possible, and alternative and equivalent various components of the embodiments will be apparent to those skilled in the art. It will be clear to those skilled in the art that the present invention may be embodied in other forms, structures, arrangements, proportions, and with other components, materials, and parts, without departing from the spirit or essential characteristics thereof. Other variations and modifications of the embodiments disclosed herein may be made without departing from the scope and spirit of the invention.
Claims (10)
1. A software testing method, characterized in that the software testing method comprises:
step S1, adding an HTTP request nationwide interface in a test tool, extracting all provinces in a return value of a background by using a regular expression in a post processor, adding a response assertion in the assertion to judge whether a province with a first identifier of 0 exists, wherein the province with the first identifier of 0 is error data in a database; then adding assertion to judge whether the total number of the elevators is 0, wherein the data with the total number of the elevators of 0 represents that no equipment is used in the region;
step S2, when province data is requested, a circular logic controller in the logic controller is used, a province json file interface is added under the logic controller, and first identifications of all provinces extracted from the national interface return value are used as json parameters of the request to be circularly traversed;
adding http request province interface data, and performing interface request by using a first identifier of province in national return data as a request parameter; extracting all market background data in the return value of the background by using a regular expression in a post processor, and judging and finding out data with a first identifier of 0 and data with a total number of elevators of 0;
step S3, when city data is requested, a circular logic controller in the logic controller is used, a city json file interface is added under the logic controller, and first identifications of all cities extracted from province interface return values are used as json parameters of the request to be circularly traversed;
adding http request city interface data, and using a first identifier in city in provincial interface return data as a request parameter to carry out interface request; extracting all background data assertions in the return value of the background by using a regular expression in a post processor, and judging to find out data with a first identifier of 0 and data with a total number of elevators of 0;
step S4, when data in the area are requested, a circular logic controller in the logic controller is used, an area json file interface is added under the logic controller, and first identifications of all areas extracted from city interface return values are used as requested json parameters to be circularly traversed;
step S5, after zone data are obtained, elevator information to be tested is obtained through street selection, cell selection and elevator individual selection in sequence;
and step S6, displaying the corresponding data content according to the selected elevator.
2. A software testing method, characterized in that the software testing method comprises:
acquiring file data of a map graphical interface;
acquiring data returned by a back-end database through an interface call request; and
and comparing the file data of the map graphical interface with the data returned from the back-end database, and judging whether the file data is matched with the data returned from the back-end database to obtain a test result.
3. The software testing method according to claim 2, characterized in that:
and requesting the data of the back-end interface by simulating the operation of a manual click interface to acquire the data returned by the back-end database.
4. The software testing method according to claim 2, characterized in that:
the step of acquiring the data returned by the back-end database through the interface call request comprises the following steps:
requesting a national interface; extracting province first identifications from return values of national interfaces from a background database to serve as interface UI map json file first identifications, calling and traversing all province json files through json file interfaces, and achieving clicking actions on a manual operation UI map in an interface request mode;
requesting a provincial interface; traversing the first identifications of the province, obtaining first identifications of the cities from the return values, and calling json files for traversing all the cities through json file interfaces;
requesting a city interface; and traversing the first identifier of the city, obtaining the first identifier of the city from the return value, and calling json files traversing all the counties through a json file interface.
5. The software testing method according to claim 4, wherein:
the testing method further comprises the following steps: an interface testing step; and adding a post extractor regular expression to extract all return values, and then adding a circulating logic controller to perform logic traversal on all the extracted return values, namely, traversing all cities contained in each province in the database and all areas contained in all cities in the province, so as to realize logic traversal of data.
6. The software testing method according to claim 5, wherein:
the comparison step comprises: corresponding data of a json file on the UI map by data returned by a back-end database, adding assertions in each interface needing to extract the first identifier, wherein the assertions comprise assertions of which the first identifier is not 0, and checking error data in the database; if the interface request reports errors, namely the data returned by the back-end database is not matched with the map data displayed by the front-end map graphical interface, a test report is generated, and the direction of the errors is positioned in detail in the report.
7. A software testing system, characterized in that the software testing system comprises:
the map graphical interface data acquisition module is used for acquiring file data of a map graphical interface;
the database data acquisition module is used for acquiring data returned by the back-end database through the interface calling request; and
and the comparison module is used for comparing the file data of the map graphical interface with the data returned from the back-end database, judging whether the file data is matched with the data, and obtaining a test result.
8. The software testing system of claim 7, wherein:
the database data acquisition module comprises an interface request unit and is used for realizing the following processes:
requesting a national interface; extracting province first identifications from return values of national interfaces from a background database to serve as first identifications of json files of an interface UI map, and calling and traversing all the json files of provinces through json file interfaces, so that clicking actions on the UI map are manually operated in an interface request mode;
requesting a provincial interface; traversing the first identifications of the province, obtaining first identifications of the cities from the return values, and calling json files for traversing all the cities through json file interfaces;
requesting a city interface; and traversing the first identifier of the city, obtaining the first identifier of the city from the return value, and calling json files traversing all the counties through a json file interface.
9. The software testing system of claim 8, wherein:
the database data acquisition module comprises an interface test unit which is used for adding a post extractor regular expression to extract all return values, and then adding a circulating logic controller to perform logic traversal on all the extracted return values, namely, all cities contained in each province in the database are traversed, all areas contained in all cities in the province are traversed, and the logic traversal of data is realized.
10. The software testing system of claim 7, wherein:
the comparison module is used for corresponding data of json files on the UI map through data returned by the back-end database, adding assertions in each interface needing to extract the first identification, wherein the assertions comprise assertions of which the first identification is not 0, and checking error data in the database; if the interface request reports errors, namely the data returned by the back-end database is not matched with the map data displayed by the front-end map graphical interface, a test report is generated, and the direction of the errors is positioned in detail in the report.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011104218.3A CN112380113B (en) | 2020-10-15 | 2020-10-15 | Software testing method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011104218.3A CN112380113B (en) | 2020-10-15 | 2020-10-15 | Software testing method and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112380113A true CN112380113A (en) | 2021-02-19 |
| CN112380113B CN112380113B (en) | 2024-05-17 |
Family
ID=74581543
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011104218.3A Active CN112380113B (en) | 2020-10-15 | 2020-10-15 | Software testing method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112380113B (en) |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8230325B1 (en) * | 2008-06-30 | 2012-07-24 | Amazon Technologies, Inc. | Structured document customizable comparison systems and methods |
| CN103927243A (en) * | 2013-01-15 | 2014-07-16 | 株式会社日立制作所 | Graphical user interface operation monitoring method and device |
| CN104423961A (en) * | 2013-09-11 | 2015-03-18 | 阿里巴巴集团控股有限公司 | Method and system for generating testing script |
| CN104516633A (en) * | 2014-11-19 | 2015-04-15 | 微梦创科网络科技（中国）有限公司 | User interface element management method and device |
| KR20160120896A (en) * | 2015-04-09 | 2016-10-19 | 엘에스산전 주식회사 | Apparatus for testing inverter parameters |
| CN106776280A (en) * | 2016-11-24 | 2017-05-31 | 上海携程商务有限公司 | Configurable performance test device |
| CN107273286A (en) * | 2017-06-02 | 2017-10-20 | 携程计算机技术（上海）有限公司 | For the scene automatic test platform and method of task application |
| CN108228443A (en) * | 2016-12-14 | 2018-06-29 | 北京国双科技有限公司 | A kind of test method and device of web applications |
| CN109101415A (en) * | 2018-06-25 | 2018-12-28 | 平安科技（深圳）有限公司 | Interface test method, system, equipment and the storage medium compared based on database |
-
2020
- 2020-10-15 CN CN202011104218.3A patent/CN112380113B/en active Active
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8230325B1 (en) * | 2008-06-30 | 2012-07-24 | Amazon Technologies, Inc. | Structured document customizable comparison systems and methods |
| CN103927243A (en) * | 2013-01-15 | 2014-07-16 | 株式会社日立制作所 | Graphical user interface operation monitoring method and device |
| CN104423961A (en) * | 2013-09-11 | 2015-03-18 | 阿里巴巴集团控股有限公司 | Method and system for generating testing script |
| CN104516633A (en) * | 2014-11-19 | 2015-04-15 | 微梦创科网络科技（中国）有限公司 | User interface element management method and device |
| KR20160120896A (en) * | 2015-04-09 | 2016-10-19 | 엘에스산전 주식회사 | Apparatus for testing inverter parameters |
| CN106776280A (en) * | 2016-11-24 | 2017-05-31 | 上海携程商务有限公司 | Configurable performance test device |
| CN108228443A (en) * | 2016-12-14 | 2018-06-29 | 北京国双科技有限公司 | A kind of test method and device of web applications |
| CN107273286A (en) * | 2017-06-02 | 2017-10-20 | 携程计算机技术（上海）有限公司 | For the scene automatic test platform and method of task application |
| CN109101415A (en) * | 2018-06-25 | 2018-12-28 | 平安科技（深圳）有限公司 | Interface test method, system, equipment and the storage medium compared based on database |
Non-Patent Citations (2)
| Title |
|---|
| ZARKO MIJAILOVIC 等: "A Retrospective on User Interface Development Technology", 《IEEE SOFTWARE》, pages 76 - 83 * |
| 赵祎骅 等: "网络机器人在数据库比对系统中的应用", 《电脑编程技巧与维护》, pages 68 - 69 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112380113B (en) | 2024-05-17 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102789416B (en) | Memory fault injection method and simulator thereof for software built-in test (BIT) | |
| CN101241467B (en) | Automatized white box test system and method facing to WEB application | |
| CN108446221A (en) | System detection method, device, computer equipment and storage medium | |
| CN105183630B (en) | Applied program testing method and device | |
| CN110727603A (en) | Improved method for automatically testing positioning elements based on UI (user interface) | |
| US10437717B2 (en) | Defect reporting in application testing | |
| CN102236600A (en) | Method and device for obtaining code coverage rate | |
| CN111459814A (en) | Automatic test case generation method and device and electronic equipment | |
| CN115080389A (en) | Test system, method, equipment and storage medium for improving index statistical efficiency | |
| CN106257429B (en) | A kind of method of the mating Survey Software acceptance test of GNSS receiver | |
| CN111241111A (en) | Data query method and device, data comparison method and device, medium and equipment | |
| CN112380113B (en) | Software testing method and system | |
| CN117251348A (en) | Method and system for testing equipment performance | |
| CN114116488A (en) | Method, device and equipment for acquiring test coverage rate information and storage medium | |
| Wu | An effective equivalence partitioning method to design the test case of the WEB application | |
| CN105204997B (en) | software defect detection method and device | |
| CN112817863A (en) | AI auxiliary automatic test method and system based on AI deep learning | |
| CN111767222A (en) | Data model verification method and device, electronic equipment and storage medium | |
| CN116755684B (en) | OAS Schema generation method, device, equipment and medium | |
| CN112799956B (en) | Asset identification capability test method, device and system device | |
| CN110750452B (en) | Automatic test method and device | |
| Wu et al. | An empirical assessment of the predictive quality of internal product metrics to predict software maintainability in practice | |
| CN113434408B (en) | Unit test case sequencing method based on test prediction | |
| CN112612705B (en) | Method for accurately positioning and displaying interface coverage rate report | |
| CN116860606A (en) | Code detection method, medium, device and computing equipment |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |