CN111581100B

CN111581100B - Background management system testing method

Info

Publication number: CN111581100B
Application number: CN202010390968.5A
Authority: CN
Inventors: 刘松
Original assignee: Beijing Shouqi Zhixing Technology Co Ltd
Current assignee: Beijing Shouqi Zhixing Technology Co Ltd
Priority date: 2020-05-11
Filing date: 2020-05-11
Publication date: 2023-05-30
Anticipated expiration: 2040-05-11
Also published as: CN111581100A

Abstract

The invention discloses a background management system testing method, which relates to the technical field of testing, and comprises the steps of obtaining an environment name to be tested in a configuration document, obtaining corresponding environment parameters to be tested, front-end browser parameters and an assertion list according to the environment name to be tested, obtaining corresponding catalog information from a rear-end server according to interface parameters in the environment parameters to be tested, judging whether the catalog information is correct, analyzing the catalog information to obtain a plurality of full paths of corresponding bottom catalogs, sequentially obtaining pages corresponding to the bottom catalogs according to a bottom catalog sequence list, respectively judging whether the pages corresponding to the bottom catalogs are correct according to the assertion list, if so, capturing corresponding testing results into a result document, if not, capturing a screenshot of the wrong page and writing the corresponding testing results into the result document, thereby improving testing efficiency and the readability of the testing results.

Description

Background management system testing method

Technical Field

The invention relates to the technical field of testing, in particular to a background management system testing method.

Background

At present, the internet company needs to update quickly, and the service changes greatly, so that the front-end and back-end update frequency is high. In front-end and back-end testing, companies often attach more importance to front-end APP testing and have weak testing forces for the back-end management system. In practice, however, each change in front-end APP corresponds to a change in a background management system, and whichever front-end or back-end has a problem directly affects customer usage and corporate revenue. The background management system has a relatively fixed and simple page structure, and provides convenience for automatic test, but has higher maintenance cost due to poor page automation fault tolerance.

The existing schemes for the background management system comprise the following schemes:

(1) Through manual traversal test, each page of the background management system is manually traversed and checked, and a test result is recorded, the test time of the scheme is long, the test result is required to be manually recorded, the traversal test result is required to be collated and sent, and the test efficiency is low;

(2) Through automatic page traversal test, elements in a background management system page are checked and test results are recorded after each page script is manually written, the page traversal test results are automatically sent, the page script is required to be rewritten for the modified or added page after the background management system is updated, and the scheme is required to complete the test for all the pages, so that the test time is long and the test efficiency is low;

(3) And after the background management system is updated, the interface script is required to be rewritten for the modified or added page, so that the maintenance cost is high.

How to ensure the functions and pages of the background management system to be normal and to rapidly and accurately complete the test of the background management system with hundreds of pages becomes the focus of attention of the majority of testers.

Disclosure of Invention

In order to solve the defects in the prior art, the embodiment of the invention provides a background management system testing method, which comprises the following steps:

s1, acquiring an environment name to be tested in a configuration document;

s2, acquiring corresponding environment parameters to be tested, front-end browser parameters and an assertion list according to the environment names to be tested;

s3, acquiring corresponding catalogue information from a back-end server according to interface parameters in the environment parameters to be tested;

s4, judging whether the catalog information is correct, if not, acquiring corresponding catalog information from a background server according to the database parameters in the environmental parameters to be tested, and if so, executing a step S6;

s5, judging whether the catalog information is correct, if so, executing a step S6, and if not, executing a step S11;

s6, analyzing the catalog information to obtain a plurality of full paths of corresponding bottom-layer catalogs;

s7, circularly traversing the full path of each bottom layer directory, judging whether the full path of each bottom layer directory needs to be tested according to the list to be tested, and if so, executing the step S8;

s8, analyzing the full path of each bottom-layer directory to obtain a bottom-layer directory sequence list;

s9, sequentially obtaining pages corresponding to the bottom-layer catalogs according to the bottom-layer catalogs sequence list;

s10, respectively judging whether the page corresponding to the bottom directory is correct or not according to the assertion list; if yes, the corresponding test result is sent to a result document, and if not, step S11 is executed;

s11, capturing a screenshot of the error page and writing the corresponding test result into a result document.

Preferably, determining whether the directory information is correct includes:

judging whether the catalogue information comprises one or more key value pair type data, if not, determining that the catalogue information is wrong.

Preferably, the interface parameters include a request line, a request body and a request header.

Preferably, the database parameters include the IP address, user name and password of the database.

Preferably, the assertion list can be flexibly configured according to actual requirements.

Preferably, in the method, corresponding directory information is obtained from a backend server according to an interface parameter in the environmental parameters to be tested, and the method further comprises:

and judging whether the front-end browser is started or not according to the front-end browser parameters.

The background management system testing method provided by the embodiment of the invention has the following beneficial effects:

(1) The one-key triggering is realized, the background management system is automatically traversed, the test result is automatically recorded, and the test efficiency is improved;

(2) The assertion list can be flexibly configured, and the verification of the background management system is more convenient and quick;

(3) Whether the background management system is updated or not, the catalog information is acquired by using an interface or a database, all the catalog information (including newly added catalog information) can be acquired at one time, and the stability is high;

(4) The catalog information is automatically analyzed, the whole path of the bottom catalog is automatically analyzed, and the fault tolerance is extremely high;

(5) The error page is subjected to real-time screenshot, the test result is clear and definite, and the readability of the test result is improved.

