CN111984534B - Arm64 architecture-based front-end UI automatic testing method and device - Google Patents
Arm64 architecture-based front-end UI automatic testing method and device Download PDFInfo
- Publication number
- CN111984534B CN111984534B CN202010791620.7A CN202010791620A CN111984534B CN 111984534 B CN111984534 B CN 111984534B CN 202010791620 A CN202010791620 A CN 202010791620A CN 111984534 B CN111984534 B CN 111984534B
- Authority
- CN
- China
- Prior art keywords
- browser
- container
- setting
- automatic test
- testng
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000012360 testing method Methods 0.000 title claims abstract description 181
- 238000000034 method Methods 0.000 claims abstract description 50
- 230000008569 process Effects 0.000 claims abstract description 40
- 239000003795 chemical substances by application Substances 0.000 claims description 32
- 241000380131 Ammophila arenaria Species 0.000 claims description 28
- BUGBHKTXTAQXES-UHFFFAOYSA-N Selenium Chemical compound [Se] BUGBHKTXTAQXES-UHFFFAOYSA-N 0.000 claims description 9
- 229910052711 selenium Inorganic materials 0.000 claims description 9
- 239000011669 selenium Substances 0.000 claims description 9
- 239000000523 sample Substances 0.000 claims description 6
- 230000004083 survival effect Effects 0.000 claims description 6
- 238000010998 test method Methods 0.000 claims description 4
- 238000007726 management method Methods 0.000 description 17
- 238000011161 development Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 238000006467 substitution reaction Methods 0.000 description 3
- 230000009286 beneficial effect Effects 0.000 description 2
- 239000008186 active pharmaceutical agent Substances 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
- G06F2009/45575—Starting, stopping, suspending or resuming virtual machine instances
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
- G06F2009/45579—I/O management, e.g. providing access to device drivers or storage
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
- G06F2009/45591—Monitoring or debugging support
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
- G06F2009/45595—Network integration; Enabling network access in virtual machine instances
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Debugging And Monitoring (AREA)
Abstract
The invention provides an arm64 architecture-based front end UI automatic testing method and device, wherein the method comprises the following steps: s1, a test management module is arranged to receive automatic test parameter configuration of a user on a configuration page and send an automatic test deployment task to a cluster agent client; s2, setting a cluster agent client to receive and analyze an automatic test deployment task, creating a testNG application deployment process in a cluster, setting the testNG application deployment process to establish a browser core intranet interface, and creating a browser container and a program container; and S3, setting the TestNG application to start, starting a browser core port through the browser container, performing automatic test and outputting an automatic test result at the browser core port through the process sequence container, and closing the browser core port through the browser container after the automatic test is finished.
Description
Technical Field
The invention belongs to the technical field of software automated testing, and particularly relates to an arm64 architecture-based front-end UI automated testing method and device.
Background
The UI is an abbreviation of User Interface, refers to a User Interface, and refers to a User Interface for realizing human-computer interaction and operation logic through software.
arm64, is a 64-bit arm processor.
Selenium, a tool for Web application testing.
In the cloud computing era, with the continuous expansion of the market scale of the internet, a large number of heterogeneous resources are uniformly managed through a cloud platform, and in a traditional development mode, developers and testers often respectively perform their duties: and after knowing the product requirements, developers start to compile codes, and testers start to compile test cases after taking product requirement specifications, and then start to perform manual test work according to the test cases after the development is completed. However, in the conventional development mode, when the requirement changes, the test case written by the tester is often completed, the test case needs to be inverted and reconstructed, the whole test flow is repeatedly and uselessly operated, the test time is long, and the test result is unreliable. The automatic test overcomes the problems of long project period, poor work content distribution of life cycle and large influence of later change in the traditional test mode, but the existing automatic test depends on an external browser core and cannot adapt to different environments, thereby influencing the test reliability and timeliness.
Therefore, it is very necessary to provide a method and an apparatus for automated testing of front-end UI based on arm64 architecture to overcome the above-mentioned drawbacks in the prior art.
Disclosure of Invention
Aiming at the defects that the existing automatic test in the prior art depends on an external browser core and cannot adapt to different environments, so that the test reliability and timeliness cannot be guaranteed, the invention provides the front-end UI automatic test method and device based on the arm64 architecture, so as to solve the technical problems.
In a first aspect, the present invention provides an arm64 architecture-based front-end UI automated testing method, including the following steps:
s1, a test management module is arranged to receive automatic test parameter configuration of a user on a configuration page and send an automatic test deployment task to a cluster agent client;
s2, setting a cluster agent client to receive and analyze an automatic test deployment task, creating a testNG application deployment process in a cluster, setting the testNG application deployment process to establish a browser core intranet interface, and creating a browser container and a program container;
and S3, setting the TestNG application to start, starting a browser core port through the browser container, performing automatic test and outputting an automatic test result at the browser core port through the process sequence container, and closing the browser core port through the browser container after the automatic test is finished.
Further, the step S1 specifically includes the following steps:
s11, setting a test management module to obtain automatic test parameter configuration input by a user on a configuration page;
s12, setting a test management module to generate an automatic deployment task according to automatic test parameter configuration;
and S13, the test management module is set to request the Kubernet cluster agent client to automatically deploy task scheduling through the WebSocket client.
Further, the step S2 specifically includes the following steps:
s21, judging whether a Helm chart tool is installed or not;
if not, installing a Helm chart tool and entering the step S22;
if yes, go directly to step S22;
s22, a Kubernetes cluster agent client is set to analyze a chart configuration file in an automatic test deployment task through a Helm chart tool;
s23, setting a Kubernets cluster agent client to create a TestNG application deployment process based on Selenium in the Kubernets cluster according to a chart configuration file analysis result;
and S24, setting a TestNG application deployment process, establishing a WebDriver browser core intranet interface, and creating a browser container for opening a WebDriver browser core port and a program container for running an automatic test program.
Further, the step S3 specifically includes the following steps:
s31, setting a TestNG application to start, and connecting a browser container with a browser core intranet interface to start a browser core port;
s32, setting a TestNG application to perform automatic testing through a program container and based on a browser core port, generating an automatic testing report and outputting the automatic testing report;
and S33, after the automated testing is finished, the TestNG application is set, a browser core port closing notice is sent to the browser container through the program container, and the browser container and the program container are closed after the browser core port is closed.
Further, the step S31 specifically includes the following steps:
s311, setting a TestNG application to start, connecting a browser container with a browser core intranet interface to start a browser core port, and judging whether the browser core port is successfully started;
if yes, go to step S32;
if not, go to step S312;
s312, setting the TestNG application to close the browser container and the program container through the survival probe.
In a second aspect, the present invention provides an arm64 architecture-based front end UI automation testing apparatus, including:
the automatic test parameter acquisition module is used for setting the test management module to receive the automatic test parameter configuration of the user on the configuration page and sending an automatic test deployment task to the cluster agent client;
the automatic test deployment module is used for setting a cluster agent client to receive and analyze an automatic test deployment task, establishing a TestNG application deployment process in a cluster, setting the TestNG application deployment process to establish a browser core intranet interface, and establishing a browser container and a program container;
and the automatic test module is used for setting the start of the TestNG application, opening the core port of the browser through the browser container, performing automatic test and outputting an automatic test result at the core port of the browser through the process sequence container, and closing the core port of the browser through the browser container after the automatic test is finished.
Further, the automatic test parameter acquisition module comprises:
the parameter acquisition unit is used for setting the test management module to acquire the automatic test parameter configuration input by the user on the configuration page;
the deployment task generating unit is used for setting the test management module to generate an automatic deployment task according to the automatic test parameter configuration;
and the task deployment request unit is used for setting the test management module to request the Kubernet cluster agent client to automatically deploy task scheduling through the WebSocket client.
Further, the automated test deployment module comprises:
a Helm chart tool judging unit for judging whether a Helm chart tool is installed or not;
the Helm chart tool mounting unit is used for mounting the Helm chart tool when the Helm chart tool is not mounted;
the configuration file analysis unit is used for setting the Kubernets cluster agent client to analyze the chart configuration file in the automatic test deployment task through a Helm chart tool;
the application deployment process creating unit is used for setting the Kubernets cluster agent client to create a TestNG application deployment process based on the Selenium in the Kubernets cluster according to the chart configuration file analysis result;
and the application deployment unit is used for setting a TestNG application deployment process, establishing a WebDriver browser core intranet interface, and creating a browser container for opening a WebDriver browser core port and a program container for running an automatic test program.
Further, the automated testing module comprises:
the browser core port opening unit is used for setting the TestNG application to be started and connecting a browser container with a browser core intranet interface to open the browser core port;
the automatic testing unit is used for setting the TestNG application to pass through the program container and automatically testing based on the core port of the browser, and generating and outputting an automatic testing report;
and the browser core port closing unit is used for setting that the TestNG application sends a browser core port closing notice to the browser container through the program container after the automatic test is finished, and closing the browser container and the program container after the browser core port is closed.
Further, the browser core port opening unit includes:
the core port opening judging subunit is used for setting the start of the TestNG application, connecting a browser container with a browser core intranet interface to open the browser core port, and judging whether the browser core port is successfully opened;
and the container closing subunit is used for setting the TestNG application to close the browser container and the program container through the survival probe.
The beneficial effect of the invention is that,
according to the arm64 architecture-based front-end UI automatic testing method and device, the testNG + selenium front-end testing UI framework is adopted, and automatic testing parameter configuration is obtained through page modification, so that embedded running automatic testing in different environments is achieved, dependence of selenium on an external browser core is avoided, adaptability is high, and testing reliability and timeliness are improved.
In addition, the invention has reliable design principle, simple structure and very wide application prospect.
Therefore, compared with the prior art, the invention has prominent substantive features and remarkable progress, and the beneficial effects of the implementation are also obvious.
Drawings
In order to more clearly illustrate the embodiments or technical solutions in the prior art of the present invention, the drawings used in the description of the embodiments or prior art will be briefly described below, and it is obvious for those skilled in the art that other drawings can be obtained based on these drawings without creative efforts.
FIG. 1 is a first schematic flow chart of the method of the present invention;
FIG. 2 is a second schematic flow chart of the method of the present invention;
FIG. 3 is a schematic diagram of the system of the present invention;
in the figure, 1-an automatic test parameter acquisition module; 1.1-a parameter acquisition unit; 1.2-a deployment task generating unit; 1.3-task deployment request unit; 2-automatic test deployment module; 2.1-Helm chart tool judging unit; 2.2-Helm chart tool mounting unit; 2.3-configuration file parsing unit; 2.4-an application deployment process creation unit; 2.5-application deployment unit; 3-an automated testing module; 3.1-browser core port opening unit; 3.2-an automated test unit; 3.3-browser core Port closing Unit.
Detailed Description
In order to make those skilled in the art better understand the technical solution of the present invention, the technical solution in the embodiment of the present invention will be clearly and completely described below with reference to the drawings in the embodiment of the present invention, and it is obvious that the described embodiment is only a part of the embodiment of the present invention, and not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
TestNG is an open source automated testing framework, and its inspiration comes from JUnit and NUnit, and TestNG has still covered the JUnit4 function of whole core, but introduced some new functions, makes its function stronger, and it is more convenient to use. The advantages are that: supporting a dependence test method, a parallel test, a load test and a local fault; a flexible plug-in API; multi-thread testing is supported.
WebSocket is a protocol for full duplex communication over a single TCP connection.
kubernets, K8s for short, is an abbreviation for 8 instead of 8 characters "ubernet". The Kubernets aims to make the application of container deployment simple and efficient, and provides a mechanism for application deployment, planning, updating and maintenance.
Helm uses a wrapper format called chart. chart is a collection of files that describes a related set of kubernets resources. A single chart might be used to deploy simple things such as memcached pod, or some complex things such as a complete Web application stack with HTTP services, databases, caches, etc. chart packs files into versioned, compressed packages by creating them as a specific directory tree, and then deploys them.
Example 1:
as shown in fig. 1, the present invention provides an arm64 architecture-based front-end UI automated testing method, which includes the following steps:
s1, a test management module is arranged to receive automatic test parameter configuration of a user on a configuration page and send an automatic test deployment task to a cluster agent client;
s2, setting a cluster agent client to receive and analyze an automatic test deployment task, creating a testNG application deployment process in a cluster, setting the testNG application deployment process to establish a browser core intranet interface, and creating a browser container and a program container;
and S3, setting the TestNG application to start, starting a browser core port through the browser container, performing automatic test and outputting an automatic test result at the browser core port through the process sequence container, and closing the browser core port through the browser container after the automatic test is finished.
Example 2:
as shown in fig. 2, the present invention provides an arm64 architecture-based front-end UI automated testing method, which includes the following steps:
s1, a test management module is arranged to receive automatic test parameter configuration of a user on a configuration page and send an automatic test deployment task to a cluster agent client; the method comprises the following specific steps:
s11, setting a test management module to obtain automatic test parameter configuration input by a user on a configuration page;
s12, setting a test management module to generate an automatic deployment task according to automatic test parameter configuration;
s13, a test management module is arranged to request for automatic deployment task scheduling from a Kubernet cluster agent client through a WebSocket client;
s2, setting a cluster agent client to receive and analyze an automatic test deployment task, creating a testNG application deployment process in a cluster, setting the testNG application deployment process to establish a browser core intranet interface, and creating a browser container and a program container; the method comprises the following specific steps:
s21, judging whether a Helm chart tool is installed or not;
if not, installing a Helm chart tool and entering the step S22;
if yes, go directly to step S22;
s22, a Kubernetes cluster agent client is set to analyze a chart configuration file in an automatic test deployment task through a Helm chart tool;
s23, setting a Kubernets cluster agent client to create a TestNG application deployment process based on Selenium in the Kubernets cluster according to a chart configuration file analysis result;
s24, setting a TestNG application deployment process, establishing a WebDriver browser core intranet interface, and creating a browser container for opening a WebDriver browser core port and a program container for running an automatic test program;
s3, setting a TestNG application to start, starting a browser core port through a browser container, performing automatic test and outputting an automatic test result at the browser core port through a process sequence container, and closing the browser core port through the browser container after the automatic test is finished; the method comprises the following specific steps:
s31, setting a TestNG application to start, and connecting a browser container with a browser core intranet interface to start a Webdriver browser core port; the method comprises the following specific steps:
s311, setting a TestNG application to start, connecting a browser container with a browser core intranet interface to start a Webdriver browser core port, and judging whether the browser core port is started successfully;
if yes, go to step S32;
if not, go to step S312;
s312, setting a TestNG application to close a browser container and a program container through a survival probe;
s32, setting a TestNG application to perform automatic testing through a program container and based on a Webdriver browser core port, generating an automatic testing report and outputting the automatic testing report;
and S33, after the automation test is finished, the TestNG application is set, a WebDriver browser core port closing notice is sent to the browser container through the program container, and the browser container and the program container are closed after the browser core port is closed.
In some embodiments, in step S33, the TestNG application is set to end the lifecycle of the WebDriver browser through curl, thereby closing the WebDriver browser core port.
In some embodiments, in step S32, the Java class automation test case is executed to perform automation test, and an automation test report in format xmL is generated.
Example 3:
as shown in fig. 3, the present invention provides an arm64 architecture-based front-end UI automation testing apparatus, including:
the automatic test parameter acquisition module 1 is used for setting the test management module to receive the automatic test parameter configuration of a user on a configuration page and sending an automatic test deployment task to the cluster agent client; the automated test parameter acquisition module 1 includes:
the parameter acquisition unit 1.1 is used for setting the test management module to acquire the automatic test parameter configuration input by the user on the configuration page;
the deployment task generating unit 1.2 is used for setting the test management module to generate an automatic deployment task according to the automatic test parameter configuration;
the task deployment request unit 1.3 is used for setting a test management module to request the Kubernet cluster agent client to automatically deploy task scheduling through the WebSocket client;
the automatic test deployment module 2 is used for setting a cluster agent client to receive and analyze an automatic test deployment task, establishing a TestNG application deployment process in a cluster, setting the TestNG application deployment process to establish a browser core intranet interface, and establishing a browser container and a program container; the automated test deployment module 2 includes:
a Helm chart tool judging unit 2.1 for judging whether a Helm chart tool is installed or not;
a Helm chart tool mounting unit 2.2, which is used for mounting the Helm chart tool when the Helm chart tool is not mounted;
the configuration file analysis unit 2.3 is used for setting the Kubernets cluster agent client to analyze the chart configuration file in the automatic test deployment task through a Helm chart tool;
an application deployment process creating unit 2.4, configured to set the kubernets cluster agent client to create a TestNG application deployment process based on the Selenium in the kubernets cluster according to a chart configuration file parsing result;
the application deployment unit 2.5 is used for setting a TestNG application deployment process, establishing a WebDriver browser core intranet interface, and creating a browser container for opening a WebDriver browser core port and a program container for running an automatic test program;
the automatic test module 3 is used for setting the start of the TestNG application, starting a browser core port through a browser container, performing automatic test on the browser core port through a process sequence container, outputting an automatic test result, and closing the browser core port through the browser container after the automatic test is finished; the automated test module 3 includes:
the browser core port opening unit 3.1 is used for setting the start of the TestNG application and connecting a browser core intranet interface through a browser container to open the browser core port;
the automatic test unit 3.2 is used for setting the TestNG application to pass through a program container and carrying out automatic test based on a browser core port, generating an automatic test report and outputting the automatic test report;
a browser core port closing unit 3.3, configured to set that the TestNG application sends a browser core port closing notification to the browser container through the program container after the automated test is finished, and close the browser container and the program container after the browser core port is closed; the browser core port opening unit 3.1 includes:
the core port opening judging subunit is used for setting the TestNG application to be started, connecting the browser container with a browser core intranet interface to open the browser core port, and judging whether the browser core port is successfully opened or not;
and the container closing subunit is used for setting the TestNG application to close the browser container and the program container through the survival probe.
Although the present invention has been described in detail by referring to the drawings in connection with the preferred embodiments, the present invention is not limited thereto. Various equivalent modifications or substitutions can be made on the embodiments of the present invention by those skilled in the art without departing from the spirit and scope of the present invention, and these modifications or substitutions are within the scope of the present invention/any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.
Claims (6)
1. An arm64 architecture-based front-end UI automatic testing method is characterized by comprising the following steps:
s1, a test management module is arranged to receive automatic test parameter configuration of a user on a configuration page and send an automatic test deployment task to a cluster agent client; the method comprises the following specific steps:
s11, setting a test management module to obtain automatic test parameter configuration input by a user on a configuration page;
s12, setting a test management module to generate an automatic deployment task according to automatic test parameter configuration;
s13, a test management module is arranged to request for automatic deployment task scheduling from a Kubernet cluster agent client through a WebSocket client;
s2, setting a cluster agent client to receive and analyze an automatic test deployment task, creating a testNG application deployment process in a cluster, setting the testNG application deployment process to establish a browser core intranet interface, and creating a browser container and a program container; the method comprises the following specific steps:
s21, judging whether a Helm chart tool is installed or not;
if not, installing a Helm chart tool and entering the step S22;
if yes, go directly to step S22;
s22, a Kubernetes cluster agent client is set to analyze a chart configuration file in an automatic test deployment task through a Helm chart tool;
s23, setting a Kubernets cluster agent client to create a TestNG application deployment process based on Selenium in the Kubernets cluster according to a chart configuration file analysis result;
s24, setting a TestNG application deployment process, establishing a WebDriver browser core intranet interface, and creating a browser container for opening a WebDriver browser core port and a program container for running an automatic test program;
and S3, setting the TestNG application to start, starting a browser core port through the browser container, performing automatic test and outputting an automatic test result at the browser core port through the process sequence container, and closing the browser core port through the browser container after the automatic test is finished.
2. The arm64 architecture-based front-end UI automation test method of claim 1, wherein the step S3 includes the following steps:
s31, setting a TestNG application to start, and connecting a browser container with a browser core intranet interface to start a browser core port;
s32, setting a TestNG application to perform automatic testing through a program container and based on a browser core port, generating an automatic testing report and outputting the automatic testing report;
and S33, after the automated testing is finished, the TestNG application is set, a browser core port closing notice is sent to the browser container through the program container, and the browser container and the program container are closed after the browser core port is closed.
3. The arm64 architecture-based front-end UI automation test method of claim 1, wherein the step S31 includes the following steps:
s311, setting a TestNG application to start, connecting a browser container with a browser core intranet interface to start a browser core port, and judging whether the browser core port is successfully started;
if yes, go to step S32;
if not, go to step S312;
s312, setting the TestNG application to close the browser container and the program container through the survival probe.
4. An automated testing device for a front-end UI (user interface) based on arm64 architecture, comprising:
the automatic test parameter acquisition module (1) is used for setting the test management module to receive the automatic test parameter configuration of a user on a configuration page and sending an automatic test deployment task to the cluster agent client; the automatic test parameter acquisition module (1) comprises:
the parameter acquisition unit (1.1) is used for setting the test management module to acquire the automatic test parameter configuration input by a user on the configuration page;
the deployment task generating unit (1.2) is used for setting the test management module to generate an automatic deployment task according to the automatic test parameter configuration;
the task deployment request unit (1.3) is used for setting a test management module to request the Kubernet cluster agent client to automatically deploy task scheduling through the WebSocket client;
the automatic test deployment module (2) is used for setting a cluster agent client to receive and analyze an automatic test deployment task, establishing a TestNG application deployment process in a cluster, setting the TestNG application deployment process to establish a browser core intranet interface, and establishing a browser container and a program container; the automated test deployment module (2) comprises:
a Helm chart tool judging unit (2.1) for judging whether a Helm chart tool is installed or not;
a Helm chart tool mounting unit (2.2) for mounting the Helm chart tool when the Helm chart tool is not mounted;
the configuration file analysis unit (2.3) is used for setting the Kubernets cluster agent client to analyze the chart configuration file in the automatic test deployment task through a Helm chart tool;
the application deployment process creating unit (2.4) is used for setting the Kubernets cluster agent client to create a Selenium-based TestNG application deployment process in the Kubernets cluster according to the chart configuration file analysis result;
the application deployment unit (2.5) is used for setting a TestNG application deployment process, establishing a WebDriver browser core intranet interface, and creating a browser container for opening a WebDriver browser core port and a program container for running an automatic test program;
and the automatic test module (3) is used for setting the start of the TestNG application, opening the core port of the browser through the browser container, performing automatic test and outputting an automatic test result at the core port of the browser through the process sequence container, and closing the core port of the browser through the browser container after the automatic test is finished.
5. The arm64 architecture-based front end UI automation testing device of claim 4, characterized in that the automation testing module (3) comprises:
the browser core port opening unit (3.1) is used for setting the start of the TestNG application and connecting a browser core intranet interface through a browser container to open the browser core port;
the automatic test unit (3.2) is used for setting the TestNG application to pass through the program container and automatically test based on the browser core port, and generating and outputting an automatic test report;
and the browser core port closing unit (3.3) is used for setting that the TestNG application sends a browser core port closing notice to the browser container through the program container after the automation test is finished, and closing the browser container and the program container after the browser core port is closed.
6. The arm 64-based architecture front end UI automation testing device of claim 4, characterized in that the browser core port opening unit (3.1) comprises:
the core port opening judging subunit is used for setting the start of the TestNG application, connecting a browser container with a browser core intranet interface to open the browser core port, and judging whether the browser core port is successfully opened;
and the container closing subunit is used for setting the TestNG application to close the browser container and the program container through the survival probe.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010791620.7A CN111984534B (en) | 2020-08-07 | 2020-08-07 | Arm64 architecture-based front-end UI automatic testing method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010791620.7A CN111984534B (en) | 2020-08-07 | 2020-08-07 | Arm64 architecture-based front-end UI automatic testing method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111984534A CN111984534A (en) | 2020-11-24 |
| CN111984534B true CN111984534B (en) | 2022-06-14 |
Family
ID=73444608
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010791620.7A Active CN111984534B (en) | 2020-08-07 | 2020-08-07 | Arm64 architecture-based front-end UI automatic testing method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111984534B (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20110047527A1 (en) * | 2009-08-21 | 2011-02-24 | Vacava, Inc. | Systems, Methods, and Apparatuses for Providing Computing Device Deployment Environments for Developing Applications |
| US20140317537A1 (en) * | 2011-12-22 | 2014-10-23 | Tencent Technology (Shenzhen) Company Limited | Browser based application program extension method and device |
| CN106371868A (en) * | 2016-08-29 | 2017-02-01 | 浪潮(北京)电子信息产业有限公司 | Automatic test method, system and test device |
| CN108519952A (en) * | 2018-04-13 | 2018-09-11 | 南京新贝金服科技有限公司 | A kind of distributed WEB automatization test systems and method |
| CN111026634A (en) * | 2019-09-27 | 2020-04-17 | 珠海随变科技有限公司 | Interface automation test system, method, device and storage medium |
-
2020
- 2020-08-07 CN CN202010791620.7A patent/CN111984534B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20110047527A1 (en) * | 2009-08-21 | 2011-02-24 | Vacava, Inc. | Systems, Methods, and Apparatuses for Providing Computing Device Deployment Environments for Developing Applications |
| US20140317537A1 (en) * | 2011-12-22 | 2014-10-23 | Tencent Technology (Shenzhen) Company Limited | Browser based application program extension method and device |
| CN106371868A (en) * | 2016-08-29 | 2017-02-01 | 浪潮(北京)电子信息产业有限公司 | Automatic test method, system and test device |
| CN108519952A (en) * | 2018-04-13 | 2018-09-11 | 南京新贝金服科技有限公司 | A kind of distributed WEB automatization test systems and method |
| CN111026634A (en) * | 2019-09-27 | 2020-04-17 | 珠海随变科技有限公司 | Interface automation test system, method, device and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111984534A (en) | 2020-11-24 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109933522B (en) | Test method, test system and storage medium for automatic case | |
| CN110633209B (en) | Automatic testing method and system for vehicle-mounted android multimedia navigator | |
| CN101707399B (en) | Method and system for acquiring electric energy information | |
| KR101008977B1 (en) | Method of testing OSGi service platform and test tool thereof | |
| CN105094783A (en) | Method and device for testing Android application stability | |
| CN102866944B (en) | Pressure testing system and method | |
| CN107577602A (en) | A kind of method of testing of APP interfaces, apparatus and system | |
| CN110955600B (en) | Interface testing method and device | |
| CN108536431A (en) | A kind of global command's row creates front end project approach and system | |
| WO2007061241A1 (en) | Error test method for mobile communication terminals | |
| CN109445384B (en) | Multi-device control system | |
| CN111984534B (en) | Arm64 architecture-based front-end UI automatic testing method and device | |
| CN108833005B (en) | Optical network communication equipment and automatic test kit and method for networking service thereof | |
| CN113961570A (en) | Real-time acquisition method applied to MYSQL BINLog change data | |
| CN108829577A (en) | A kind of automated testing method of application program capacity | |
| CN109739754B (en) | Automatic testing method and system for application program based on WeChat development | |
| CN101296462A (en) | Method and system for batch execution of mobile terminal software automatic test | |
| CN109614320A (en) | A kind of method and terminal detecting code interface accuracy | |
| CN110489336A (en) | A kind of software interface Test cases technology and maintaining method and its device | |
| CN113641594B (en) | Cross-terminal automatic testing method and related device | |
| US11366642B1 (en) | Change migration: processes for ensuring successful deployment of design changes | |
| CN110795330A (en) | Monkey pressure testing method and device | |
| CN111427770B (en) | Resource testing method and related equipment | |
| Scherfke | Mosaik documentation | |
| CN112231158A (en) | Method and device for testing floating-point operation performance of multi-card GPGPU cluster |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |