CN109634844B - JS code testing method and device and electronic equipment - Google Patents

Abstract

The invention relates to the technical field of Internet, in particular to a JS code testing method and device and electronic equipment. The JS code testing method comprises the following steps: acquiring a JS code to be tested and a first configuration file corresponding to the JS code to be tested; and simultaneously testing the compatibility of the JS codes to be tested relative to a preset browser set based on the first configuration file, and obtaining a code compatibility test result of the JS codes to be tested. When the JS code to be tested is required to be tested, the compatibility of the JS code to be tested relative to a preset browser set can be directly and simultaneously tested only on the basis of the first configuration file, so that a code compatibility test result of the JS code to be tested is obtained, and compared with the scheme that each browser is used for testing the compatibility of the JS code to be tested in a manual test mode in the prior art, the test efficiency is improved to a greater extent.

Description

JS code testing methods, devices and electronic equipment

Technical field

The present invention relates to the field of Internet technology, and specifically to a JS code testing method, device and electronic equipment.

Background technique

JS, or Javascript, is a programming language born to meet the needs of dynamic web page production. It is now more and more widely used in the production of Internet web pages. Therefore, the amount of development and testing of JS code is also gradually increasing. However, in the existing technology, the testing efficiency of JS code is low. For example, when testing the compatibility of the JS code to be tested in a set of preset browsers, each preset browser to be tested JS code can only be tested separately through manual testing. Code compatibility, therefore, testing efficiency is extremely low.

Contents of the invention

In view of this, the purpose of embodiments of the present invention is to provide a JS code testing method, device and electronic equipment to effectively improve the above problems.

The JS code testing method provided in the embodiment of the present invention includes:

Obtain the JS code to be tested and the first configuration file corresponding to the JS code to be tested;

Based on the first configuration file, the compatibility of the JS code to be tested with respect to a preset browser set is simultaneously tested to obtain a code compatibility test result of the JS code to be tested.

Further, the JS code to be tested includes at least one target JS function, and the first configuration file includes at least one piece of function compatibility information used to indicate that the JS function is incompatible with the preset browser set;

Simultaneously testing the compatibility of the JS code to be tested with respect to a preset browser set based on the first configuration file and obtaining the code compatibility test results of the JS code to be tested includes:

Based on at least one piece of the function compatibility information, respectively determine the function compatibility test results of each target JS function in the JS code to be tested relative to the preset browser set;

Determine the code compatibility test results of the JS code to be tested based on the function compatibility test results of all target JS functions in the JS code to be tested;

Wherein, if all target JS functions in the JS code to be tested are compatible with the preset browser set, the code compatibility test result of the JS code to be tested is determined to be compatible; otherwise, the code compatibility test result of the JS code to be tested is determined to be compatible. The code compatibility test result of the JS code to be tested is determined to be incompatible.

Further, based on at least one piece of the function compatibility information, respectively determining the function compatibility test results of each target JS function in the JS code to be tested relative to the preset browser set includes:

For each target JS function in the JS code to be tested, determine whether there is function compatibility information corresponding to the target JS function in the first configuration file;

If there is function compatibility information corresponding to the target JS function in the first configuration file, the function compatibility test result of the target JS function is determined according to the function compatibility information; otherwise, the function compatibility test result of the target JS function is determined. The function compatibility test result of the target JS function is determined to be compatible.

Further, the function compatibility information includes function labels and function content corresponding to the function labels. Each function label corresponds to a JS function, and the function content is used to characterize the JS function corresponding to the function label. Compatibility relative to the browsers in the preset browser set;

Determining the function compatibility test result of the target JS function based on the function compatibility information includes:

Based on the preset information association situation, the association type of the function compatibility information is determined. The association type includes a first association type and a second association type. The first association type is used to characterize the information in the first configuration file. There is no function compatibility information functionally associated with the function compatibility information, and the second association type is used to represent that there is function compatibility information functionally associated with the function compatibility information in the first configuration file;

If the association type of the function compatibility information is the first association type, determine the function compatibility test result of the target JS function according to the function compatibility information;

If the association type of the function compatibility information is the second association type, the target JS is determined based on the function content of the function compatibility information and the function content of the function compatibility information functionally associated with the function compatibility information. The function compatibility test results for the function.

Further, determining the function compatibility test result of the target JS function based on the function content of the function compatibility information and the function content of the function compatibility information functionally associated with the function compatibility information includes:

According to the function content of the function compatibility information, a browser compatible with the JS function corresponding to the function compatibility information is obtained as the first browser;

The function compatibility information functionally associated with the function compatibility information is used as the associated function compatibility information, and based on the function content of the associated function compatibility information, a function compatible with the JS function corresponding to the associated function compatibility information is obtained. Browser, as a second browser;

Determine whether the set of the first browser and the second browser is the same as the default browser set;

If the set of the first browser and the second browser is the same as the preset browser set, it is determined that the function compatibility test result of the target JS function is compatible; otherwise, it is determined that the target JS function is compatible. The function compatibility test result of the JS function is incompatible.

Further, when the function compatibility test result of the target JS function is incompatible, determining the function compatibility test result of the target JS function according to the function compatibility information further includes:

Based on the preset browser compatibility situation, the incompatibility type of the function compatibility information is determined. The incompatibility type includes a first incompatibility type and a second incompatibility type. The first incompatibility type is used to characterize the The incompatibility of the function compatibility information is completely incompatible, and the second incompatibility type is used to characterize the incompatibility of the function compatibility information as incomplete compatibility;

If the incompatibility type of the function compatibility information is the first incompatibility type, determine the function compatibility result of the target JS function to be completely incompatible;

If the incompatibility type of the function compatibility information is the second incompatibility type, the function compatibility result of the target JS function is determined to be incompletely compatible.

Further, the JS code testing method also includes:

Obtain the second configuration file corresponding to the JS code to be tested;

The syntax standardization of the JS code to be tested is tested based on the second configuration file, and the code syntax standardization test result of the JS code to be tested is obtained.

Further, the second configuration file includes at least one piece of grammatical normative information used to characterize the grammatical irregularities of the JS code to be tested;

The method of testing the syntax standardization of the JS code to be tested based on the second configuration file and obtaining the code syntax standardization test results of the JS code to be tested includes:

For each piece of grammatical normative information, determine whether there is a grammatical setting corresponding to the grammatical normative information in the JS code to be tested;

If there is a grammar setting corresponding to the grammar normative information in the JS code to be tested, the grammar setting is regarded as non-standard grammar;

If the non-standard syntax exists in the JS code, it is determined that the code syntax normative test result of the JS code to be tested is non-standard; otherwise, it is determined that the code syntax normative test result of the JS code to be tested is normative. .

Further, if there is a grammar setting corresponding to the grammar normative information in the JS code to be tested, the grammar setting is regarded as non-standard grammar, including:

Based on the preset grammatical normative situation, the irregularity type of the grammatical normative information is determined. The irregularity type includes a first irregularity type and a second irregularity type. The first irregularity type is used to characterize the The grammatical irregularities of the grammatical normative information are completely irregular, and the second irregularity type used to characterize the irregularities of the grammatical normative information is incompletely normative;

If the irregularity type of the grammar normative information is the first irregularity type, then the grammar is set as a completely irregular grammar;

If the irregularity type of the grammar normative information is the second irregularity type, the grammar is set as a completely incomplete normative grammar.

The JS code testing device provided by the embodiment of the present invention includes:

The first configuration file acquisition module is used to obtain the JS code to be tested and the first configuration file corresponding to the JS code to be tested;

The first test result acquisition module is configured to simultaneously test the compatibility of the JS code to be tested with respect to the preset browser collection based on the first configuration file, and obtain the code compatibility test results of the JS code to be tested.

Further, the JS code to be tested includes at least one target JS function, and the first configuration file includes at least one piece of function compatibility information used to indicate that the JS function is incompatible with the preset browser set;

The first test result acquisition module is specifically used for:

Based on at least one piece of the function compatibility information, respectively determine the function compatibility test results of each target JS function in the JS code to be tested relative to the preset browser set;

Determine the code compatibility test results of the JS code to be tested based on the function compatibility test results of all target JS functions in the JS code to be tested;

Wherein, if all target JS functions in the JS code to be tested are compatible with the preset browser set, the code compatibility test result of the JS code to be tested is determined to be compatible; otherwise, the code compatibility test result of the JS code to be tested is determined to be compatible. The code compatibility test result of the JS code to be tested is determined to be incompatible.

Further, the first test result acquisition module is specifically used for:

For each target JS function in the JS code to be tested, determine whether there is function compatibility information corresponding to the target JS function in the first configuration file;

If there is function compatibility information corresponding to the target JS function in the first configuration file, the function compatibility test result of the target JS function is determined according to the function compatibility information; otherwise, the function compatibility test result of the target JS function is determined. The function compatibility test result of the target JS function is determined to be compatible.

Further, the function compatibility information includes function labels and function content corresponding to the function labels. Each function label corresponds to a JS function, and the function content is used to represent the relative relationship between the JS functions corresponding to the function labels. Compatibility of browsers in the default browser set;

The first test result acquisition module is specifically used for:

Based on the preset information association situation, the association type of the function compatibility information is determined. The association type includes a first association type and a second association type. The first association type is used to characterize the information in the first configuration file. There is no function compatibility information functionally associated with the function compatibility information, and the second association type is used to represent that there is function compatibility information functionally associated with the function compatibility information in the first configuration file;

If the association type of the function compatibility information is the first association type, determine the function compatibility test result of the target JS function according to the function compatibility information;

If the association type of the function compatibility information is the second association type, the target JS is determined based on the function content of the function compatibility information and the function content of the function compatibility information functionally associated with the function compatibility information. The function compatibility test results for the function.

Further, the first test result acquisition module is specifically used for:

According to the function content of the function compatibility information, a browser compatible with the JS function corresponding to the function compatibility information is obtained as the first browser;

The function compatibility information functionally associated with the function compatibility information is used as the associated function compatibility information, and based on the function content of the associated function compatibility information, a function compatible with the JS function corresponding to the associated function compatibility information is obtained. Browser, as a second browser;

Determine whether the set of the first browser and the second browser is the same as the default browser set;

If the set of the first browser and the second browser is the same as the preset browser set, it is determined that the function compatibility test result of the target JS function is compatible; otherwise, it is determined that the target JS function is compatible. The function compatibility test result of the JS function is incompatible.

Further, when the function compatibility test result of the target JS function is incompatible, the first test result acquisition module is also specifically used to:

Based on the preset browser compatibility situation, the incompatibility type of the function compatibility information is determined. The incompatibility type includes a first incompatibility type and a second incompatibility type. The first incompatibility type is used to characterize the The incompatibility of the function compatibility information is completely incompatible, and the second incompatibility type is used to characterize the incompatibility of the function compatibility information as incomplete compatibility;

If the incompatibility type of the function compatibility information is the first incompatibility type, determine the function compatibility result of the target JS function to be completely incompatible;

If the incompatibility type of the function compatibility information is the second incompatibility type, the function compatibility result of the target JS function is determined to be incompletely compatible.

Further, the JS code testing device also includes:

The second configuration file acquisition module is used to obtain the second configuration file corresponding to the JS code to be tested;

The second test result acquisition module is configured to test the syntax standardization of the JS code to be tested based on the second configuration file, and obtain the code syntax standardization test results of the JS code to be tested.

Further, the second configuration file includes at least one piece of grammatical normative information used to characterize the grammatical irregularities of the JS code to be tested;

The second test result acquisition module is specifically used for:

For each piece of grammatical normative information, determine whether there is a grammatical setting corresponding to the grammatical normative information in the JS code to be tested;

If there is a grammar setting corresponding to the grammar normative information in the JS code to be tested, the grammar setting is regarded as non-standard grammar;

If the non-standard syntax exists in the JS code, it is determined that the code syntax normative test result of the JS code to be tested is non-standard; otherwise, it is determined that the code syntax normative test result of the JS code to be tested is normative. .

Further, the second test result acquisition module is specifically configured to determine the irregularity type of the grammatical normative information based on the preset grammatical normative situation. The irregularity type includes a first irregularity type and a second irregularity type. Irregularity type, the first irregularity type is used to characterize the grammatical irregularity of the grammatical normative information as completely irregular, and the second irregularity type is used to characterize the irregularity of the grammatical normative information. For incomplete specification;

If the irregularity type of the grammar normative information is the first irregularity type, then the grammar is set as a completely irregular grammar;

If the irregularity type of the grammar normative information is the second irregularity type, the grammar is set as a completely incomplete normative grammar.

An electronic device provided by an embodiment of the present invention includes a processor, a memory, and the above JS code testing device. The JS code testing device includes one or more software function modules stored in the memory and executed by the processor.

Embodiments of the present invention also provide a computer-readable storage medium on which a computer program is stored. When the computer program is executed, the above JS code testing method can be implemented.

The JS code testing method, device and electronic equipment provided by the embodiments of the present invention can obtain the JS code to be tested and the first configuration file corresponding to the JS code to be tested, and simultaneously test the JS code to be tested based on the first configuration file. Test the compatibility of the JS code with respect to the preset browser set, and obtain the code compatibility test results of the JS code to be tested. In this way, when the JS code to be tested needs to be tested, the compatibility of the JS code to be tested with respect to the preset browser collection can be directly and simultaneously tested based on the first configuration file, thereby obtaining code compatibility of the JS code to be tested. Therefore, compared with the existing technology, which uses manual testing to separately test the compatibility of each browser with the JS code to be tested, the testing efficiency has been greatly improved.

The above description is only an overview of the technical solution of the present invention. In order to have a clearer understanding of the technical means of the present invention, it can be implemented according to the content of the description, and in order to make the above and other objects, features and advantages of the present invention more obvious and understandable. , the specific embodiments of the present invention are listed below.

Description of the drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings required to be used in the embodiments will be briefly introduced below. It should be understood that the following drawings only show certain embodiments of the present disclosure and therefore do not It should be regarded as a limitation of the scope. For those of ordinary skill in the art, other relevant drawings can be obtained based on these drawings without exerting creative efforts.

Figure 1 is a schematic structural block diagram of an electronic device provided by an embodiment of the present invention.

Figure 2 is a schematic flow chart of a JS code testing method provided by an embodiment of the present invention.

Figure 3 is another partial flow chart of a JS code testing method provided by an embodiment of the present invention.

Figure 4 is a schematic structural block diagram of a JS code testing device provided by an embodiment of the present invention.

Figure 5 is another schematic structural block diagram of a JS code testing device provided by an embodiment of the present invention.

Icons: 100-electronic equipment; 110-JS code testing device; 111-first configuration file acquisition module; 112-first test result acquisition module; 113-second configuration file acquisition module; 114-second test result acquisition module; 120-processor; 130-memory.

Detailed ways

The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only some of the embodiments of the present disclosure, rather than all of the embodiments. The components of the embodiments of the invention generally described and illustrated in the figures herein may be arranged and designed in a variety of different configurations. Therefore, the following detailed description of the embodiments of the disclosure provided in the appended drawings is not intended to limit the scope of the claimed disclosure, but rather to represent selected embodiments of the disclosure. Based on the embodiments of the present disclosure, all other embodiments obtained by those skilled in the art without any creative efforts shall fall within the scope of protection of the present disclosure.

It should be noted that similar reference numerals and letters represent similar items in the following figures, therefore, once an item is defined in one figure, it does not need further definition and explanation in subsequent figures.

Please refer to FIG. 1 , which is a schematic structural block diagram of an electronic device 100 using a JS code testing method and device according to an embodiment of the present invention. Further, in the embodiment of the present invention, the electronic device 100 includes a code testing device 110, a processor 120 and a memory 130.

The processor 120 and the memory 130 are electrically connected directly or indirectly to realize data transmission or interaction. For example, these components can be electrically connected to each other through one or more communication buses or signal lines. The JS code testing device 110 includes at least one software module that can be stored in the memory 130 in the form of software or firmware or solidified in the operating system (Operating System, OS) of the electronic device 100 . The processor 120 is used to execute executable modules stored in the memory 130, such as software function modules and computer programs included in the JS code testing device 110. The processor 120 can execute the computer program after receiving the execution instruction.

The processor 120 may be an integrated circuit chip with signal processing capabilities. The processor 120 may also be a general-purpose processor, for example, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a discrete gate or transistor logic device, or a discrete hardware component, and may implement or execute the steps in the embodiments of the present invention. Disclosed methods, steps and logical block diagrams. Furthermore, the general-purpose processor may be a microprocessor or any conventional processor or the like.

The memory 130 may be, but is not limited to, random access memory (Random Access Memory, RAM), read only memory (Read Only Memory, ROM), programmable read only memory (Programmable Read-Only Memory, PROM), erasable and programmable memory. Program read-only memory (Erasable Programmable Read-Only Memory, EPROM), electrically erasable programmable read-only memory, Electric Erasable Programmable Read-Only Memory, EEPROM), etc. The memory 130 is used to store a program, and the processor 120 executes the program after receiving the execution instruction.

It should be understood that the structure shown in FIG. 1 is only illustrative, and the electronic device 100 provided by the embodiment of the present invention may also have fewer or more components than that shown in FIG. 1 , or have a different configuration than that shown in FIG. 1 . In addition, each component shown in Figure 1 can be implemented by software, hardware, or a combination thereof.

Please refer to Figure 2. Figure 2 is a schematic flow chart of a JS code testing method provided by an embodiment of the present invention. The JS code testing method is applied to the electronic device shown in Figure 1. The specific flow of the JS code testing method is described below in conjunction with Figure 2. and steps are explained in detail. It should be noted that the method provided by the present invention is not limited to the order shown in Figure 2 and below. The specific process and steps of the JS code testing method will be described in detail below in conjunction with Figure 2.

Step S100: Obtain the JS code to be tested and the first configuration file corresponding to the JS code to be tested.

The first configuration file is created in advance and is used to test the compatibility of the JS code to be tested with respect to the preset browser collection. Among them, the default browser collection includes multiple different types of browsers, such as IE, Google Chrome, Firefox, 360 Secure Browser, Sogou Browser, World Window Browser and other browsers. Multiple. In the embodiment of the present invention, the specific process and steps of the JS code testing method will be described in detail, taking the default browser set including IE, Google Chrome, and Firefox as examples.

Step S200: Simultaneously test the compatibility of the JS code to be tested with respect to the preset browser set based on the first configuration file, and obtain the code compatibility test results of the JS code to be tested.

The JS code to be tested includes at least one target JS function. Among them, the target JS function is event-driven, or executes a reusable code block to implement the corresponding function when it is called. For example, JS functions such as function currentStyle(), function getComputedStyle(), function const(), etc.

In this embodiment of the present invention, the first configuration file may include at least one piece of function compatibility information used to indicate that the JS function is incompatible with the preset browser set. It should be noted that in the embodiment of the present invention, if a certain JS function has an incompatible browser in the default browser set, it is incompatible with the default browser set. Based on this, simultaneously testing the compatibility of the JS code to be tested with respect to the preset browser set based on the first configuration file and obtaining the code compatibility test results of the JS code to be tested may include the following steps.

Based on at least one piece of function compatibility information, determine the function compatibility test results of each target JS function in the JS code to be tested relative to the preset browser collection, and based on the function compatibility of all target JS functions in the JS code to be tested Test results, determine the code compatibility test results of the JS code to be tested. Among them, if all target JS functions in the JS code to be tested are compatible with the preset browser set, the code compatibility test result of the JS code to be tested will be determined to be compatible; otherwise, the code compatibility of the JS code to be tested will be determined as compatible. The test results determined that it is incompatible.

Further, in the embodiment of the present invention, based on at least one piece of function compatibility information, determining the function compatibility test results of each target JS function in the JS code to be tested relative to the preset browser set may include the following steps.

For each target JS function in the JS code to be tested, determine whether there is function compatibility information corresponding to the target JS function in the first configuration file. Since, in the embodiment of the present invention, the function compatibility information is used to indicate that the JS function is incompatible with the default browser set, therefore, if there is function compatibility information corresponding to the target JS function in the first configuration file, then The function compatibility test result of the target JS function is determined according to the function compatibility information; otherwise, the function compatibility test result of the target JS function is determined to be compatible.

Optionally, in this embodiment of the present invention, the function compatibility information includes function labels and function content corresponding to the function labels. Each function label corresponds to a JS function, and the function content is used to characterize the JS function corresponding to the function label relative to the preset function. Assume the compatibility of the browsers in the browser collection.

For example, the function compatibility information can be "currentStyle": "true: IE", where "currentStyle" is a function label, its corresponding JS function is currentStyle(), and the corresponding function of the JS function currentStyle() is to obtain html page elements The non-interline style, "true: IE" is the function content, which is used to indicate that the JS function currentStyle() is compatible with the IE browser in the default browser collection, that is, relative to Google Chrome in the default browser collection The browser is not compatible with Firefox, so it is understandable that the function compatibility information can also be written as ""currentStyle": "false: Chrome, Firefox"". In the embodiment of the present invention, in order to ensure the simplicity of the code, it is preferably written as ""currentStyle":"true:IE"". For another example, the function compatibility information can be "getComputedStyle": "false: IE", where "getComputedStyle" is a function label, its corresponding JS function is getComputedStyle(), and the corresponding function of the JS function getComputedStyle() is to obtain an html page The non-interline style of the element, "false: IE" is the function content, which is used to indicate that the JS function getComputedStyle() is incompatible with the IE browser in the default browser collection, that is, relative to the IE browser in the default browser collection Google Chrome and Firefox are compatible. Therefore, it is understandable that the function compatibility information can also be written as "getComputedStyle: "true: Chrome, Firefox". In the embodiment of the present invention, in order to ensure the simplicity of the code, it is preferably written as "getComputedStyle": "false: IE". For another example, the function compatibility information can be "setAttribute": "false: IE", where "setAttribute" is a function label, and its corresponding JS function is setAttribute(), and the JS function The corresponding function of setAttribute() is to set object attributes, and "false: IE" is the function content, which is used to indicate that the JS function setAttribute() is incompatible with the IE browser in the default browser collection, that is, relative to the default Google Chrome and Firefox in the browser collection are compatible. Therefore, it is understandable that the function compatibility information can also be written as "const": "false: Chrome, Firefox". In the embodiment of the present invention, in order to ensure that the code For simplicity, it is better to write "setAttribute":"true:Firefox".

It can be seen from the above that the JS code to be tested may include two different JS functions at the same time, and the corresponding functions of these two JS functions are the same but compatible with different browsers. For example, the JS function currentStyle() and the JS function getComputedStyle() have the same functions, but the JS function currentStyle() is compatible with IE browser, and the JS function getComputedStyle() is compatible with Google Chrome and Firefox. To address this situation, in the embodiment of the present invention, the first configuration file also sets a preset information association situation, which is used to determine the association type of the function compatibility information. The association type includes a first association type and a second association type. The first association type is used to represent that there is no function compatibility information functionally associated with the function compatibility information in the first configuration file, for example, function compatibility information "setAttribute": "false: IE". The second association type is used to represent that there is function compatibility information functionally associated with the function compatibility information in the first configuration file, for example, function compatibility information "currentStyle": "true:IE" and function compatibility information "getComputedStyle": "false: IE". In actual implementation, in order to ensure the cleanliness of the code, the function compatibility information whose associated type is the second associated type and the function compatibility information associated with its function can be written as one overall message, for example, the function compatibility information "currentStyle": "true: IE" and function compatibility information "getComputedStyle": "false: IE" are written as "currentStyle": "true: IE"; "getComputedStyle": "true: Chrome, Firefox".

Based on the above description, in the embodiment of the present invention, determining the function compatibility test result of the target JS function based on the function compatibility information may include the following steps.

Determines the associated type of function compatibility information. If the association type of the function compatibility information is the first association type, the function compatibility test result of the target JS function is determined according to the function compatibility information. In the embodiment of the present invention, that is, the function compatibility test result of the target JS function is determined to be Not compatible. If the association type of the function compatibility information is the second association type, the function compatibility test result of the target JS function is determined based on the function content of the function compatibility information and the function content of the function compatibility information functionally associated with the function compatibility information.

In actual implementation, first, according to the function content of the function compatibility information, a browser compatible with the JS function corresponding to the function compatibility information can be obtained as the first browser. Then, the function compatibility information associated with the function compatibility information function is used as the associated function compatibility information, and based on the function content of the associated function compatibility information, a browser compatible with the JS function corresponding to the associated function compatibility information is obtained as the third Two browsers. Finally, it is determined whether the set of the first browser and the second browser is the same as the default browser set. If the set of the first browser and the second browser is the same as the preset browser set, it is determined that the function compatibility test result of the target JS function is compatible; otherwise, it is determined that the function compatibility test result of the target JS function is incompatible.

For example, when the JS code to be tested includes both the JS function currentStyle() and the JS function getComputedStyle(), the function compatibility of the JS function currentStyle() can be obtained based on the function compatibility information "currentStyle": "true: IE" in the first configuration file. ) compatible browser, that is, the IE browser, is used as the first browser, and at the same time, the function compatibility information "getComputedStyle": "false: IE" associated with the function compatibility information "currentStyle": "true: IE" is used as Associated function compatibility information, and obtains browsers compatible with the JS function getComputedStyle(), that is, Google Chrome and Firefox, as the second browser. If the set of the first browser and the second browser is the same as the default browser, it is determined that the function compatibility test result of the JS function currentStyle() is compatible. Through the same judgment method, it can also be determined that the function compatibility test result of the JS function getComputedStyle() is compatible.

In order to further determine the degree of incompatibility of the target JS function with respect to the preset browser set, in the embodiment of the present invention, the first configuration file also sets the preset browser compatibility status, which is used to determine the incompatibility type of the function compatibility information. , the incompatible type includes a first incompatible type and a second incompatible type. The first incompatibility type is used to characterize the incompatibility of the function compatibility information as complete incompatibility, and the second incompatibility type is used to characterize the incompatibility of the function compatibility information as incomplete compatibility. For a certain piece of function compatibility information, if its incompatibility type is the first incompatibility type, the JS function represented by it cannot implement the corresponding function on an incompatible browser in the default browser collection. If its incompatibility type is The second incompatible type means that the JS function represented by it can implement the corresponding function on incompatible browsers in the default browser collection, but the implementation effect cannot meet the preset requirements.

For example, the first configuration file has function compatibility information "setAttribute": "false: IE" and function compatibility information "str": "false: IE6, IE7", and the corresponding function of the JS function setAttribute() is in IE browsing If it cannot be implemented on the device, the incompatible type of the function compatibility information "setAttribute": "false: IE" will be determined as the first incompatible type. The corresponding function of the JS function str() can be implemented on IE6 and IE7. However, the implementation effect cannot meet the preset requirements, and the incompatibility type of the function compatibility information "str": "false: IE6, IE7" is determined as the second incompatibility type. In actual implementation, in order to ensure the cleanliness of the code, the function compatibility information of the first incompatible type can be written into a program segment, and then the function compatibility information of the second incompatible type can be written into Write another program segment, for example, write the function compatibility information of the first incompatible type into the program segment "block" {...}, and make the function compatibility information of the second incompatible type compatible Sexual information is written into the program segment "warning"{...}

Based on the above description, in the embodiment of the present invention, when the function compatibility test result of the target JS function is incompatible, determining the function compatibility test result of the target JS function based on the function compatibility information may also include the following steps.

Determine the incompatibility type of the function compatibility information. If the incompatibility type of the function compatibility information is the first incompatibility type, then determine the function compatibility result of the target JS function as completely incompatible. If the incompatibility of the function compatibility information is If the type is the second incompatible type, the function compatibility result of the target JS function is determined to be not fully compatible.

In the embodiment of the present invention, after obtaining the code compatibility test results of the JS code to be tested, a code compatibility test report can also be generated based on the code compatibility test results. The code compatibility test report can include the target functions for which each function compatibility test result is completely incompatible, as well as the completely incompatible browsers in the corresponding preset browser set. Similarly, the code compatibility test report can also include The compatibility test results of each function are the target functions that are not fully compatible, and the browsers that are not fully compatible in the corresponding default browser set.

The following will take an example to illustrate the overall process of simultaneously testing the compatibility of the JS code to be tested with respect to the preset browser set based on the first configuration file and obtaining the code compatibility test results of the JS code to be tested.

For example, the first configuration file is:

The target functions included in the code to be tested are JS function cursor: hand(), JS function currentStyle(), JS function getComputedStyle(), JS function "setAttribute"() and JS function str().

Regarding the JS function cursor:hand(), if there is no function compatibility information corresponding to the JS function cursor:hand() in the first configuration file, then the function compatibility test result of the JS function cursor:hand() is determined to be compatible.

Regarding the JS function currentStyle(), there is an association in the first configuration file with the function compatibility information "currentStyle": "true: IE" corresponding to the JS function currentStyle() and the function compatibility information "currentStyle": "true: IE" The type is the second associated type, and the associated function compatibility information of the function compatibility information "currentStyle": "true: IE" is "getComputedStyle": "false: IE". Further, the browsers compatible with the JS function currentStyle() are IE browsers, the browsers compatible with the JS function getComputedStyle() are Google Chrome and Firefox, and the browsers of IE, Google Chrome and Firefox The collection is the same as the default browser collection, so the function compatibility test result of the JS function currentStyle() is determined to be compatible. After the same judgment method, the function compatibility test result of the JS function getComputedStyle() is also compatible. It can be understood that if the JS function currentStyle() exists in the JS code to be tested, but the JS function getComputedStyle() does not exist, the function compatibility test result of the JS function currentStyle() is determined to be incompatible. Similarly, if the JS function to be tested does not If the JS function getComputedStyle() exists in the code, but the JS function currentStyle() does not exist, the function compatibility test result of the JS function getComputedStyle() is determined to be incompatible.

For the JS function "setAttribute" (), there is function compatibility information "setAttribute" corresponding to the JS function "setAttribute" () in the first configuration file: "false: IE", and the associated type of the JS function "setAttribute" () is the first association type, then the function compatibility test result of the JS function "setAttribute"() is determined to be incompatible. Furthermore, because the incompatibility type of the function compatibility information "setAttribute": "false: IE" is the first incompatibility Compatible type, it can be further determined that the function compatibility test result of the JS function "setAttribute"() is determined to be completely incompatible.

For the JS function str(), there is function compatibility information "str" corresponding to the JS function str() in the first configuration file: "false: IE6, IE7", and the association type of the JS function str() is the first association type, then the function compatibility test result of the JS function str() is determined to be incompatible. Furthermore, since the incompatible type of the function compatibility information "str": "false: IE6, IE7" is the second incompatible type, then It can be further determined that the function compatibility test result of the JS function str() is determined to be not fully compatible.

After that, it is determined that the code compatibility test result of the JS code to be tested is incompatible, and the code including the JS function "setAttribute" that is completely incompatible with IE browser, and the JS function str() that is not fully compatible with IE6 browser and IE7 browser can be generated. Compatibility test report.

Optionally, in this embodiment of the present invention, the JS code testing method also includes:

Step S300: Obtain the second configuration file corresponding to the JS code to be tested.

The second configuration file is created in advance and is used to test the syntax standardization of the JS code to be tested.

Step S400: Test the syntax standardization of the JS code to be tested based on the second configuration file, and obtain the code syntax standardization test result of the JS code to be tested.

In this embodiment of the present invention, the second configuration file may include at least one piece of grammatical normative information used to characterize the grammatical irregularities of the JS function. Based on this, testing the syntax standardization of the JS code to be tested based on the second configuration file and obtaining the code syntax standardization test results of the JS code to be tested may include the following steps.

For each piece of grammatical normative information, determine whether there is a grammatical setting corresponding to the grammatical normative information in the JS code to be tested. If there is a syntax setting corresponding to the syntax normative information in the JS code to be tested, the syntax setting will be regarded as non-standard syntax. If there is irregular syntax in the JS code, it is determined that the code syntax normative test result of the JS code to be tested is irregular; otherwise, the code syntax normative test result of the JS code to be tested is determined to be normative.

Optionally, in the embodiment of the present invention, the grammar normative information includes grammar tags and judgment standard content corresponding to the grammar tags. Each grammar tag corresponds to a grammar setting, and the judgment standard content is used to characterize the grammar setting corresponding to the grammar tag. Grammatical normativity is irregular.

For example, the syntax normative information can be "bitwise": true, where "bitwise" is the syntax tag, and its corresponding syntax setting is whether disabled bit operators (such as ^, &) are set in the JS code, and true is the judgment Standard content, used to indicate that if disabled bit operators (such as ^, &) are set in the JS code to be tested, it is confirmed that the syntax in the code of the JS code to be tested is set to non-standard syntax, and it can further confirm that the JS code to be tested is not standardized. The code syntax standardization test result of the code is irregular. For another example, the grammar normative information can be "curly": true, where "curly" is a grammar label, and its corresponding grammar setting is whether to use {} in statements such as if and while to clarify code blocks, and true is the judgment criterion. Content, used to represent that if {} is used in statements such as if and while to clarify the code block in the JS code to be tested, it is confirmed that the syntax in the code of the JS code to be tested is set to non-standard syntax, and it can be further confirmed that the code to be tested is The code syntax standardization test result of JS code is non-standard. For another example, "noarg": true, where "noarg" is a syntax tag, and its corresponding syntax setting is whether arguments.caller and arguments.callee are used. true is the judgment standard content, which is used to characterize the JS code to be tested. If arguments.caller and arguments.callee are used, it is confirmed that the syntax setting in the code of the JS code to be tested is non-standard syntax, and it can be further confirmed that the code syntax normative test result of the JS code to be tested is non-standard.

In order to further determine the degree of grammatical irregularity of the target JS function, in the embodiment of the present invention, the second configuration file also sets a preset grammatical normative situation, which is used to determine the irregularity type of the grammatical normative information. The irregularity type includes the first The first irregularity type and the second irregularity type. The first irregularity type is used to represent grammatical normative information. The grammatical irregularities are completely irregular. The second irregularity type is used to represent grammatical normative information. The irregularity is Not completely standardized. For a certain non-standard grammar, if the non-standard type of the corresponding grammatical normative information is the first non-standard type, it means that using the non-standard syntax in JS code will make the JS code unable to be executed, and the implementation of various JS The corresponding function of the function, if the non-standard type of the corresponding syntax normative information is the second non-standard type, it means that using the non-standard syntax in the JS code will enable the JS code to be executed, and realize the implementation of each JS function. Corresponding function, but the implementation effect cannot meet the preset requirements.

For example, the second configuration file has syntax normative information "bitwise": true and "noarg": true. Since disabled bit operators (such as ^, &) are set in the JS code, the JS code cannot be executed. To realize the corresponding functions of each JS function, the non-standard type of "bitwise": true is confirmed as the first non-standard type. Since arguments.caller and arguments.callee are used in the JS code, the JS code can be executed, and various The corresponding function of the JS function, but the implementation effect cannot meet the preset requirements, then the non-standard type with "noarg": true is confirmed as the second non-standard type. In actual implementation, in order to ensure the cleanliness of the code, the grammatical normative information of the irregular type as the first irregular type can be written into a program segment, and then the grammatical normative information of the irregular type as the second irregular type can be written into a program segment. Write another program segment, for example, write the syntax specification information of the first irregular type into the program segment "block" {...}, and write the syntax specification information of the second irregular type into the program segment "block" {...} Sexual information is written into the program segment "warning"{...}

Based on the above description, in the embodiment of the present invention, if there is a grammar setting corresponding to the grammar normative information in the JS code to be tested, the grammar setting is used as non-standard grammar. Specifically, the following steps may be included.

Determine the irregularity type of the grammatical normative information. If the irregularity type of the grammatical normative information is the first irregularity type, set the grammar as a completely irregular grammar. If the irregularity type of the grammatical normative information is the second irregularity type type, sets the grammar as a completely incomplete canonical grammar.

In the embodiment of the present invention, after obtaining the code syntax normative test results of the JS code to be tested, a code syntax normative test report can also be generated based on the code syntax normative test results. The code syntax normative test report can include each irregular syntax and its corresponding irregularity type.

The following will take an example to illustrate the overall process of testing the syntax standardization of the JS code to be tested based on the second configuration file and obtaining the code syntax standardization test results of the JS code to be tested.

For example, the second configuration file is:

Disabled bit operators (such as ^, &) are set in the code to be tested, and arguments.caller and arguments.callee are used.

For the first piece of syntax normative information "bitwise": true, it is confirmed that the code syntax normative test result of the JS code to be tested is irregular, and because the irregularity type of the syntax normative information "bitwise": true is the first irregularity Type, confirm that the disabled bit operators (such as ^, &) set in the JS code to be tested are completely non-standard syntax.

Regarding the seventh grammatical normative information "noarg": true, confirm that the code syntax normative test result of the JS code to be tested is nonstandard, and the nonstandard type due to the grammatical normative information "noarg": true is the second irregularity Type, confirm that the arguments.caller and arguments.callee used in the JS code to be tested are incompletely standardized syntax.

Based on the same inventive concept as the above-mentioned method for estimating virtual network resources to be distributed, embodiments of the present invention also provide a JS code testing device 110. Referring to FIG. 4 , the JS code testing device 110 includes a first configuration file acquisition module 111 and a first test result acquisition module 112 .

The first configuration file acquisition module is used to obtain the JS code to be tested and the first configuration file corresponding to the JS code to be tested.

For a description of the first configuration file acquisition module 111, reference may be made to the detailed description of the above-mentioned step S100. That is, step S100 may be executed by the first configuration file acquisition module 111, and will not be described again here.

The first test result acquisition module is used to simultaneously test the compatibility of the JS code to be tested with respect to the preset browser set based on the first configuration file, and obtain the code compatibility test results of the JS code to be tested.

The JS code to be tested includes at least one target JS function, and the first configuration file includes at least one piece of function compatibility information used to indicate that the JS function is incompatible with the preset browser set. Based on this, optionally, in the embodiment of the present invention, the first test result acquisition module is specifically used for:

Based on at least one piece of function compatibility information, respectively determine the function compatibility test results of each target JS function in the JS code to be tested relative to the preset browser set;

Determine the code compatibility test results of the JS code to be tested based on the function compatibility test results of all target JS functions in the JS code to be tested;

Among them, if all target JS functions in the JS code to be tested are compatible with the preset browser set, the code compatibility test result of the JS code to be tested will be determined to be compatible; otherwise, the code compatibility of the JS code to be tested will be determined as compatible. The test results determined that it is incompatible.

Optionally, in the embodiment of the present invention, the first test result acquisition module is specifically used for:

For each target JS function in the JS code to be tested, determine whether there is function compatibility information corresponding to the target JS function in the first configuration file;

If there is function compatibility information corresponding to the target JS function in the first configuration file, the function compatibility test result of the target JS function is determined based on the function compatibility information; otherwise, the function compatibility test result of the target JS function is determined to be compatible. .

Function compatibility information includes function tags and function content corresponding to the function tag. Each function tag corresponds to a JS function. The function content is used to characterize the compatibility of the JS function corresponding to the function tag with respect to the browsers in the preset browser collection. sex. Based on this, optionally, in the embodiment of the present invention, the first test result acquisition module is specifically used for:

Based on the preset information association situation, the association type of the function compatibility information is determined. The association type includes a first association type and a second association type. The first association type is used to indicate that there is no functional association with the function compatibility information in the first configuration file. Function compatibility information, the second association type is used to represent that there is function compatibility information functionally associated with the function compatibility information in the first configuration file;

If the association type of the function compatibility information is the first association type, determine the function compatibility test result of the target JS function based on the function compatibility information;

If the association type of the function compatibility information is the second association type, the function compatibility test result of the target JS function is determined based on the function content of the function compatibility information and the function content of the function compatibility information functionally associated with the function compatibility information.

Optionally, in the embodiment of the present invention, the first test result acquisition module is specifically used for:

According to the function content of the function compatibility information, a browser compatible with the JS function corresponding to the function compatibility information is obtained as the first browser;

The function compatibility information associated with the function compatibility information function is used as the associated function compatibility information, and based on the function content of the associated function compatibility information, a browser compatible with the JS function corresponding to the associated function compatibility information is obtained as the second browser;

Determine whether the set of the first browser and the second browser is the same as the default browser set;

If the set of the first browser and the second browser is the same as the preset browser set, it is determined that the function compatibility test result of the target JS function is compatible; otherwise, it is determined that the function compatibility test result of the target JS function is incompatible.

When the function compatibility test result of the target JS function is incompatible, optionally, in the embodiment of the present invention, the first test result acquisition module is also specifically used to:

Based on the preset browser compatibility situation, the incompatibility type of the function compatibility information is determined. The incompatibility type includes a first incompatibility type and a second incompatibility type. The first incompatibility type is used to characterize the incompatibility of the function compatibility information. The situation is completely incompatible, and the incompatibility situation where the second incompatibility type is used to represent function compatibility information is incomplete compatibility;

If the incompatibility type of the function compatibility information is the first incompatibility type, the function compatibility result of the target JS function is determined to be completely incompatible;

If the incompatible type of the function compatibility information is the second incompatible type, the function compatibility result of the target JS function is determined to be incompletely compatible.

For a description of the first test result acquisition module 112, reference may be made to the detailed description of the above-mentioned step S200. That is, step S200 may be executed by the first test result acquisition module 112, and will not be described again here.

Please refer to Figure 5. Optionally, in this embodiment of the present invention, the JS code testing device also includes:

The second configuration file acquisition module is used to obtain the second configuration file corresponding to the JS code to be tested.

For a description of the second configuration file acquisition module 113, reference may be made to the detailed description of the above-mentioned step S300. That is, step S300 may be executed by the second configuration file acquisition module 113, and will not be described again here.

The second test result acquisition module is used to test the syntax standardization of the JS code to be tested based on the second configuration file, and obtain the code syntax standardization test results of the JS code to be tested.

The second configuration file includes at least one piece of grammatical normative information used to characterize grammatical irregularities in the JS code to be tested. Based on this, optionally, in the embodiment of the present invention, the second test result acquisition module is specifically used for:

For each piece of grammatical normative information, determine whether there is a grammatical setting corresponding to the grammatical normative information in the JS code to be tested;

If there is a grammar setting corresponding to the grammar normative information in the JS code to be tested, the grammar setting will be regarded as non-standard grammar;

If there is irregular syntax in the JS code, it is determined that the code syntax normative test result of the JS code to be tested is irregular; otherwise, the code syntax normative test result of the JS code to be tested is determined to be normative.

Optionally, in the embodiment of the present invention, the second test result acquisition module is specifically used for:

Based on the preset grammatical normative situation, the irregularity type of the grammatical normative information is determined. The irregularity type includes the first irregularity type and the second irregularity type. The first irregularity type is used to characterize the grammatical irregularity of the grammatical normative information. The question is completely irregular, and the second type of irregularity used to represent grammatical normative information is incompletely standardized;

If the irregularity type of the grammar normative information is the first irregularity type, the grammar is set as a completely irregular grammar;

If the irregularity type of the grammar normative information is the second irregularity type, the grammar is set as a completely incomplete normative grammar.

For a description of the second test result acquisition module 114, reference may be made to the detailed description of the above step S400. That is, step S400 may be executed by the second test result acquisition module 114, and will not be described again here.

In summary, the JS code testing method, device and electronic equipment provided by the embodiments of the present invention can obtain the JS code to be tested and the first configuration file corresponding to the JS code to be tested, and simultaneously test the JS code to be tested based on the first configuration file Relative to the compatibility of the preset browser set, obtain the code compatibility test results of the JS code to be tested. In this way, when the JS code to be tested needs to be tested, the compatibility of the JS code to be tested with respect to the preset browser collection can be directly and simultaneously tested based on the first configuration file, thereby obtaining a code compatibility test of the JS code to be tested. As a result, compared with the existing technology that separately tests the compatibility of each browser with the JS code to be tested through manual testing, the testing efficiency is greatly improved.

In the several embodiments provided by the embodiments of the present invention, it should be understood that the disclosed devices and methods can also be implemented in other ways. The device and method embodiments described above are only illustrative. For example, the flowcharts and block diagrams in the accompanying drawings show possible implementation architectures of the devices, methods and computer program products according to multiple embodiments of the present disclosure. Functionality and operation. In this regard, each block in the flowchart or block diagram may represent a module, segment, or portion of code that contains one or more executable functions for implementing the specified logical function instruction. 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 consecutive blocks may actually execute substantially in parallel, or they may sometimes execute in the reverse order, depending on the functionality involved. It will also be noted that each block of the block diagram and/or flowchart illustration, and combinations of blocks in the block diagram and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts. , or can be implemented using a combination of specialized hardware and computer instructions.

In addition, each functional module in various embodiments of the present disclosure can be integrated together to form an independent part, each module can be included separately, or two or more modules can be integrated to form an independent part.

If functions are implemented in the form of software function modules and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present disclosure is essentially or the part that contributes to the existing technology or the part of the technical solution can be embodied in the form of a software product. The computer software product is stored in a storage medium, including Several instructions are used to cause a computer device (which may be a personal computer, electronic device, or network device, etc.) to execute all or part of the steps of the methods of various embodiments of the present disclosure. The aforementioned storage media include: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), magnetic disk or optical disk and other media that can store program code. It should be noted that, as used herein, the terms "include", "comprises" or any other variation thereof are intended to cover a non-exclusive inclusion, such that a process, method, article or device that includes a series of elements not only includes those elements, It also includes other elements not expressly listed or inherent in the process, method, article or equipment. Without further limitation, an element qualified by the statement "comprises a..." does not preclude the inclusion of additional identical elements in the process, method, article, or apparatus that includes the element.

The above are only optional embodiments of the present disclosure and are not intended to limit the present disclosure. For those skilled in the art, the present disclosure may have various modifications and changes. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of this disclosure shall be included in the protection scope of this disclosure.

A1. A JS code testing method, which is characterized by including:

Obtain the JS code to be tested and the first configuration file corresponding to the JS code to be tested;

Based on the first configuration file, the compatibility of the JS code to be tested with respect to a preset browser set is simultaneously tested to obtain a code compatibility test result of the JS code to be tested.

A2. The JS code testing method according to claim A1, characterized in that the JS code to be tested includes at least one target JS function, and the first configuration file includes at least one item used to characterize the JS function relative to the target JS function. Function compatibility information that is incompatible with the default browser set described above;

Simultaneously testing the compatibility of the JS code to be tested with respect to a preset browser set based on the first configuration file and obtaining the code compatibility test results of the JS code to be tested includes:

Based on at least one piece of the function compatibility information, respectively determine the function compatibility test results of each target JS function in the JS code to be tested relative to the preset browser set;

Determine the code compatibility test results of the JS code to be tested based on the function compatibility test results of all target JS functions in the JS code to be tested;

Wherein, if all target JS functions in the JS code to be tested are compatible with the preset browser set, the code compatibility test result of the JS code to be tested is determined to be compatible; otherwise, the code compatibility test result of the JS code to be tested is determined to be compatible. The code compatibility test result of the JS code to be tested is determined to be incompatible.

A3. The JS code testing method according to claim A2, characterized in that, based on at least one piece of the function compatibility information, it is determined respectively that each target JS function in the JS code to be tested is relative to the preset Function compatibility test results for the browser collection, including:

For each target JS function in the JS code to be tested, determine whether there is function compatibility information corresponding to the target JS function in the first configuration file;

If there is function compatibility information corresponding to the target JS function in the first configuration file, the function compatibility test result of the target JS function is determined according to the function compatibility information; otherwise, the function compatibility test result of the target JS function is determined. The function compatibility test result of the target JS function is determined to be compatible.

A4. The JS code testing method according to claim A3, wherein the function compatibility information includes function labels and function content corresponding to the function labels, and each function label corresponds to a JS function, so The function content is used to characterize the compatibility of the JS function corresponding to the function tag with respect to the browsers in the preset browser collection;

Determining the function compatibility test result of the target JS function based on the function compatibility information includes:

Based on the preset information association situation, the association type of the function compatibility information is determined. The association type includes a first association type and a second association type. The first association type is used to characterize the information in the first configuration file. There is no function compatibility information functionally associated with the function compatibility information, and the second association type is used to represent that there is function compatibility information functionally associated with the function compatibility information in the first configuration file;

If the association type of the function compatibility information is the first association type, determine the function compatibility test result of the target JS function according to the function compatibility information;

If the association type of the function compatibility information is the second association type, the target JS is determined based on the function content of the function compatibility information and the function content of the function compatibility information functionally associated with the function compatibility information. The function compatibility test results for the function.

A5. The JS code testing method according to claim A4, characterized in that the function content of the function compatibility information and the function content of the function compatibility information functionally associated with the function compatibility information are determined. The function compatibility test results of the target JS function include:

According to the function content of the function compatibility information, a browser compatible with the JS function corresponding to the function compatibility information is obtained as the first browser;

The function compatibility information functionally associated with the function compatibility information is used as the associated function compatibility information, and based on the function content of the associated function compatibility information, a function compatible with the JS function corresponding to the associated function compatibility information is obtained. Browser, as a second browser;

Determine whether the set of the first browser and the second browser is the same as the default browser set;

If the set of the first browser and the second browser is the same as the preset browser set, it is determined that the function compatibility test result of the target JS function is compatible; otherwise, it is determined that the target JS function is compatible. The function compatibility test result of the JS function is incompatible.

A6. The JS code testing method according to claim A4, characterized in that when the function compatibility test result of the target JS function is incompatible, the target is determined based on the function compatibility information. The function compatibility test results of JS functions also include:

Based on the preset browser compatibility situation, the incompatibility type of the function compatibility information is determined. The incompatibility type includes a first incompatibility type and a second incompatibility type. The first incompatibility type is used to characterize the The incompatibility of the function compatibility information is completely incompatible, and the second incompatibility type is used to characterize the incompatibility of the function compatibility information as incomplete compatibility;

If the incompatibility type of the function compatibility information is the first incompatibility type, determine the function compatibility result of the target JS function to be completely incompatible;

If the incompatibility type of the function compatibility information is the second incompatibility type, the function compatibility result of the target JS function is determined to be incompletely compatible.

A7. The JS code testing method according to claim A1, characterized in that the JS code testing method further includes:

Obtain the second configuration file corresponding to the JS code to be tested;

The syntax standardization of the JS code to be tested is tested based on the second configuration file, and the code syntax standardization test result of the JS code to be tested is obtained.

A8. The JS code testing method according to claim A7, characterized in that the second configuration file includes at least one piece of grammatical normative information used to characterize the grammatical irregularities of the JS code to be tested;

The method of testing the syntax standardization of the JS code to be tested based on the second configuration file and obtaining the code syntax standardization test results of the JS code to be tested includes:

For each piece of grammatical normative information, determine whether there is a grammatical setting corresponding to the grammatical normative information in the JS code to be tested;

If there is a grammar setting corresponding to the grammar normative information in the JS code to be tested, the grammar setting is regarded as non-standard grammar;

If the non-standard syntax exists in the JS code, it is determined that the code syntax normative test result of the JS code to be tested is non-standard; otherwise, it is determined that the code syntax normative test result of the JS code to be tested is normative. .

A9. The JS code testing method according to claim A8, characterized in that if there is a grammar setting corresponding to the grammar normative information in the JS code to be tested, the grammar setting is regarded as non-standard grammar, include:

Based on the preset grammatical normative situation, the irregularity type of the grammatical normative information is determined. The irregularity type includes a first irregularity type and a second irregularity type. The first irregularity type is used to characterize the The grammatical irregularities of the grammatical normative information are completely irregular, and the second irregularity type used to characterize the irregularities of the grammatical normative information is incompletely normative;

If the irregularity type of the grammar normative information is the first irregularity type, then the grammar is set as a completely irregular grammar;

If the irregularity type of the grammar normative information is the second irregularity type, the grammar is set as a completely incomplete normative grammar.

B10. A JS code testing device, which is characterized by including:

The first configuration file acquisition module is used to obtain the JS code to be tested and the first configuration file corresponding to the JS code to be tested;

The first test result acquisition module is configured to simultaneously test the compatibility of the JS code to be tested with respect to the preset browser collection based on the first configuration file, and obtain the code compatibility test results of the JS code to be tested.

B11. The JS code testing device according to claim B10, wherein the JS code to be tested includes at least one target JS function, and the first configuration file includes at least one item used to characterize the JS function relative to the target JS function. Function compatibility information that is incompatible with the default browser set described above;

The first test result acquisition module is specifically used for:

Based on at least one piece of the function compatibility information, respectively determine the function compatibility test results of each target JS function in the JS code to be tested relative to the preset browser set;

Determine the code compatibility test results of the JS code to be tested based on the function compatibility test results of all target JS functions in the JS code to be tested;

Wherein, if all target JS functions in the JS code to be tested are compatible with the preset browser set, the code compatibility test result of the JS code to be tested is determined to be compatible; otherwise, the code compatibility test result of the JS code to be tested is determined to be compatible. The code compatibility test result of the JS code to be tested is determined to be incompatible.

B12. The JS code testing device according to claim B10, characterized in that the first test result acquisition module is specifically used for:

For each target JS function in the JS code to be tested, determine whether there is function compatibility information corresponding to the target JS function in the first configuration file;

If there is function compatibility information corresponding to the target JS function in the first configuration file, the function compatibility test result of the target JS function is determined according to the function compatibility information; otherwise, the function compatibility test result of the target JS function is determined. The function compatibility test result of the target JS function is determined to be compatible.

B13. The JS code testing device according to claim B12, wherein the function compatibility information includes function labels and function content corresponding to the function labels, and each function label corresponds to a JS function, so The function content is used to characterize the compatibility of the JS function corresponding to the function tag with respect to the browsers in the preset browser collection;

The first test result acquisition module is specifically used for:

Based on the preset information association situation, the association type of the function compatibility information is determined. The association type includes a first association type and a second association type. The first association type is used to characterize the information in the first configuration file. There is no function compatibility information functionally associated with the function compatibility information, and the second association type is used to represent that there is function compatibility information functionally associated with the function compatibility information in the first configuration file;

If the association type of the function compatibility information is the first association type, determine the function compatibility test result of the target JS function according to the function compatibility information;

If the association type of the function compatibility information is the second association type, the target JS is determined based on the function content of the function compatibility information and the function content of the function compatibility information functionally associated with the function compatibility information. The function compatibility test results for the function.

B14. The JS code testing device according to claim B13, characterized in that the first test result acquisition module is specifically used for:

According to the function content of the function compatibility information, a browser compatible with the JS function corresponding to the function compatibility information is obtained as the first browser;

The function compatibility information functionally associated with the function compatibility information is used as the associated function compatibility information, and based on the function content of the associated function compatibility information, a function compatible with the JS function corresponding to the associated function compatibility information is obtained. Browser, as a second browser;

Determine whether the set of the first browser and the second browser is the same as the default browser set;

If the set of the first browser and the second browser is the same as the preset browser set, it is determined that the function compatibility test result of the target JS function is compatible; otherwise, it is determined that the target JS function is compatible. The function compatibility test result of the JS function is incompatible.

B15. The JS code testing device according to claim B13, characterized in that when the function compatibility test result of the target JS function is incompatible, the first test result acquisition module is also specifically used to :

Based on the preset browser compatibility situation, the incompatibility type of the function compatibility information is determined. The incompatibility type includes a first incompatibility type and a second incompatibility type. The first incompatibility type is used to characterize the The incompatibility of the function compatibility information is completely incompatible, and the second incompatibility type is used to characterize the incompatibility of the function compatibility information as incomplete compatibility;

If the incompatibility type of the function compatibility information is the first incompatibility type, determine the function compatibility result of the target JS function to be completely incompatible;

If the incompatibility type of the function compatibility information is the second incompatibility type, the function compatibility result of the target JS function is determined to be incompletely compatible.

B16. The JS code testing device according to claim B10, characterized in that the JS code testing device further includes:

The second configuration file acquisition module is used to obtain the second configuration file corresponding to the JS code to be tested;

The second test result acquisition module is configured to test the syntax standardization of the JS code to be tested based on the second configuration file, and obtain the code syntax standardization test results of the JS code to be tested.

B17. The JS code testing device according to claim B16, wherein the second configuration file includes at least one piece of grammatical normative information used to characterize the grammatical irregularities of the JS code to be tested;

The second test result acquisition module is specifically used for:

For each piece of grammatical normative information, determine whether there is a grammatical setting corresponding to the grammatical normative information in the JS code to be tested;

If there is a grammar setting corresponding to the grammar normative information in the JS code to be tested, the grammar setting is regarded as non-standard grammar;

If the non-standard syntax exists in the JS code, it is determined that the code syntax normative test result of the JS code to be tested is non-standard; otherwise, it is determined that the code syntax normative test result of the JS code to be tested is normative. .

B18. The JS code testing device according to claim B17, characterized in that the second test result acquisition module is specifically used for:

Based on the preset grammatical normative situation, the irregularity type of the grammatical normative information is determined. The irregularity type includes a first irregularity type and a second irregularity type. The first irregularity type is used to characterize the The grammatical irregularities of the grammatical normative information are completely irregular, and the second irregularity type used to characterize the irregularities of the grammatical normative information is incompletely normative;

If the irregularity type of the grammar normative information is the first irregularity type, then the grammar is set as a completely irregular grammar;

If the irregularity type of the grammar normative information is the second irregularity type, the grammar is set as a completely incomplete normative grammar.

C19. An electronic device, characterized by comprising a processor, a memory and the JS code testing device of claims B10-B18, the JS code testing device including one or more devices stored in the memory and configured by the Software function modules executed by the processor.

D20. A computer-readable storage medium with a computer program stored thereon, characterized in that when the computer program is executed, the JS code testing method described in any one of claims A1-A9 can be implemented.

Claims (18)

1. The JS code testing method is characterized by comprising the following steps of:

acquiring a JS code to be tested and a first configuration file corresponding to the JS code to be tested;

based on the first configuration file, simultaneously testing the compatibility of the JS codes to be tested relative to a preset browser set, and obtaining a code compatibility test result of the JS codes to be tested;

the to-be-tested JS code comprises at least one target JS function, the first configuration file comprises at least one piece of function compatibility information for representing that the JS function is incompatible with the preset browser set, the function compatibility information comprises function labels and function contents, each function label corresponds to one JS function, and the function contents are used for representing that the JS function corresponding to the function label is compatible or incompatible with a browser in the preset browser set;

The step of simultaneously testing the compatibility of the JS code to be tested relative to a preset browser set based on the first configuration file to obtain a code compatibility test result of the JS code to be tested includes:

based on at least one piece of function compatibility information, respectively determining a function compatibility test result of each target JS function in the JS code to be tested relative to the preset browser set;

determining a code compatibility test result of the JS codes to be tested according to function compatibility test results of all target JS functions in the JS codes to be tested;

and if all the target JS functions in the JS codes to be tested are compatible with the preset browser set, determining that the code compatibility test results of the JS codes to be tested are compatible, otherwise, determining that the code compatibility test results of the JS codes to be tested are incompatible.

2. The JS code testing method of claim 1, wherein the determining, based on at least one piece of the function compatibility information, a function compatibility test result of each target JS function in the JS code to be tested with respect to the preset browser set, includes:

For each target JS function in the JS code to be tested, judging whether function compatibility information corresponding to the target JS function exists in the first configuration file or not respectively;

if the function compatibility information corresponding to the target JS function exists in the first configuration file, determining the function compatibility test result of the target JS function according to the function compatibility information, otherwise, determining the function compatibility test result of the target JS function as compatible.

3. The JS code test method of claim 2, wherein the function compatibility information includes function labels and function content corresponding to the function labels, each function label corresponding to a JS function, the function content being used to characterize compatibility of the JS function corresponding to the function label with respect to a browser in the preset browser set;

the determining the function compatibility test result of the target JS function according to the function compatibility information includes:

determining an association type of the function compatibility information based on a preset information association condition, wherein the association type comprises a first association type and a second association type, the first association type is used for representing that function compatibility information associated with the function compatibility information function does not exist in the first configuration file, and the second association type is used for representing that function compatibility information associated with the function compatibility information function exists in the first configuration file;

If the association type of the function compatibility information is the first association type, determining the function compatibility test result of the target JS function according to the function compatibility information;

and if the association type of the function compatibility information is the second association type, determining the function compatibility test result of the target JS function according to the function content of the function compatibility information and the function content of the function compatibility information functionally associated with the function compatibility information.

4. The JS code test method of claim 3, wherein the determining the function compatibility test result for the target JS function based on the function content of the function compatibility information and the function content of the function compatibility information functionally associated with the function compatibility information includes:

obtaining a browser compatible with a JS function corresponding to the function compatibility information as a first browser according to the function content of the function compatibility information;