Detailed Description

The present invention will be specifically described with reference to the following specific examples.

The background management system testing method provided by the embodiment of the invention comprises the following steps:

s101, obtaining the name of the environment to be tested in the configuration document.

S102, acquiring corresponding environment parameters to be tested, front-end browser parameters and an assertion list according to the environment names to be tested.

S103, according to interface parameters in the environment parameters to be tested, corresponding directory information is obtained from the back-end server.

And S104, judging whether the catalog information is correct, if not, acquiring the corresponding catalog information from a background server according to the database parameters in the environment parameters to be tested, and if so, executing the step S106.

S105, judging whether the catalog information is correct, if yes, executing step S106, and if not, executing step S111.

S106, analyzing the directory information to obtain a plurality of corresponding full paths of the bottom-layer directories.

As a specific embodiment, in a data structure tree, C, E and F are the bottom-level directories (leaf nodes), and there are specific pages; a is a top-level directory (root node), and no specific page exists; b and D are intermediate layer directories (child nodes) and there are no specific pages. The corresponding full path of the underlying directory refers to: A-B-C, A-D-E, A-F; after logging in the system, A is in a closed state, B, F and D can be seen only by clicking A, so that clicking A and then clicking B are needed to enter the C page, and finally clicking C and entering the C page.

And S107, traversing the full path of each bottom layer directory in a circulating way, judging whether the full path of each bottom layer directory needs to be tested according to the list to be tested, and if so, executing the step S108.

S108, analyzing the full path of each bottom-layer directory to obtain a bottom-layer directory sequence list.

And S109, sequentially obtaining pages corresponding to the bottom layer catalogs according to the bottom layer catalogs sequence list.

S110, judging whether the page corresponding to the bottom layer catalog is correct or not according to the assertion list; if yes, the corresponding test result is sent to the result document, and if not, step S111 is executed.

S111, capturing a screenshot of the error page and writing a corresponding test result into a result document.

Optionally, determining whether the directory information is correct includes:

and judging whether the directory information comprises one or more key value pair type data, and if not, determining that the directory information is wrong.

Optionally, the interface parameters include a request line, a request body, and a request header.

Optionally, the database parameters include an IP address, a user name, and a password of the database.

Optionally, the assertion list can be flexibly configured according to actual requirements.

As a specific example, when a page contains 500, 404 and Error fields, the page is considered to be displaying exceptions, then the above fields may be added to the predicate list, i.e., the predicate list is (500, 404, error).

Preferably, in the step of acquiring corresponding directory information from the back-end server according to the interface parameters in the environment parameters to be tested, the method further comprises:

As a specific embodiment, when the front-end browser parameter is 1, it means to open the front-end browser, and when the front-end browser parameter is 0, it means to close the front-end browser.

According to the background management system testing method provided by the embodiment of the invention, the environment names to be tested in the configuration document are obtained, the corresponding environment parameters to be tested, the front-end browser parameters and the assertion list are obtained according to the environment names to be tested, the corresponding directory information is obtained from the rear-end server according to the interface parameters in the environment parameters to be tested, whether the directory information is correct or not is judged, if yes, the directory information is analyzed to obtain all paths of a plurality of corresponding bottom directories, the all paths of all bottom directories are traversed circularly, whether the all paths of all bottom directories need to be tested is judged according to the to-be-tested list, if yes, the all paths of all bottom directories are analyzed to obtain a bottom directory sequence list, pages corresponding to the bottom directories are sequentially obtained according to the bottom directory sequence list, if yes, the corresponding test results are respectively judged to be correct according to the assertion list, if no, the corresponding test results are obtained to the result document, if no, the error pages are captured, the corresponding test results are written to the result document, and the test efficiency and the readability of the test results are improved.

In the foregoing embodiments, the descriptions of the embodiments are emphasized, and for parts of one embodiment that are not described in detail, reference may be made to related descriptions of other embodiments.

It will be appreciated that the relevant features of the methods and apparatus described above may be referenced to one another. In addition, the "first", "second", and the like in the above embodiments are for distinguishing the embodiments, and do not represent the merits and merits of the embodiments.

It should also be noted that 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 an element.

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

The foregoing is merely exemplary of the present application and is not intended to limit the present application. Various modifications and changes may be made to the present application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc. which are within the spirit and principles of the present application are intended to be included within the scope of the claims of the present application.

Claims

1. A background management system testing method, comprising:

s1, acquiring an environment name to be tested in a configuration document;

s4, judging whether the catalog information acquired in the step S3 is correct, if not, acquiring corresponding catalog information from a background server according to database parameters in the environmental parameters to be tested, and executing the step S5, if so, executing the step S6;

s5, judging whether the catalog information acquired in the step S4 is correct, if so, executing the step S6, and if not, executing the step S11;

s6, analyzing the acquired directory information to obtain a plurality of full paths of corresponding bottom-layer directories;

2. The background management system test method according to claim 1, wherein determining whether the directory information is correct comprises:

3. The method of claim 1, wherein the interface parameters include a request line, a request body, and a request header.

4. The background management system test method according to claim 1, wherein the database parameters include an IP address, a user name, and a password of a database.

5. The method for testing a background management system according to claim 1, wherein the assertion list is flexibly configured according to actual requirements.

6. The method for testing a background management system according to claim 1, wherein, in accordance with an interface parameter in the environmental parameters to be tested, corresponding directory information is obtained from a backend server, the method further comprises: