A unified interface application supervision method and system for multi-terminal integration

Abstract

The present invention discloses a unified interface application supervision method and system for multi-terminal integration, which belongs to the field of application supervision technology. By constructing the application layer, abstraction layer and test layer, the generation of demand code packages, the adaptive construction of component architecture and the setting of cross-platform test scripts are realized. The component architecture to be tested is collected through the supervision processing center, and a monitoring sample set is generated. The component architecture adaptability evaluation model and the script adjustment model are used to optimize the components and evaluate the achievement rate of the test scripts. The present invention can adaptively optimize components as cross-platform requirements change, intelligently adjust scripts, and ensure the integrated response of the application service end, the code development end and the script testing end. The system implementation includes a business execution logic module and a supervision processing center module to achieve efficient supervision of diversified unified interface applications and improve development efficiency and user experience.

Description

Technical Field

[0001] The present invention relates to the field of application supervision technology, and specifically to a unified interface application supervision method and system for multi-terminal integration. Background Art

[0002] With the rapid development of mobile internet and multiple terminal devices, cross-platform application development has become a core requirement for improving development efficiency and reducing maintenance costs. While mainstream cross-platform frameworks on the market (such as Flutter and React Native) achieve code reuse to a certain extent by providing unified development interfaces, they still face the following significant challenges:

[0003] The separation of business logic and UI adaptation: In existing technologies, although some business logic can be reused across platforms, the UI display requirements of different platforms often need to be adjusted separately. Developers need to write differentiated code for each platform, resulting in a high degree of coupling between business logic and UI implementation, making it difficult to achieve true "write once, run on multiple platforms";

[0004] Low test coverage and adaptation efficiency: Cross-platform application testing typically relies on manually written multiple sets of platform-specific test scripts. Test cases are fragmented and lack unified management. Existing testing tools struggle to dynamically assess component compatibility on different platforms, and test scripts can't automatically optimize as requirements change. This results in low test completion rates and high maintenance costs.

[0005] Rigid component architecture and delayed optimization: In traditional development processes, component architecture is difficult to dynamically adjust after the application is launched. When cross-platform requirements change, components must be manually rebuilt and revalidated, lacking an adaptive optimization mechanism. Furthermore, component updates and test scripts are often disconnected, resulting in inefficient collaboration between development, testing, and deployment.

[0006] Lack of supervision and feedback mechanisms: Existing solutions lack integrated supervision capabilities for development, testing, and operation. Data in each link is isolated, and closed-loop feedback cannot be formed. It is difficult to monitor component performance, script coverage, and platform adaptation status in real time, which in turn affects the agility of application iteration. Summary of the Invention

[0007] The purpose of the present invention is to provide a unified interface application supervision method and system for multi-terminal integration to solve the problems raised in the above background technology.

[0008] In order to solve the above technical problems, the present invention provides the following technical solutions:

[0009] A unified interface application supervision system for multi-terminal integration, the system includes: business execution logic module and supervision processing center module;

[0010] The business execution logic module is used to construct the application layer, abstraction layer and test layer; the application layer is used to code programmatically calculate application requirements for cross-platform display, generate requirement code packages, and compile a standardized component architecture before the application is launched to instruct the business execution logic of the components; the abstraction layer is used to set the import interface and shared library of the requirement code package, and when the requirement code package is transplanted through the import interface, the standardized component architecture before the application is launched is converted into the component architecture to be tested after the application is launched; the test layer sets sub-scripts based on the business execution logic of the application, and the sub-scripts constitute a unified test script for the application across platforms, and the test script is used to test the component architecture to be tested;

[0011] The supervision processing center module is used to build a supervision processing center, collect several component architectures to be tested that are adaptively constructed corresponding to the standardized component architecture to generate a monitoring sample set, and extract the test script under the cross-platform test script to generate a sub-script group set.

[0012] Furthermore, the business execution logic module includes an application layer unit, an abstract layer unit and a test layer unit;

[0013] The application layer unit is used to code programmatically determine the application requirements of the unified interface application when displayed across platforms, and to perform program annotations to obtain a requirement code package; based on the business execution logic of the application, a standardized component architecture is compiled before the application is launched, and an import interface for the requirement code package of the standardized component architecture is set to receive and execute the application requirements after the code is programmed;

[0014] The abstract layer unit transplants the required code package through the set import interface of the required code package of the standardized component architecture to achieve the adaptive structure; the abstract layer has a built-in shared library, and the required code package is stored in the shared library. When each component in the standardized component architecture is connected to the shared library through the import interface to achieve the transplantation of the required code package, the component architecture to be tested after the application is put on the shelf is obtained;

[0015] The test layer unit sets and stores a cross-platform test script for the application based on the business execution logic of the application. The test script contains several sub-scripts, where one sub-script corresponds to testing a component; an identifier of the sub-script is set, and the identifier has a unified relationship with the program annotation of the required code package. The sub-script is uniformly encoded through the identifier or program annotation, and each transplanted component in the component architecture to be tested is matched by identifying the identifier of the sub-script.

[0016] Furthermore, the supervision processing center module includes a fitness analysis unit and a test calibration unit;

[0017] The fitness analysis unit is used to collect a plurality of adaptively constructed component architectures to be tested corresponding to a standardized component architecture when performing a test script run test on the adaptively constructed component architecture to be tested under the standardized component architecture, generate a monitoring sample set, and construct a component architecture fitness evaluation model to optimize the monitoring sample set;

[0018] The test calibration unit is used to extract the test script in a cross-platform test script to generate a sub-script set after the identifier of the sub-script is matched with the program annotation of the requirement code package corresponding to each transplanted component in the component architecture to be tested, and to build a script adjustment model to evaluate the test achievement rate of the test script so as to select the optimal component architecture after the application is launched.

[0019] A unified interface application supervision method for multi-terminal integration, the method comprising the following steps:

[0020] Build the application layer, program the application requirements for cross-platform display, generate the required code package, and compile a standardized component architecture before the application is launched to instruct the business execution logic of the component;

[0021] Build an abstraction layer and set up the import interface and shared library of the required code package. When implementing the required code package through the import interface, convert the standardized component architecture before the application is launched into the component architecture to be tested after the application is launched.

[0022] Build a test layer, set sub-scripts based on the application's business execution logic, and use the sub-scripts to form a unified test script across platforms. Use the test scripts to test the component architecture to be tested.

[0023] Build a monitoring processing center to collect several component architectures to be tested that are adaptively constructed based on standardized component architectures to generate monitoring sample sets. Under the cross-platform test scripts, extract the test scripts to generate sub-script sets.

[0024] Build a component architecture adaptability evaluation model and optimize the monitoring sample set. After the optimization is completed, build a script adjustment model to evaluate the test achievement rate of the test script, and analyze and lock the component architecture to be tested through the test achievement rate.

[0025] Furthermore, the specific implementation process of building the application layer includes:

[0026] The application requirements of the unified interface application when displayed across platforms are programmed into code, and program annotations are performed to obtain a requirement code package, wherein one requirement code package corresponds to one application requirement programmed into code, and the requirement code package is uniformly coded, and the requirement refers to the display requirements of the application on different platform interfaces;

[0027] Based on the business execution logic of the application, a standardized component architecture is compiled before the application is put on the shelf, wherein the standardized component architecture is used to instruct the business execution logic of the component, and one component corresponds to an application requirement after code programming, and the component is defined by the requirement code package; the standardized component architecture is uniformly coded, and an import interface of the requirement code package of the standardized component architecture is set to receive and run the application requirement after code programming.

[0028] Furthermore, the specific implementation process of building the abstraction layer includes:

[0029] The abstract layer is used to implement the adaptive construction of the standardized component architecture, and to transplant the required code package through the set import interface of the required code package of the standardized component architecture to implement the adaptive construction;

[0030] A shared library is built into the abstract layer, and the required code package is stored in the shared library. When each component in the standardized component architecture is connected to the shared library through an import interface to realize the transplantation of the required code package, the component architecture to be tested after the application is put on the shelf is obtained.

[0031] Furthermore, the specific implementation process of building the test layer includes:

[0032] The test layer sets and stores cross-platform test scripts based on the application's business execution logic, and tests the component architecture to be tested through the test scripts; the test scripts contain several sub-scripts, where one sub-script tests one component;

[0033] An identifier of the sub-script is set, wherein the identifier has a unified relationship with the program annotation of the required code package, the sub-script is uniformly encoded through the identifier or program annotation, and each transplanted component in the component architecture to be tested is matched by identifying the identifier of the sub-script.

[0034] Furthermore, the specific implementation process of building a regulatory processing center includes:

[0035] Under the standardized component architecture, when running the test script for the adaptively constructed component architecture to be tested, a standardized component architecture corresponding to several adaptively constructed component architectures to be tested is collected and a monitoring sample set is generated, which is recorded as SCA i ={CCA e |e∈[1, E]}, where i represents the coding number of the standardized component architecture, SCA i represents the monitoring sample set generated by the i-th standardized component architecture, CCA e represents the set of components transplanted in the e-th component architecture to be tested, and CCAe ={DCP r |r∈[1, R]}, E represents the total number of component architectures to be tested, DCP r represents the rth required code package, and R represents the total number of required code packages;

[0036] In the cross-platform test script, when the sub-script identifier matches the program annotation of the required code package corresponding to each transplanted component in the component architecture to be tested, the test script is extracted to generate a sub-script set, which is recorded as S(CCA e ), where S(CCA e ) represents the component collection CCA e The corresponding sub-script set is generated.

[0037] Furthermore, the specific implementation methods of constructing a component architecture adaptability evaluation model and optimizing the monitoring sample set include:

[0038] When the e-th component architecture to be tested is adaptively constructed, the component collection CCA is called e , and run the component collection CCA e Each requirement code package in the record running requirement code package DCP r In the component collection CCA e The smoothness of the Where, t k Indicates the requirement code package DCP under the preset kth abnormal condition r The time it takes for the entire process from starting the operation to resuming the operation and completing the operation, T k Indicates that in the component set CCA e Pre-assigned to Demand Code Package DCP r Initialization runtime of

[0039] Preset smoothness threshold, if smoothness SD(DCP r ) is less than or equal to the smoothness threshold, the demand code package DCP r Replace and re-port it to the e-th component architecture to be tested to generate a new component architecture to be tested, and continue to evaluate the smoothness of the re-ported requirement code package under the new component architecture to be tested; if the smoothness SD(DCP r ) is greater than the smoothness threshold, then the component set CCA e Record to monitoring sample set SCA i middle.

[0040] Furthermore, the specific implementation of constructing a script adjustment model and evaluating the test achievement rate of the test script includes:

[0041] In the monitoring sample set SCAi Calculate the test success rate of the test script Where G represents the total number of sub-scripts contained in the extracted test script. Indicates the monitoring sample set SCA i The corresponding generated sub-script set S(CCA e ), μ is the mean, and σ 2 is the variance, and

[0042] Preset test achievement rate threshold. If the test achievement rate of the test script is less than or equal to the test achievement rate threshold, the tester will be prompted to adjust the test script and recalculate the test achievement rate of the test script until the test achievement rate of the test script is greater than the test achievement rate threshold. The maximum value is selected. The corresponding e-th component architecture to be tested is used as the optimal component architecture after the application is launched.

