Unified interface application supervision method and system oriented to multi-terminal integration

Abstract

The invention discloses a unified interface application supervision method and system oriented to multi-terminal integration, and belongs to the technical field of application supervision. By constructing an application layer, an abstraction layer and a test layer, generation of a demand code package, self-adaptive construction of a component architecture and setting of a cross-platform test script are achieved, a to-be-tested component architecture is collected through a supervision processing center, a monitoring sample set is generated, a component architecture adaptation degree evaluation model and a script adjustment model are utilized, and a test result is obtained. Optimizing the component and evaluating the achievement rate of the test script; according to the method, components can be adaptively optimized along with cross-platform demand changes, scripts are intelligently adjusted, and integrated response of the application server side, the code development side and the script test side is ensured; the system implementation comprises a service execution logic module and a supervision processing center module, efficient supervision of diversified and unified interface applications is achieved, and the development efficiency and the user experience are improved.

Description

Technical Field

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

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

[0003] Fragmentation between business logic and interface adaptation: In the existing technology, although some business logics can be reused across platforms, the interface display requirements of different platforms often need to be adjusted separately. Developers need to write differentiated codes for each platform, resulting in a high coupling degree between business logic and interface implementation, and it is difficult to achieve true "write once, run on multiple terminals".

[0004] Low test coverage and adaptation efficiency: The testing of cross-platform applications usually relies on manually writing multiple sets of platform-specific test scripts. The test cases are scattered and lack unified management. Existing test tools are difficult to dynamically evaluate the adaptation degree of components on different platforms, and the test scripts cannot be automatically optimized with the change of requirements, resulting in a low test achievement rate and high maintenance costs.

[0005] Rigidity of component architecture and lag in optimization: In the traditional development process, it is difficult to dynamically adjust the component architecture after the application is launched. When cross-platform requirements change, it is necessary to manually reconstruct the components and re-verify them, lacking an adaptive optimization mechanism. In addition, the updates of components and test scripts are often out of sync, resulting in low collaborative efficiency in the development, testing, and deployment links.

[0006] Lack of supervision and feedback mechanism: The existing solutions lack the ability to integrate the supervision of the development, testing, and operation links. The data of each link is isolated and cannot form a closed-loop feedback. It is difficult to monitor the component performance, script coverage rate, and platform adaptation status in real time, thus affecting 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 art.

[0008] 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, which includes: a business execution logic module and a supervision processing center module;

[0010] The business execution logic module is used to construct an application layer, an abstraction layer, and a test layer. The application layer is used for the application requirements during the cross-platform display of code programming, generating a requirement code package, and formulating the business execution logic of instruction components by preparing a standardized component architecture before the application is put on the shelf. 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 put on the shelf is transformed into a component architecture to be tested after the application is put on the shelf. The test layer sets sub-scripts based on the business execution logic of the application, and the sub-scripts form a unified test script for the application across platforms. The component architecture to be tested is tested through the test script.

[0011] The supervision and processing center module is used to build a supervision and processing center, collect a number of component architectures to be tested 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 set.

[0012] Further, the business execution logic module includes an application layer unit, an abstraction layer unit, and a test layer unit.

[0013] The application layer unit is used for the application requirements during the cross-platform display of the unified interface application of code programming, and performs program annotation to obtain a requirement code package. Based on the business execution logic of the application, a standardized component architecture is prepared before the application is put on the shelf, and the import interface of the requirement code package of the standardized component architecture is set to receive and run the application requirements after the code programming.

[0014] The abstraction layer unit performs the transplantation of the requirement code package through the set import interface of the requirement code package of the standardized component architecture to achieve the adaptive construction. A shared library is built in the abstraction layer, and the requirement 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 complete the transplantation of the requirement code package, a 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 a number of sub-scripts, where one sub-script corresponds to testing one type of component. An identifier for the sub-script is set, and the identifier has a unified relationship with the program annotation of the requirement code package. The sub-scripts are 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] Further, the supervision and processing center module includes a fitness analysis unit and a test calibration unit.

[0017] The adaptation degree analysis unit is used to collect several component architectures to be tested with adaptive construction corresponding to a standardized component architecture when running a test script for the component architecture to be tested with adaptive construction under the standardized component architecture, generate a monitoring sample set, and construct a component architecture adaptation degree evaluation model to optimize the monitoring sample set;

[0018] The test calibration unit is used to extract the test script to generate a sub-script set when the identifier of the sub-script matches the program annotation of the required code package corresponding to each transplanted component in the component architecture to be tested under the cross-platform test script, and construct 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 put on the shelf.

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

[0020] Build an application layer, program the application requirements when the code is displayed across platforms, generate a required code package, and compile a standardized component architecture before the application is put on the shelf to instruct the business execution logic of the component;

[0021] Build an abstraction layer, set the import interface and shared library of the required code package, and convert the standardized component architecture before the application is put on the shelf into the component architecture to be tested after the application is put on the shelf when the required code package is transplanted through the import interface;

[0022] Build a test layer, set sub-scripts based on the business execution logic of the application, and form a unified test script for the application across platforms by the sub-scripts, and test the component architecture to be tested through the test script;

[0023] Set up a supervision and processing center, collect several component architectures to be tested with adaptive construction 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 set;

[0024] Construct a component architecture adaptation degree evaluation model to optimize the monitoring sample set. After the optimization is completed, construct 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] Further, the specific implementation process of building the application layer includes:

[0026] Program the application requirements when the unified interface application with programmed code is displayed across platforms, and perform program annotation to obtain a required code package. Among them, one required code package corresponds to one application requirement with programmed code, and the required code package is uniformly encoded. 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. Among them, the standardized component architecture is used to instruct the business execution logic of the components, and one component corresponds to one application requirement after code programming, and the components are defined through requirement code packages; the standardized component architecture is uniformly encoded, and an import interface for the requirement code package of the standardized component architecture is set to receive and run the application requirement after code programming.

[0028] Further, the specific implementation process of constructing the abstraction layer includes:

[0029] The abstraction layer is used to realize the adaptive construction of the standardized component architecture, and the transplantation of the requirement code package is carried out through the set import interface of the requirement code package of the standardized component architecture to realize the adaptive construction;

[0030] A shared library is built in the abstraction layer, and the requirement 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 requirement code package, the component architecture to be tested after the application is put on the shelf is obtained.

[0031] Further, the specific implementation process of constructing the test layer includes:

[0032] Based on the business execution logic of the application, the test layer sets and stores test scripts for cross-platform applications, and tests the component architecture to be tested through the test scripts; several sub-scripts are included in the test scripts, and one sub-script corresponds to testing one component;

[0033] Set the identifier of the sub-script, the identifier has a unified relationship with the program comment of the requirement 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.

[0034] Further, the specific implementation process of building the supervision and processing center includes:

[0035] Under the standardized component architecture, when running the test script on the component architecture to be tested with adaptive construction, several component architectures to be tested with adaptive construction corresponding to one standardized component architecture are collected, and a monitoring sample set is generated, denoted as SCA i ={CCA e |e∈[1, E]}, where i represents the encoding number of the standardized component architecture, SCA i represents the monitoring sample set generated corresponding to 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]}, where E represents the total number of component architectures to be tested, DCP r represents the r-th requirement code package, and R represents the total number of requirement code packages;

[0036] Under the cross-platform test script, after the identifier of the sub-script matches the program comments of the requirement code packages corresponding to each transplanted component in the component architecture to be tested, the test script is extracted to generate a set of sub-scripts, denoted as S(CCA e ), where S(CCA e ) represents the set of sub-scripts generated corresponding to the component set CCA e .

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

[0038] When the e-th component architecture to be tested is adaptively constructed, the component set CCA e is retrieved and the requirement code packages in the component set CCA e are run, and the smoothness of running the requirement code package DCP r under the component set CCA e is recorded In the formula, t k represents the duration consumed by the complete process of the requirement code package DCP r from starting to run, interrupting, resuming running until running to completion under the k-th preset abnormal condition, and T k represents the initial running duration pre-allocated to the requirement code package DCP e under the component set CCA r ;

[0039] A smoothness threshold is preset. If the smoothness SD(DCP r ) is less than or equal to the smoothness threshold, the requirement code package DCP r is replaced and re-transplanted into the e-th component architecture to be tested to generate a new component architecture to be tested, and the smoothness of the re-transplanted requirement code package is continuously evaluated under the new component architecture to be tested; if the smoothness SD(DCP r ) is greater than the smoothness threshold, the component set CCA e is recorded in the monitoring sample set SCA i .

[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 achievement rate of the test script In the formula, G represents the total number of sub-scripts included in the test script after extraction, represents the monitored sample set SCA i The set of sub-script groups S(CCA e ) The total number of sub-scripts included in the intersection set, μ is the mean, and σ 2 is the variance, and

[0042] The 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, prompt the tester 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, then select the maximum value The corresponding e-th component architecture to be tested is used as the optimal component architecture after the application is put on the shelf.

[0043] Compared with the prior art, the beneficial effects achieved by the present invention are: in a unified interface application supervision method and system for multi-terminal integration provided by the present invention, by constructing an application layer, an abstraction layer, and a test layer, the generation of a requirement code package, the adaptive construction of a component architecture, and the setting of cross-platform test scripts are realized. The supervision processing center collects the component architectures to be tested, generates a monitored sample set, and uses the component architecture adaptation degree evaluation model and the script adjustment model to optimize the components and evaluate the achievement rate of the test script; the present invention can adaptively optimize the components according to the cross-platform requirement changes, intelligently adjust the scripts, and ensure the integrated response of the application server, the code development side, and the script test side; the system implementation includes a business execution logic module and a supervision processing center module, realizing the efficient supervision of diversified unified interface applications and improving the development efficiency and user experience. Description of the Drawings

[0044] The drawings are used to provide a further understanding of the present invention, and constitute a part of the specification. They are used together with the embodiments of the present invention to explain the present invention, and do not constitute a limitation to 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 Embodiments

[0046] The following will clearly and completely describe the technical solutions in the embodiments of the present invention with reference to the drawings in the embodiments of the present invention. Obviously, the described embodiments are only a part of the embodiments of the present invention, rather than all the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without creative efforts belong to the scope of protection of the present invention.

[0047] In the first embodiment: A unified interface application supervision system for multi-terminal integration is provided. The system includes:

[0048] A business execution logic module for constructing an application layer, an abstraction layer, and a test layer; The application layer is used for the application requirements during the cross-platform display of code-programmed applications, generating a requirement code package, and formulating the business execution logic of instruction components by preparing a standardized component architecture before the application is put on the shelf; 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 put on the shelf is transformed into the component architecture to be tested after the application is put on the shelf; 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. The component architecture to be tested is tested through the test script;

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

[0050] The application layer unit is used for the application requirements during the cross-platform display of code-programmed unified interface applications, and performs program annotation to obtain a requirement code package; Based on the business execution logic of the application, a standardized component architecture is prepared before the application is put on the shelf, and the import interface of the requirement code package of the standardized component architecture is set to receive and run the application requirements after code programming;

[0051] The abstraction layer unit transplants the requirement code package through the set import interface of the requirement code package of the standardized component architecture to achieve adaptive construction; A shared library is built in the abstraction layer, and the requirement 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 complete the transplantation of the requirement code package, the component architecture to be tested after the application is put on the shelf is obtained;

[0052] The test layer unit sets and stores a test script for the application across platforms based on the business execution logic of the application. The test script contains several sub-scripts. Among them, one sub-script corresponds to testing one component; The identifier of the sub-script is set, and the identifier has a unified relationship with the program annotation of the requirement code package. The sub-scripts are 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;

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

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

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

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

[0057] The test calibration unit is used to extract the test script to generate a sub-script set under the cross-platform test script after the identifier of the sub-script matches the program annotation of the required code package corresponding to each transplanted component in the component architecture to be tested, and build a script adjustment model to evaluate the test achievement rate of the test script to select the optimal component architecture after the application is put on the shelf.

[0058] It should be noted that after the application is put on the shelf, the system can regularly perform continuous monitoring through scripts to monitor the application running status and conduct service inspections. Once abnormal situations such as the application being unavailable, the network being unstable, or the interface crashing are found, the warning mechanism will be immediately triggered and synchronized feedback will be given on multiple platforms to ensure that the problems are handled in a timely manner.

[0059] Please refer to Figure 1 , in the second embodiment: A unified interface application supervision method for multi-terminal integration is provided and applied to the above-mentioned first embodiment. The method includes the following steps:

[0060] Build an application layer, generate a required code package for the application requirements when the code is programmed and displayed across platforms, and compile the standardized component architecture before the application is put on the shelf to instruct the business execution logic of the components.

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

[0062] Program the unified interface of the code to meet the application requirements when displayed across platforms, and add program comments to obtain a requirement code package. Here, one requirement code package corresponds to one application requirement programmed by the code, and the requirement code package is uniformly encoded. The requirement refers to the display requirements of the application on different platform interfaces;

[0063] For example, the 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, prepare a standardized component architecture before the application is put on the shelf. Here, the standardized component architecture is used to instruct the business execution logic of the components, and one component corresponds to one application requirement programmed by the code, and the components are defined through the requirement code package; the standardized component architecture is uniformly encoded, and an import interface for the requirement code package of the standardized component architecture is set to receive and run the application requirements programmed by the code.

[0065] Construct an abstraction layer, and set the import interface and shared library for the requirement code package. When the requirement code package is transplanted through the import interface, the standardized component architecture before the application is put on the shelf is transformed into the component architecture to be tested after the application is put on the shelf;

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

[0067] The abstraction layer is used to implement the adaptive construction of the standardized component architecture, and the requirement code package is transplanted through the set import interface of the requirement code package of the standardized component architecture to achieve adaptive construction;

[0068] A shared library is built into the abstraction layer, and the requirement 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 complete the transplantation of the requirement code package, the component architecture to be tested after the application is put on the shelf is obtained.

[0069] Construct a test layer, set sub-scripts based on the business execution logic of the application, and form a unified test script for the application across platforms by the sub-scripts, and test the component architecture to be tested through the test script;

[0070] For example, the sub-scripts can be customized based on statements, judgments, conditions, paths, etc.;

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

[0072] The test layer sets and stores cross-platform test scripts for an application 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 corresponds to testing one type of component.

[0073] Set the identifier of the sub-script. The identifier has a unified relationship with the program comment of the requirement code package. The sub-scripts are uniformly encoded through the identifier or the 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 supervision and processing center, collect several component architectures to be tested adaptively constructed corresponding to the standardized component architecture to generate a monitoring sample set, and under the cross-platform test script, extract the test script to generate a sub-script set.

[0075] Exemplarily, the specific implementation process of building the supervision and processing center includes:

[0076] When running the test script for the component architecture to be tested adaptively constructed under the standardized component architecture, collect several component architectures to be tested adaptively constructed corresponding to one standardized component architecture and generate a monitoring sample set, denoted as SCA i ={CCA e |e∈[1, E]}, where i represents the encoding number of the standardized component architecture, SCA i represents the monitoring sample set generated corresponding to the i-th standardized component architecture, CCA e represents the set of transplanted components 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 r-th requirement code package, and R represents the total number of requirement code packages;

[0077] Under the cross-platform test script, after the identifier of the sub-script matches the program comment of the requirement code package corresponding to each transplanted component in the component architecture to be tested, extract the test script to generate a sub-script set, denoted as S(CCA e ), where S(CCA e ) represents the sub-script set generated corresponding to the component set CCA e .

[0078] Build a component architecture adaptability evaluation model to 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.

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

[0080] When the e-th component architecture to be tested is adaptively constructed, the component set CCA is retrieved e , and the component set CCA is run e The demand code packages in it are run, and the smoothness of running the demand code package DCP r under the component set CCA e is recorded In the formula, t k represents the duration consumed by the complete process of the demand code package DCP r from starting to run, interrupting and resuming running until running to completion under the k-th preset abnormal condition, and T k represents the initialized running duration pre-allocated to the demand code package DCP e under the component set CCA r ;

[0081] A preset smoothness threshold. If the smoothness SD(DCP r ) is less than or equal to the smoothness threshold, the demand code package DCP r is replaced and re-transplanted into the e-th component architecture to be tested to generate a new component architecture to be tested, and the smoothness of the re-transplanted demand code package is continuously evaluated under the new component architecture to be tested; if the smoothness SD(DCP r ) is greater than the smoothness threshold, the component set CCA e is recorded into the monitoring sample set SCA i ;

[0082] Exemplarily, the specific implementation manners of constructing a script adjustment model and evaluating the test achievement rate of a test script include:

[0083] Under the monitoring sample set SCA i , calculate the test achievement rate of the test script In the formula, G represents the total number of sub-scripts included in the extracted test script, represents the total number of sub-scripts included in the intersection set of the sub-script group sets S(CCA i ) corresponding to the monitoring sample set SCA e , μ is the mean value, and σ 2 is the variance, and

[0084] Preset a test achievement rate threshold. If the test achievement rate of the test script is less than or equal to the test achievement rate threshold, prompt the tester 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, and then select the maximum value. The corresponding e-th component architecture to be tested is used as the optimal component architecture after the application is put on the shelf.

[0085] It should be noted that in this article, relational terms such as first and second are only used 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 term "comprising", "including" or any other variant thereof is intended to cover non-exclusive inclusion, so that a process, method, article or device comprising a series of elements not only includes those elements, but also includes other elements not expressly listed, or further includes elements inherent to such process, method, article or device.

[0086] Finally, it should be noted that the above are only the preferred embodiments of the present invention and are not used to limit the present invention. Although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art can still modify the technical solutions described in the foregoing embodiments, or perform equivalent replacements for some of the technical features. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principle of the present invention shall be included in the protection scope of the present invention.

Claims

1. A unified interface application supervision method for multi-terminal integration, characterized in that, The method includes the following steps: Construct an application layer, program the application requirements during cross-platform display, generate a requirement code package, and compile a standardized component architecture before the application is put on the shelf to instruct the business execution logic of the components; Construct an abstraction layer, and set the import interface and shared library of the requirement code package. When transplanting the requirement code package through the import interface, convert the standardized component architecture before the application is put on the shelf into the component architecture to be tested after the application is put on the shelf; Construct a test layer, set sub-scripts based on the business execution logic of the application, and form a unified test script for the application across platforms by the sub-scripts. Test the component architecture to be tested through the test script; Build a supervision and processing center, collect a number of component architectures to be tested 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 set; Construct a component architecture adaptability evaluation model to optimize the monitoring sample set. After the optimization is completed, construct a script adjustment model, 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. The unified interface application supervision method for multi-terminal integration according to claim 1, characterized in that, The specific implementation process of constructing the application layer includes: Program the application requirements of the unified interface application during cross-platform display and add program comments to obtain a requirement code package. Among them, one requirement code package corresponds to one application requirement programmed by code, and the requirement code package is uniformly encoded. The requirement refers to the display requirements of the application on different platform interfaces; Based on the business execution logic of the application, compile a standardized component architecture before the application is put on the shelf. Among them, the standardized component architecture is used to instruct the business execution logic of the components, and one component corresponds to one application requirement after code programming, and the component is defined by the requirement code package; uniformly encode the standardized component architecture, and set the import interface of the requirement code package of the standardized component architecture to receive and run the application requirement after code programming.

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

4. A unified interface application supervision method for multi-terminal integration according to claim 1, characterized in that The specific implementation process of constructing the test layer includes: The test layer sets and stores a test script for the application across platforms based on the business execution logic of the application, and tests the component architecture to be tested through the test script; the test script contains several sub-scripts, where one sub-script corresponds to testing one component; Set the identifier of the sub-script. The identifier has a unified relationship with the program comment of the requirement code package. Uniformly encode the sub-script through the identifier or program comment, and match each transplanted component in the component architecture to be tested by identifying the identifier of the sub-script.

5. The unified interface application supervision method for multi-terminal integration according to claim 1, characterized in that, The specific implementation process of building a supervision and processing center includes: When running a test script on an adaptively constructed component architecture to be tested under a standardized component architecture, a number of adaptively constructed component architectures to be tested corresponding to a standardized component architecture are collected, and a monitoring sample set is generated, denoted as SCA i ={CCA e |e ∈ [1, E]}, where i represents the encoding number of the standardized component architecture, SCA i represents the monitoring sample set generated corresponding to 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 r-th requirement code package, and R represents the total number of requirement code packages; Under a cross-platform test script, after the identifiers of the sub-scripts match the program comments of the requirement code packages corresponding to the respective ported components in the component architecture to be tested, the test script is extracted to generate a set of sub-scripts, denoted as S(CCA e ), where S(CCA e ) represents the set of sub-scripts generated corresponding to the component set CCA e .

6. A unified interface application supervision method for multi-terminal integration according to claim 5, characterized in that, The specific implementation method of constructing a component architecture adaptability evaluation model and optimizing the monitoring sample set includes: When the e-th component architecture to be tested is adaptively constructed, the component collection CCA is retrieved e , and the component collection CCA is run e . Each requirement code package in it is run, and the smoothness of running the requirement code package DCP r under the component collection CCA e is recorded where t k represents the duration consumed by the complete process of the requirement code package DCP r from starting to run, interrupting and resuming running until running to completion under the k-th preset abnormal condition, and T k represents the initial running duration pre-allocated to the requirement code package DCP e under the component collection CCA r ; Preset a smoothness threshold. If the smoothness SD(DCP r ) is less than or equal to the smoothness threshold, replace the requirement code package DCP r and re - transplant it into 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 - transplanted requirement code package under the new component architecture to be tested; if the smoothness SD(DCP r ) is greater than the smoothness threshold, record the component set CCA e into the monitoring sample set SCA i .

7. A unified interface application supervision method for multi-terminal integration according to claim 5, characterized in that, The specific implementation method of constructing a script adjustment model and evaluating the test achievement rate of test scripts includes: Under the monitoring sample set SCA i Calculate the test achievement rate of the test script In the formula, G represents the total number of sub-scripts included in the test script after extraction, Indicates the monitoring sample set SCA i The total number of sub-scripts included in the intersection set of the corresponding generated sub-script group set S(CCA e ), μ is the mean value, and σ 2 Is the variance, and Set a 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, prompt the tester 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, and then select the maximum value. The corresponding e-th component architecture to be tested is used as the optimal component architecture after the application is put on the shelf.

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-7, characterized in that, The system includes: a business execution logic module and a supervision and processing center module; The business execution logic module is used to construct an application layer, an abstraction layer, and a test layer; the application layer is used for the application requirements when the code is programmed for cross-platform display, generating a requirement code package, and formulating a standardized component architecture before the application is put on the shelf 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 put on the shelf is transformed into the component architecture to be tested after the application is put on the shelf; the test layer sets sub-scripts based on the business execution logic of the application, and the sub-scripts form a unified test script for the application across platforms, and the component architecture to be tested is tested through the test script. The supervision and processing center module is used to build a supervision and processing center, collect a number of component architectures to be tested 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 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 abstraction layer unit, and a test layer unit; The application layer unit is used for the application requirements when the code is programmed for unified interface applications across platforms, and performs program annotation to obtain a requirement code package; based on the business execution logic of the application, a standardized component architecture is formulated before the application is put on the shelf, and the import interface of the requirement code package of the standardized component architecture is set to receive and run the application requirements after the code is programmed. The abstraction layer unit performs the transplantation of the requirement code package through the set import interface of the requirement code package of the standardized component architecture to achieve the adaptive construction; a shared library is built in the abstraction layer, and the requirement 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 requirement 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 the cross-platform test script of the application based on the business execution logic of the application. The test script contains a number of sub-scripts, where one sub-script corresponds to testing one component; the identifier of the sub-script is set, and the identifier has a unified relationship with the program annotation of the requirement code package. The sub-scripts are 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. A unified interface application supervision system for multi-terminal integration according to claim 8, characterized in that: The supervision and processing center module includes an adaptability analysis unit and a test calibration unit; The adaptability analysis unit is used to collect several component architectures to be tested with adaptive construction corresponding to a standardized component architecture when running test scripts for the component architecture to be tested with adaptive construction under a standardized component architecture, generate a monitoring sample set, and construct a component architecture adaptability evaluation model to optimize the monitoring sample set; The test calibration unit is used to extract the test script to generate a sub-script set and construct a script adjustment model to evaluate the test achievement rate of the test script when the identifier of the sub-script matches the program annotation of the required code package corresponding to each transplanted component in the component architecture to be tested under a cross-platform test script, so as to select the optimal component architecture after the application is put on the shelf.

Images