the function compatibility information functionally associated with the function compatibility information is used as associated function compatibility information, and a browser compatible with a JS function corresponding to the associated function compatibility information is obtained as a second browser according to the function content of the associated function compatibility information;

Judging whether the set of the first browser and the second browser is the same as the preset browser set or not;

and if the set of the first browser and the second browser is the same as the preset browser set, determining that the function compatibility test result of the target JS function is compatible, otherwise, determining that the function compatibility test result of the target JS function is incompatible.

5. The JS code test method of claim 3, wherein when the function compatibility test result of the target JS function is incompatible, the determining the function compatibility test result of the target JS function from the function compatibility information further includes:

determining an incompatibility type of the function compatibility information based on a preset browser compatibility condition, wherein the incompatibility type comprises a first incompatibility type and a second incompatibility type, the first incompatibility type is used for representing that the incompatibility condition of the function compatibility information is completely incompatibility, and the second incompatibility type is used for representing that the incompatibility condition of the function compatibility information is not completely compatibility;

if the incompatible type of the function compatibility information is the first incompatible type, determining that the function compatibility result of the target JS function is completely incompatible;

And if the incompatible type of the function compatibility information is the second incompatible type, determining that the function compatibility result of the target JS function is not completely compatible.

6. The JS code test method of claim 1, further comprising:

acquiring a second configuration file corresponding to the JS code to be tested;

and testing the grammar standardability of the JS codes to be tested based on the second configuration file, and obtaining a code grammar standardability test result of the JS codes to be tested.

7. The JS code testing method of claim 6, wherein the second configuration file includes at least one piece of grammar normalization information for characterizing a grammar non-normalization problem of the JS code to be tested;

the step of testing the grammar normalization of the JS code to be tested based on the second configuration file to obtain a code grammar normalization test result of the JS code to be tested, including:

judging whether grammar setting corresponding to the grammar normalization information exists in the JS codes to be tested according to each piece of grammar normalization information;

if the JS codes to be tested have grammar setting corresponding to the grammar normalization information, setting the grammar as non-canonical grammar;

If the non-standard grammar exists in the JS codes, determining that the code grammar standardability test result of the JS codes to be tested is non-standard, otherwise, determining that the code grammar standardability test result of the JS codes to be tested is standard.

8. The JS code test method of claim 7, wherein if there is a grammar setting corresponding to the grammar normalization information in the JS code to be tested, then setting the grammar as an unnormalized grammar includes:

determining an irregular type of the grammar normalization information based on a preset grammar normalization condition, wherein the irregular type comprises a first irregular type and a second irregular type, the first irregular type is used for representing that grammar irregular questions of the grammar normalization information are completely irregular, and the second irregular type is used for representing that the irregular questions of the grammar normalization information are incompletely standardized;

if the non-canonical type of the grammar normalization information is the first non-canonical type, setting the grammar as a completely non-canonical grammar;

and if the non-canonical type of the grammar normalization information is the second non-canonical type, setting the grammar as an incomplete canonical grammar.

9. A JS code test device, characterized by:

the device comprises a first configuration file acquisition module, a second configuration file acquisition module and a test module, wherein the first configuration file acquisition module is used for acquiring a JS code to be tested and a first configuration file corresponding to the JS code to be tested;

the first test result obtaining module is used for simultaneously testing the compatibility of the JS codes to be tested relative to a preset browser set based on the first configuration file and obtaining a code compatibility test result of the JS codes to be tested;

the to-be-tested JS code comprises at least one target JS function, the first configuration file comprises at least one piece of function compatibility information for representing that the JS function is incompatible with the preset browser set, the function compatibility information comprises function labels and function contents, each function label corresponds to one JS function, and the function contents are used for representing that the JS function corresponding to the function label is compatible or incompatible with a browser in the preset browser set;

the first test result obtaining module is specifically configured to:

based on at least one piece of function compatibility information, respectively determining a function compatibility test result of each target JS function in the JS code to be tested relative to the preset browser set;

Determining a code compatibility test result of the JS codes to be tested according to function compatibility test results of all target JS functions in the JS codes to be tested;

and if all the target JS functions in the JS codes to be tested are compatible with the preset browser set, determining that the code compatibility test results of the JS codes to be tested are compatible, otherwise, determining that the code compatibility test results of the JS codes to be tested are incompatible.

10. The JS code test device of claim 9, wherein the first test result acquisition module is further specifically configured to:

for each target JS function in the JS code to be tested, judging whether function compatibility information corresponding to the target JS function exists in the first configuration file or not respectively;

if the function compatibility information corresponding to the target JS function exists in the first configuration file, determining the function compatibility test result of the target JS function according to the function compatibility information, otherwise, determining the function compatibility test result of the target JS function as compatible.

11. The JS code test device of claim 10, wherein the function compatibility information includes function labels and function content corresponding to the function labels, each function label corresponding to a JS function, the function content being used to characterize compatibility of the JS function corresponding to the function label with respect to a browser in the preset browser set;

The first test result obtaining module is specifically further configured to:

determining an association type of the function compatibility information based on a preset information association condition, wherein the association type comprises a first association type and a second association type, the first association type is used for representing that function compatibility information associated with the function compatibility information function does not exist in the first configuration file, and the second association type is used for representing that function compatibility information associated with the function compatibility information function exists in the first configuration file;

if the association type of the function compatibility information is the first association type, determining the function compatibility test result of the target JS function according to the function compatibility information;

and if the association type of the function compatibility information is the second association type, determining the function compatibility test result of the target JS function according to the function content of the function compatibility information and the function content of the function compatibility information functionally associated with the function compatibility information.

12. The JS code test device of claim 11, wherein the first test result acquisition module is further specifically configured to:

Obtaining a browser compatible with a JS function corresponding to the function compatibility information as a first browser according to the function content of the function compatibility information;

the function compatibility information functionally associated with the function compatibility information is used as associated function compatibility information, and a browser compatible with a JS function corresponding to the associated function compatibility information is obtained as a second browser according to the function content of the associated function compatibility information;

judging whether the set of the first browser and the second browser is the same as the preset browser set or not;

and if the set of the first browser and the second browser is the same as the preset browser set, determining that the function compatibility test result of the target JS function is compatible, otherwise, determining that the function compatibility test result of the target JS function is incompatible.

13. The JS code test device of claim 11, wherein when the function compatibility test result of the target JS function is incompatible, the first test result acquisition module is further specifically configured to:

determining an incompatibility type of the function compatibility information based on a preset browser compatibility condition, wherein the incompatibility type comprises a first incompatibility type and a second incompatibility type, the first incompatibility type is used for representing that the incompatibility condition of the function compatibility information is completely incompatibility, and the second incompatibility type is used for representing that the incompatibility condition of the function compatibility information is not completely compatibility;

If the incompatible type of the function compatibility information is the first incompatible type, determining that the function compatibility result of the target JS function is completely incompatible;

and if the incompatible type of the function compatibility information is the second incompatible type, determining that the function compatibility result of the target JS function is not completely compatible.

14. The JS code test device of claim 9, further comprising:

the second configuration file acquisition module is used for acquiring a second configuration file corresponding to the JS code to be tested;

and the second test result acquisition module is used for testing the grammar normalization of the JS codes to be tested based on the second configuration file and acquiring a code grammar normalization test result of the JS codes to be tested.

15. The JS code test device of claim 14, wherein the second configuration file includes at least one piece of grammar normalization information for characterizing a grammar non-normalization problem of the JS code to be tested;

the second test result obtaining module is specifically configured to:

judging whether grammar setting corresponding to the grammar normalization information exists in the JS codes to be tested according to each piece of grammar normalization information;

If the JS codes to be tested have grammar setting corresponding to the grammar normalization information, setting the grammar as non-canonical grammar;

if the non-standard grammar exists in the JS codes, determining that the code grammar standardability test result of the JS codes to be tested is non-standard, otherwise, determining that the code grammar standardability test result of the JS codes to be tested is standard.

16. The JS code test device of claim 15, wherein the second test result acquisition module is further specifically configured to:

determining an irregular type of the grammar normalization information based on a preset grammar normalization condition, wherein the irregular type comprises a first irregular type and a second irregular type, the first irregular type is used for representing that grammar irregular questions of the grammar normalization information are completely irregular, and the second irregular type is used for representing that the irregular questions of the grammar normalization information are incompletely standardized;

if the non-canonical type of the grammar normalization information is the first non-canonical type, setting the grammar as a completely non-canonical grammar;

and if the non-canonical type of the grammar normalization information is the second non-canonical type, setting the grammar as an incomplete canonical grammar.

17. An electronic device comprising a processor, a memory, and the JS code testing apparatus of claims 9-16, the JS code testing apparatus including one or more software functional modules stored in the memory and executed by the processor.

18. A computer-readable storage medium having a computer program stored thereon, wherein the computer program, when executed, implements the JS code test method of any one of claims 1-8.