[0043] Compared with the prior art, the beneficial effects achieved by the present invention are as follows: in the unified interface application supervision method and system for multi-terminal integration provided by the present invention, by constructing the application layer, abstraction layer and test layer, the generation of required code packages, the adaptive construction of component architecture and the setting of cross-platform test scripts are realized, the component architecture to be tested is collected through the supervision processing center, a monitoring sample set is generated, and the component architecture adaptability evaluation model and the script adjustment model are used to optimize the components and evaluate the achievement rate of the test scripts; the present invention can adaptively optimize components as cross-platform requirements change, intelligently adjust scripts, and ensure the integrated response of the application server, code development end and script testing end; the system implementation includes a business execution logic module and a supervision processing center module, which realizes efficient supervision of diversified unified interface applications and improves development efficiency and user experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0044] The accompanying drawings are used to provide further understanding of the present invention and constitute a part of the specification. They are used to explain the present invention together with the embodiments of the present invention and do not constitute a limitation of the present invention.

[0045] Figure 1 It is a schematic diagram of the steps of a unified interface application supervision method for multi-terminal integration of the present invention. DETAILED DESCRIPTION

[0046] The following will clearly and completely describe the technical solutions in the embodiments of the present invention in conjunction with the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of the present invention.

[0047] In this first embodiment, a unified interface application supervision system for multi-terminal integration is provided, which includes:

[0048] The business execution logic module is used to build the application layer, abstraction layer, and test layer. The application layer is used to programmatically code application requirements for cross-platform display, generate requirement code packages, and compile a standardized component architecture before the application is launched to instruct the business execution logic of the components. The abstraction layer is used to set the import interface and shared library of the requirement code package. When the requirement code package is transplanted through the import interface, the standardized component architecture before the application is launched is converted into the component architecture to be tested after the application is launched. The test layer sets sub-scripts based on the application's business execution logic, and the sub-scripts form a unified test script for the application across platforms, and the test scripts are used to test the component architecture to be tested.

[0049] Among them, the business execution logic module includes application layer unit, abstract layer unit and test layer unit;

[0050] The application layer unit is used to program the application requirements of the unified interface application when displaying across platforms, and perform program annotation to obtain the required code package. Based on the business execution logic of the application, a standardized component architecture is compiled before the application is launched, and an import interface for the required code package of the standardized component architecture is set up to receive and run the application requirements after coding.

[0051] The abstract layer unit transplants the required code package through the import interface of the standardized component architecture to achieve adaptive construction. The abstract layer has a built-in shared library, which stores the required code package. When each component in the standardized component architecture connects to the shared library through the import interface to transplant the required code package, the component architecture to be tested after the application is launched is obtained.

[0052] The test layer unit sets and stores cross-platform test scripts for the application based on the application's business execution logic. The test script contains several sub-scripts, where each sub-script tests a component. The sub-script identifier is set, and the identifier has a unified relationship with the program annotation of the required code package. The sub-script is uniformly encoded through the identifier or program annotation, and each transplanted component in the component architecture to be tested is matched by identifying the sub-script identifier.

[0053] It should be noted that in the early stage, it is necessary to design native code packages, release rules and packaging rules to ensure the consistency of service quality of applications on different terminals and meet the unified configuration of applications on the terminals to provide flexibility and efficiency in interface management; calls on each terminal must also set and follow unified standards to ensure the stable operation of applications on different platforms; in addition, by monitoring interface data (such as fluctuations, traffic conditions and other abnormal conditions in the testing phase), the stability of the application before going online is ensured, and through the application on and off the shelves process, pre-listing testing and multi-terminal adaptation capability evaluation, the compatibility and user experience of the application on different terminals are ensured.

[0054] The monitoring and processing center module is used to build a monitoring and processing center, collect several component architectures to be tested that are adaptively constructed based on standardized component architectures to generate monitoring sample sets, and extract test scripts under cross-platform test scripts to generate sub-script sets;

[0055] Among them, the supervision processing center module includes the fitness analysis unit and the test calibration unit;

[0056] The adaptability analysis unit is used to collect data corresponding to a number of adaptively constructed component architectures to be tested under a standardized component architecture when running a test script on the adaptively constructed component architecture to be tested, generate a monitoring sample set, and build a component architecture adaptability evaluation model to optimize the monitoring sample set;

[0057] The test calibration unit is used to extract the test script from the cross-platform test script to generate a sub-script set after the sub-script identifier matches the program annotation of the required code package corresponding to each transplanted component in the component architecture to be tested. It also constructs a script adjustment model to evaluate the test achievement rate of the test script to select the optimal component architecture after the application is launched.

[0058] It should be noted that after the application is launched, the system can regularly implement continuous monitoring through scripts to monitor the application's operating status and conduct service inspections. Once abnormal situations such as application unavailability, network instability or interface downtime are found, the early warning mechanism will be triggered immediately and feedback will be provided simultaneously on multiple platforms to ensure that the problem is handled in a timely manner.

[0059] See also Figure 1 In the second embodiment, a unified interface application supervision method for multi-terminal integration is provided to be applied to the first embodiment. The method includes the following steps:

[0060] Build the application layer, program the application requirements for cross-platform display, generate the required code package, and compile a standardized component architecture before the application is launched to instruct the business execution logic of the component;

[0061] Exemplarily, the specific implementation process of building the application layer includes:

[0062] The application requirements of the unified interface application when displayed across platforms are programmed into code, and program annotations are performed to obtain a requirement code package. Among them, one requirement code package corresponds to one application requirement programmed into code, and the requirement code package is uniformly coded. The requirement refers to the display requirements of the application interface on different platforms;

[0063] For example, application requirements can be the interface size, interface resolution, or interface color of the application across platforms;

[0064] Based on the business execution logic of the application, a standardized component architecture is compiled before the application is put on the shelf. The standardized component architecture is used to instruct the business execution logic of the component, and one component corresponds to an application requirement after code programming, and the component is defined by the requirement code package; the standardized component architecture is uniformly coded, and an import interface of the requirement code package of the standardized component architecture is set to receive and run the application requirements after code programming.

[0065] Build an abstraction layer and set up the import interface and shared library of the required code package. When implementing the required code package through the import interface, convert the standardized component architecture before the application is launched into the component architecture to be tested after the application is launched.

[0066] Exemplarily, the specific implementation process of building the abstraction layer includes:

[0067] The abstract layer is used to implement the adaptive construction of the standardized component architecture and to transplant the required code package through the set import interface of the required code package of the standardized component architecture to achieve the adaptive construction;

[0068] A shared library is built into the abstract layer, and the required code package is stored in the shared library. When each component in the standardized component architecture is connected to the shared library through the import interface to realize the transplantation of the required code package, the component architecture to be tested after the application is put on the shelf is obtained.

[0069] Build a test layer, set sub-scripts based on the application's business execution logic, and use the sub-scripts to form a unified test script across platforms. Use the test scripts to test the component architecture to be tested.

[0070] For example, subscripts can be customized based on statements, decisions, conditions, paths, etc.

[0071] Exemplarily, the specific implementation process of building the test layer includes:

[0072] The test layer sets and stores cross-platform test scripts based on the application's business execution logic, and uses the test scripts to test the component architecture to be tested. The test script contains several sub-scripts, where each sub-script tests a component.

[0073] The identifier of the sub-script is set. The identifier has a unified relationship with the program comment of the required code package. The sub-script is uniformly encoded through the identifier or program comment, and each transplanted component in the component architecture to be tested is matched by identifying the identifier of the sub-script.

[0074] Build a monitoring processing center to collect several component architectures to be tested that are adaptively constructed based on standardized component architectures to generate monitoring sample sets. Under the cross-platform test scripts, extract the test scripts to generate sub-script sets.

[0075] For example, the specific implementation process of establishing a regulatory processing center includes:

[0076] Under the standardized component architecture, when running the test script for the adaptively constructed component architecture to be tested, a standardized component architecture corresponding to several adaptively constructed component architectures to be tested is collected and a monitoring sample set is generated, which is recorded as SCA i ={CCA e |e∈[1, E]}, where i represents the coding number of the standardized component architecture, SCA i represents the monitoring sample set generated by the i-th standardized component architecture, CCA e represents the set of components transplanted in the e-th component architecture to be tested, and CCA e ={DCP r |r∈[1, R]}, E represents the total number of component architectures to be tested, DCP r represents the rth required code package, and R represents the total number of required code packages;

[0077] In the cross-platform test script, when the sub-script identifier matches the program annotation of the required code package corresponding to each transplanted component in the component architecture to be tested, the test script is extracted to generate a sub-script set, which is recorded as S(CCA e ), where S(CCA e ) represents the component collection CCA e The corresponding sub-script set is generated.

[0078] Build a component architecture adaptability assessment model and optimize the monitoring sample set. After optimization is complete, build a script adjustment model to evaluate the test script's test achievement rate. Use the test achievement rate analysis to identify the component architecture to be tested.

[0079] Exemplarily, the specific implementation of constructing a component architecture fitness evaluation model and optimizing a monitoring sample set includes:

[0080] When the e-th component architecture to be tested is adaptively constructed, the component collection CCA is called e , and run the component collection CCA e Each requirement code package in the record running requirement code package DCP r In the component collection CCA e The smoothness of the Where, t k Indicates the requirement code package DCP under the preset kth abnormal condition r The time it takes for the entire process from starting the operation to resuming the operation and completing the operation, T k Indicates that in the component set CCA e Pre-assigned to Demand Code Package DCP r Initialization runtime of

[0081] Preset smoothness threshold, if smoothness SD(DCP r ) is less than or equal to the smoothness threshold, the demand code package DCP r Replace and re-port it to the e-th component architecture to be tested to generate a new component architecture to be tested, and continue to evaluate the smoothness of the re-ported requirement code package under the new component architecture to be tested; if the smoothness SD(DCP r ) is greater than the smoothness threshold, then the component set CCA e Record to monitoring sample set SCA i middle;

[0082] Exemplarily, a specific implementation of constructing a script adjustment model to evaluate the test achievement rate of a test script includes:

[0083] In the monitoring sample set SCA i Calculate the test success rate of the test script Where G represents the total number of sub-scripts contained in the extracted test script. Indicates the monitoring sample set SCA i The corresponding generated sub-script set S(CCA e ), μ is the mean, and σ 2 is the variance, and

[0084] Preset test achievement rate threshold. If the test achievement rate of the test script is less than or equal to the test achievement rate threshold, the tester will be prompted to adjust the test script and recalculate the test achievement rate of the test script until the test achievement rate of the test script is greater than the test achievement rate threshold. The maximum value is selected. The corresponding e-th component architecture to be tested is used as the optimal component architecture after the application is launched.

[0085] It should be noted that, in this document, relational terms such as first and second, etc., are used only to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual relationship or order between these entities or operations. Moreover, the terms "comprises," "comprising," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that includes a list of elements includes not only those elements but also other elements not explicitly listed, or elements inherent to such process, method, article, or apparatus.

[0086] Finally, it should be noted that the above description is merely a preferred embodiment of the present invention and is not intended to limit the present invention. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art will be able to modify the technical solutions described in the aforementioned embodiments or substitute equivalents for some of the technical features. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of the present invention shall be included within the scope of protection of the present invention.

Claims

1. A unified interface application supervision method for multi-terminal integration, characterized in that: The method comprises the following steps: Build the application layer, program the application requirements for cross-platform display, generate the required code package, and compile a standardized component architecture before the application is launched to instruct the business execution logic of the component; Build an abstraction layer and set up the import interface and shared library of the required code package. When implementing the required code package through the import interface, convert the standardized component architecture before the application is launched into the component architecture to be tested after the application is launched. Build a test layer, set sub-scripts based on the application's business execution logic, and use the sub-scripts to form a unified test script across platforms. Use the test scripts to test the component architecture to be tested. Build a monitoring processing center to collect several component architectures to be tested that are adaptively constructed based on standardized component architectures to generate monitoring sample sets. Under the cross-platform test scripts, extract the test scripts to generate sub-script sets. Build a component architecture adaptability evaluation model and optimize the monitoring sample set. After the optimization is completed, build a script adjustment model to evaluate the test achievement rate of the test script, and analyze and lock the component architecture to be tested through the test achievement rate.

2. A method for unified interface application supervision for multi-terminal integration according to claim 1, characterized in that: The specific implementation process of building the application layer includes: The application requirements of the unified interface application when displayed across platforms are programmed into code, and program annotations are performed to obtain a requirement code package, wherein one requirement code package corresponds to one application requirement programmed into code, and the requirement code package is uniformly coded, and the requirement refers to the display requirements of the application on different platform interfaces; Based on the business execution logic of the application, a standardized component architecture is compiled before the application is put on the shelf, wherein the standardized component architecture is used to instruct the business execution logic of the component, and one component corresponds to an application requirement after code programming, and the component is defined by the requirement code package; the standardized component architecture is uniformly coded, and an import interface of the requirement code package of the standardized component architecture is set to receive and run the application requirement after code programming.

3. The method for unified interface application supervision for multi-terminal integration according to claim 1 is characterized in that: The specific implementation process of building the abstraction layer includes: The abstract layer is used to implement the adaptive construction of the standardized component architecture, and to transplant the required code package through the set import interface of the required code package of the standardized component architecture to implement the adaptive construction; A shared library is built into the abstract layer, and the required code package is stored in the shared library. When each component in the standardized component architecture is connected to the shared library through an import interface to realize the transplantation of the required code package, the component architecture to be tested after the application is put on the shelf is obtained.

4. The method for unified interface application supervision for multi-terminal integration according to claim 1 is characterized in that: The specific implementation process of building the test layer includes: The test layer sets and stores cross-platform test scripts based on the application's business execution logic, and tests the component architecture to be tested through the test scripts; the test scripts contain several sub-scripts, where one sub-script tests one component; An identifier of the sub-script is set, wherein the identifier has a unified relationship with the program annotation of the required code package, the sub-script is uniformly encoded through the identifier or program annotation, and each transplanted component in the component architecture to be tested is matched by identifying the identifier of the sub-script.

5. The method for unified interface application supervision for multi-terminal integration according to claim 1 is characterized in that: The specific implementation process of establishing a regulatory processing center includes: Under the standardized component architecture, when running the test script for the adaptively constructed component architecture to be tested, a standardized component architecture corresponding to several adaptively constructed component architectures to be tested is collected and a monitoring sample set is generated, which is recorded as SCA i ={CCA e |e∈[1, E]}, where i represents the coding number of the standardized component architecture, SCA i represents the monitoring sample set generated by the i-th standardized component architecture, CCA e represents the set of components transplanted in the e-th component architecture to be tested, and CCA e ={DCP r |r∈[1, R]}, E represents the total number of component architectures to be tested, DCP r represents the rth required code package, and R represents the total number of required code packages; In the cross-platform test script, when the sub-script identifier matches the program annotation of the required code package corresponding to each transplanted component in the component architecture to be tested, the test script is extracted to generate a sub-script set, which is recorded as S(CCA e ), where S(CCA e ) represents the component collection CCA e The corresponding sub-script set is generated.

6. A method for multi-terminal integrated unified interface application supervision according to claim 5, characterized in that: The specific implementation methods for building a component architecture adaptability evaluation model and optimizing the monitoring sample set include: When the e-th component architecture to be tested is adaptively constructed, the component collection CCA is called e , and run the component collection CCA e Each requirement code package in the record running requirement code package DCP r In the component collection CCA e The smoothness of the Where, t k Indicates the requirement code package DCP under the preset kth abnormal condition r The time it takes for the entire process from starting the operation to resuming the operation and completing the operation, T k Indicates that in the component set CCA e Pre-assigned to Demand Code Package DCP r Initialization runtime of Preset smoothness threshold, if smoothness SD(DCP r ) is less than or equal to the smoothness threshold, the demand code package DCP r Replace and re-port it to the e-th component architecture to be tested to generate a new component architecture to be tested, and continue to evaluate the smoothness of the re-ported requirement code package under the new component architecture to be tested; if the smoothness SD(DCP r ) is greater than the smoothness threshold, then the component set CCA e Record to monitoring sample set SCA i middle.

7. A method for unified interface application supervision for multi-terminal integration according to claim 5, characterized in that: The specific implementation methods for building a script adjustment model and evaluating the test achievement rate of test scripts include: In the monitoring sample set SCA i Calculate the test success rate of the test script Where G represents the total number of sub-scripts contained in the extracted test script. Indicates the monitoring sample set SCA i The corresponding generated sub-script set S(CCA e ), μ is the mean, and σ 2 is the variance, and Preset test achievement rate threshold. If the test achievement rate of the test script is less than or equal to the test achievement rate threshold, the tester will be prompted to adjust the test script and recalculate the test achievement rate of the test script until the test achievement rate of the test script is greater than the test achievement rate threshold. The maximum value is selected. The corresponding e-th component architecture to be tested is used as the optimal component architecture after the application is launched.

8. A unified interface application supervision system for multi-terminal integration, which executes a unified interface application supervision method for multi-terminal integration as described in any one of claims 1 to 7, characterized in that: The system includes: a business execution logic module and a supervision processing center module; The business execution logic module is used to construct the application layer, abstraction layer and test layer; the application layer is used to code programmatically calculate application requirements for cross-platform display, generate requirement code packages, and compile a standardized component architecture before the application is launched to instruct the business execution logic of the components; the abstraction layer is used to set the import interface and shared library of the requirement code package, and when the requirement code package is transplanted through the import interface, the standardized component architecture before the application is launched is converted into the component architecture to be tested after the application is launched; the test layer sets sub-scripts based on the business execution logic of the application, and the sub-scripts constitute a unified test script for the application across platforms, and the test script is used to test the component architecture to be tested; The supervision processing center module is used to build a supervision processing center, collect several component architectures to be tested that are adaptively constructed corresponding to the standardized component architecture to generate a monitoring sample set, and extract the test script under the cross-platform test script to generate a sub-script group set.

9. The unified interface application supervision system for multi-terminal integration according to claim 8, characterized in that: The business execution logic module includes an application layer unit, an abstract layer unit and a test layer unit; The application layer unit is used to code programmatically determine the application requirements of the unified interface application when displayed across platforms, and to perform program annotations to obtain a requirement code package; based on the business execution logic of the application, a standardized component architecture is compiled before the application is launched, and an import interface for the requirement code package of the standardized component architecture is set to receive and execute the application requirements after the code is programmed; The abstract layer unit transplants the required code package through the set import interface of the required code package of the standardized component architecture to achieve the adaptive structure; the abstract layer has a built-in shared library, and the required code package is stored in the shared library. When each component in the standardized component architecture is connected to the shared library through the import interface to achieve the transplantation of the required code package, the component architecture to be tested after the application is put on the shelf is obtained; The test layer unit sets and stores a cross-platform test script for the application based on the business execution logic of the application. The test script contains several sub-scripts, where one sub-script corresponds to testing a component; an identifier of the sub-script is set, and the identifier has a unified relationship with the program annotation of the required code package. The sub-script is uniformly encoded through the identifier or program annotation, and each transplanted component in the component architecture to be tested is matched by identifying the identifier of the sub-script.

10. The unified interface application supervision system for multi-terminal integration according to claim 8, characterized in that: The supervision processing center module includes a fitness analysis unit and a test calibration unit; The fitness analysis unit is used to collect a plurality of adaptively constructed component architectures to be tested corresponding to a standardized component architecture when performing a test script run test on the adaptively constructed component architecture to be tested under the standardized component architecture, generate a monitoring sample set, and construct a component architecture fitness evaluation model to optimize the monitoring sample set; The test calibration unit is used to extract the test script in a cross-platform test script to generate a sub-script set after the identifier of the sub-script is matched with the program annotation of the requirement code package corresponding to each transplanted component in the component architecture to be tested, and to build a script adjustment model to evaluate the test achievement rate of the test script so as to select the optimal component architecture after the application is launched.

Images