CN114153726A - Login test method and device based on linux desktop operating system - Google Patents
Login test method and device based on linux desktop operating system Download PDFInfo
- Publication number
- CN114153726A CN114153726A CN202111414992.9A CN202111414992A CN114153726A CN 114153726 A CN114153726 A CN 114153726A CN 202111414992 A CN202111414992 A CN 202111414992A CN 114153726 A CN114153726 A CN 114153726A
- Authority
- CN
- China
- Prior art keywords
- login
- data
- data file
- screen capture
- input
- 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.)
- Granted
Links
- 238000010998 test method Methods 0.000 title description 3
- 238000012360 testing method Methods 0.000 claims abstract description 67
- 238000001514 detection method Methods 0.000 claims abstract description 13
- 230000000694 effects Effects 0.000 claims abstract description 13
- 238000000034 method Methods 0.000 abstract description 22
- 230000004048 modification Effects 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 230000008569 process Effects 0.000 description 3
- 238000010586 diagram Methods 0.000 description 2
- 230000002159 abnormal effect Effects 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 238000012804 iterative process Methods 0.000 description 1
- 230000026676 system process 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
- G06F11/3684—Test management for test design, e.g. generating new test cases
-
- 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
- G06F11/3688—Test management for test execution, e.g. scheduling of test suites
-
- 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
- G06F11/3692—Test management for test results analysis
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/16—File or folder operations, e.g. details of user interfaces specifically adapted to file systems
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Human Computer Interaction (AREA)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- Debugging And Monitoring (AREA)
Abstract
The invention discloses a login testing method and device based on a linux desktop operating system. The original input data can be written into the equipment node again according to the input time sequence by calling, so that the automatic login behavior of the operating system and the account password login behavior of an actual tester are not different. The automatic screen capture and result detection operations after the automatic login of the operating system are realized. The method can realize repeated automatic login test of a single user of the operating system only by once deployment without manual intervention, can effectively improve the test efficiency, and saves the time of testers. The method is particularly significant for reproducing the log-in function fault problem and verifying the solution effect.
Description
Technical Field
The application relates to the field of computer automation testing, in particular to a login testing method and device based on a linux desktop operating system.
Background
In the iterative process of desktop operating system products, in order to ensure the correctness and stability of the system login function and avoid the probability abnormal loading of system component icons or customized application icons on the desktop after a user logs in the system, the login test needs to be repeatedly performed in the test process. Most conventional testing tools operate in a graphical system environment where a user has logged in. However, when the operating system is in the login interface state, some system processes, environment variables and graphic libraries related to the user are not loaded, and most application software, especially graphic software, depends on a specific user environment and does not have running conditions. At present, the logging-in test method of the graphical interface of the operating system mainly adopts manual password input logging-in and judges the correctness of desktop loading by manual work. This approach not only requires a significant amount of time and cost for the tester, but also is not convenient for reproducing sporadic problems and validating solutions.
Disclosure of Invention
In order to solve the problems in the prior art, the invention provides a login testing method and device based on a linux desktop operating system, and solves the problems of low manual efficiency and high error probability in the current system login test.
In order to achieve the above object, a first aspect of the present invention provides a login testing method based on a linux desktop operating system, including the following steps:
step S1, determining the equipment node of the input equipment;
step S2, recording login operation data written into the equipment node during login operation, and generating a login data file according to the login operation data;
step S3, recording screen capturing operation data written into the equipment node when screen capturing operation is carried out, and generating a screen capturing data file according to the screen capturing operation data;
step S4, uploading the login data file, the screenshot data file and a reference picture, wherein the reference picture is a picture when a system component icon or a customized application icon is loaded normally;
step S5, rewriting the data in the login data file into the equipment according to the input time sequence, and automatically logging in;
step S6, rewriting data in the screen capture data file into the equipment according to the input time sequence, automatically capturing the screen and acquiring a screen capture image;
step S7, comparing the screen capture image with a reference picture and recording a test result;
and step S8, repeating the steps S5-S7 until the test times reach the preset threshold value.
Wherein the step S2 includes:
step S201, starting a system, and entering a graphical user login interface;
step S202, executing a terminal entering command, inputting a created account password for logging in, and entering a text console;
step S203, recording the input information of the device node, including: operation type, operation code, operation value, time difference between the last operation and the current operation;
step S204, switching to a user login graphical interface, and executing account login operation;
and S205, switching to a text console, stopping recording and saving the recorded information into a login data file.
Wherein the step S3 includes:
s301, logging in a system, and entering a user graphical interface;
step S302, recording the input information of the device node, including: operation type, operation code, operation value, time difference between the last operation and the current operation;
step S303, manually carrying out screen capturing operation;
and step S304, stopping recording and saving the recording information into a screen capture data file.
Wherein the step S1 includes:
step S101, checking a/proc/bu/input/device file in a system, and finding corresponding device information of an input device in the/proc/bu/input/device file through a Name field;
s102, finding a corresponding event value in the value of the Handler field;
and S103, determining a specific path of the equipment node according to the event value.
Wherein the step S4 includes:
step S401, uploading the recorded login data file to a system under a home/directory, and naming the login data file as autologic data;
step S402, uploading the recorded screenshot data file to a system under a home/directory, and naming the screenshot data file as screen.
And S403, modifying the configuration file of the display manager.
Wherein the step S5 includes:
s501, detecting whether the user login interface is loaded completely according to the system log;
step S502, if the loading is not completed after the set time limit is exceeded, the test is ended and a test failure result is generated, and if the loading is completed within the set time limit, the step S503 is executed;
step S503, reading and analyzing the login data file;
step S504 writes the data recorded in the log data file into the device at the input timing.
Wherein the step S6 includes:
step S601, judging whether the user desktop is completely loaded through a system log;
step S602, if the loading is not completed after the set time limit is exceeded, ending the test and generating a test failure result, and if the loading is completed within the set time limit, entering step S603;
step S603, reading and analyzing the screenshot data file;
and step S604, writing the data recorded in the screen capture data file into the equipment according to the input time sequence.
Wherein the step S7 includes:
step S701, detecting whether a screen capture image is generated or not;
step S702, if the screen capture image exceeds the set time limit and is not successfully generated, ending the test and generating a test failure result, and if the generation of the set time limit is finished, entering step S703;
step S703, after detecting the screen capture image, dividing the screen capture file according to the predefined application display position;
step S704, comparing whether the single application display effect after being divided is consistent with the application display effect in the reference picture one by one;
and step S705, recording a comparison test result.
The second aspect of the present invention provides a login testing apparatus based on a linux desktop operating system, including:
the data recording module is used for recording specified input equipment information and input data information in the text type console, generating a login data file by recording login operation data written into the equipment node during login operation, and generating a screen capture data file by recording screen capture operation data written into the equipment node during screen capture operation;
the login module is used for reading and analyzing a login data file in the text type console and rewriting data into an equipment file according to an input time sequence;
the screen capture module is used for reading and analyzing a screen capture data file in the text console and rewriting data into an equipment file according to an input time sequence;
the result detection module is used for comparing the screen capture image with the reference picture and recording a test result;
the repeated execution module is used for sending a restart command to the system when the test frequency does not reach the threshold value, and carrying out the next test;
and the system configuration module is used for calling and executing the login module, the screen capture module, the result detection module and the repeated execution module.
According to the technical scheme, the technical scheme of the invention has the following advantages:
according to the login testing method and device based on the linux desktop operating system, the automatic login of the operating system is realized by recording and storing the input data of the equipment nodes during the operation of automatic screen capture and result detection and then calling the stored input data. The original input data can be written into the equipment node again according to the input time sequence by calling, so that the automatic login behavior of the operating system and the account password login behavior of an actual tester are not different. The automatic screen capture and result detection operations after the automatic login of the operating system are realized. The method can realize repeated automatic login test of a single user of the operating system only by once deployment without manual intervention, can effectively improve the test efficiency, and saves the time of testers. The method is particularly significant for reproducing the log-in function fault problem and verifying the solution effect.
Drawings
In order to express the technical scheme of the embodiment of the invention more clearly, the drawings used for describing the embodiment will be briefly introduced below, and obviously, the drawings in the following description are only some embodiments of the invention, and other drawings can be obtained by those skilled in the art without creative efforts.
FIG. 1 is a flowchart of a login testing method based on a linux desktop operating system in an embodiment of the present invention;
FIG. 2 is a flowchart illustrating the step S5 according to an embodiment of the present invention;
FIG. 3 is a flowchart illustrating the step S6 according to an embodiment of the present invention;
FIG. 4 is a flowchart illustrating the step S7 according to an embodiment of the present invention;
FIG. 5 is a block diagram of a login testing device based on the linux desktop operating system in an embodiment of the present invention;
fig. 6 is a schematic diagram of an operating principle of a login testing device based on a linux desktop operating system in an embodiment of the present invention.
Detailed Description
In order to make the technical solutions of the present application better understood, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the 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 application.
For the convenience of understanding the scheme of the present invention, taking a touch notebook computer as an example, a linux desktop operating system, specifically, a galaxy kylin desktop operating system, is installed in the computer, and the desktop operating system simultaneously supports a touch screen, a keyboard, a mouse, and the like as input devices. The touch screen is used as account password input equipment, and the screen capture operation key is a PtrSc key in a notebook keyboard. The operating system of the Galaxy kylin desktop is simply called as an kylin desktop system in the following. Referring to fig. 1, a login testing method based on a linux desktop operating system in this embodiment includes:
and step S1, determining the device node of the input device. The method comprises the steps of searching device nodes corresponding to input devices for executing login operation and screen capture operation in an kylin desktop system.
The kylin desktop system inherits the characteristics of an input subsystem in a Linux operating system. The equipment nodes are the components of the input subsystem. The input subsystem manages external input devices of the whole kylin desktop system. And the input subsystem feeds back the received data to the upper application through the equipment node. When the external input equipment performs input operation, the input subsystem writes input data into the equipment node, and then the upper layer application reads and processes the data in the equipment node, so that interaction with the external input equipment is realized.
The core of the method for realizing the automatic login of the user account password in the method is also to simulate the operation of logging in the Galaxy kylin desktop operating system by a tester by using the account password by writing data into the equipment node.
Step S1 specifically includes the following steps:
step S101, checking the/proc/bus/input/devices file, and finding the corresponding device information of the input device in the/proc/bus/input/devices file through the Name field.
The/proc/bus/input/devices is a file in the input subsystem, and all device information registered in the kernel of the operating system is written into the file. The device information in the file comprises a Name field and Handlers fields, wherein the Name field comprises the Name of the device, and the Handlers field comprises the event value related to the device node.
In the system, looking at the/proc/bus/input/devices file, the following two pieces of information can be found:
I:Bus＝0011Vendor＝0001Product＝0001Version＝ab83
N:Name＝"AT Translated Set 2keyboard"
P:Phys＝isa0060/serio0/input0
S:Sysfs＝/devices/platform/i8042/serio0/input/input4
U:Uniq＝
H:Handlers＝sysrq kbd leds event4
B:PROP＝0
B:EV＝120013
B:KEY＝20000 20 0 0 1500f02100000 3803078f900d401 feffffdfffefffff fffffffffffffffe
B:MSC＝10
B:LED＝7
...
I:Bus＝0018Vendor＝04f3 Product＝3139Version＝0100
N:Name＝"ELAN0722:00 04F3:3139Touchpad"
P:Phys＝i2c-ELAN0722:00
S:
Sysfs＝/devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-15/i2c-ELAN0722:00/0018:04F3:3139.0002/input/input16
U:Uniq＝
H:Handlers＝event8
B:PROP＝5
B:EV＝1b
B:KEY＝e520 10000 0 0 0 0
B:ABS＝2e0800000000003
B:MSC＝20
according to the Name field, the first part of information belongs to the keyboard device, and the second part of information belongs to the touch screen device.
And step S102, finding the corresponding event value in the values of the Handlers field. According to the Handers field in the device information, the keyboard device corresponds to the event4, and the touch screen corresponds to the event 8.
And S103, determining a specific path of the equipment node according to the event value. In the kylin desktop system, the directories of the equipment nodes are/dev/input/. The event value corresponding to each device node is the specific file name. According to the judgment that the event value in the step S102 can be, the device node path of the keyboard device is/dev/input/event 4, and the device node path of the touch screen device is/dev/input/event 8.
And step S2, recording login operation data written into the equipment node during login operation, and generating a login data file according to the login operation data. The step aims to record input information of equipment nodes corresponding to the touch screen when a tester logs in by using the touch screen.
Step S2 specifically includes the following steps:
step S201, starting an kylin desktop system, and entering a graphical user login interface;
s202, pressing Ctrl + Alt + F1, inputting the created account password for login, and entering a text console;
step S203, starting a data recording module, and recording input information of the/dev/input/event 8 file, wherein the input information comprises: data such as operation type, operation code, operation value, time difference between the last operation and the current operation, and the like;
s204, pressing Ctrl + Alt + F7, switching to a user login graphical interface, and manually executing account login operation by using touch screen equipment;
and S205, pressing Ctrl + Alt + F1, switching to a text console, stopping the data recording module, and storing the recorded information into a login data file.
And step S3, recording screen capturing operation data written into the equipment node during screen capturing operation, and generating a screen capturing data file according to the screen capturing operation data. The step aims to record input information of a device node corresponding to the keyboard when a tester presses a PtrSc key to capture a screen.
Step S3 specifically includes the following steps:
s301, logging in an kylin desktop system and entering a graphical user interface;
step S302, starting a data recording module, recording input information of the device node/dev/input/event 4, including: operation type, operation code, operation value, time difference between the last operation and the current operation;
step S303, pressing a PtrSc key on a keyboard to perform screen capturing operation;
and step S304, stopping the data recording module and saving the recorded information into a screen capture data file.
And S4, uploading the login data file, the screen capture data file and a reference picture, wherein the reference picture is a picture when a system component icon or a customized application icon is loaded normally. The method comprises the steps of uploading login data files, screen capture data files and reference pictures to an kylin desktop system, modifying configuration file parameters of a display manager to enable the system to simultaneously execute a login module when entering a login interface, executing a step S5 when the login module works, rewriting data in the login data files into equipment by the login module according to an input time sequence during login, and further achieving automatic login of account numbers and passwords of the kylin desktop system.
Step S4 specifically includes the following steps:
step S401, uploading the recorded login data file to the system under the home/directory, and naming the login data file as autologic.
And S402, uploading the recorded screenshot data file to a system under a home/directory, and naming the screenshot data file as screen.
And S403, modifying the configuration file of the display manager. And modifying the configuration file/etc/lightdm/lightdm.conf, setting the parameter value of the greener-setup-script in the configuration item [ Seat: ] in the configuration file as a calling method of the login module, and executing the step S5 by calling the login module.
And step S5, rewriting the data in the login data file into the equipment according to the input sequence, and automatically logging in.
Referring to fig. 2, step S5 specifically includes:
s501, detecting whether the user login interface is loaded completely according to the system log;
step S502, if the overtime is not loaded, recording a failure test result;
step S503, after the user login interface is loaded, reading and analyzing the login data file autologic.data;
step S504 is to rewrite the data recorded in the log data file into the device in accordance with the input timing.
And step S6, rewriting the data in the screen capture data file into the equipment according to the input time sequence, automatically capturing the screen and acquiring the screen capture image. The method aims to enable a user to automatically call a screen capture module after logging in the kylin desktop system, read, analyze and process a screen capture data file, rewrite data in the screen capture data file into equipment according to an input time sequence during logging in, and further achieve automatic screen capture after logging in by the user.
The method for writing the screen capture module calling method into the user login self-starting script comprises the following steps: and adding a screen capture module calling method into the/etc/profile script file.
Referring to fig. 3, the specific steps of step S6 are:
step S601, judging whether the user desktop is completely loaded through a system log;
step S602, if the loading is not completed in overtime, recording a failure test result;
step S603, after the desktop loading is finished, reading and analyzing a screenshot data file screen.
And step S604, rewriting the data recorded in the screen capture data file into the equipment according to the input time sequence.
And step S7, comparing the screen capture image with a reference picture and recording a test result. The method comprises the steps of detecting whether the display of each application in the desktop is correct after a user logs in the kylin desktop system. Referring to fig. 4, step S7 specifically includes:
step S701, detecting whether a screen capture image is generated or not;
step S702, if the screen capture image exceeds the set time limit and is not successfully generated, ending the test and generating a test failure result, and if the generation of the set time limit is finished, entering step S703;
step S703, after detecting the screen capture image, dividing the screen capture file according to the predefined application display position;
step 704, comparing the single application display effect after being divided with the application display effect in the reference picture one by one to determine whether the single application display effect is consistent with the application display effect in the reference picture.
And step S8, repeating the steps S5-S7 until the test times reach the preset threshold value.
In the embodiment, the automatic login of the operating system is realized by recording and storing the input data of the equipment node during the operation of automatic screen capture and result detection and then calling the stored input data. The original input data can be written into the equipment node again according to the input time sequence by calling, so that the automatic login behavior of the operating system and the account password login behavior of an actual tester are not different. The automatic screen capture and result detection operations after the automatic login of the operating system are realized. The method can realize repeated automatic login test of a single user of the operating system only by once deployment without manual intervention, can effectively improve the test efficiency, and saves the time of testers. The method is particularly significant for reproducing the log-in function fault problem and verifying the solution effect.
Referring to fig. 5, an embodiment of the present invention further provides a login testing apparatus based on a linux desktop operating system, including:
the data recording module is used for recording specified input equipment information and input data information in the text type console, generating a login data file by recording login operation data written into the equipment node during login operation, and generating a screen capture data file by recording screen capture operation data written into the equipment node during screen capture operation;
the login module is used for reading and analyzing a login data file in the text type console and rewriting data into an equipment file according to an input time sequence;
the screen capture module is used for reading and analyzing a screen capture data file in the text console and rewriting data into an equipment file according to an input time sequence;
the result detection module is used for comparing the screen capture image with the reference picture and recording a test result;
the repeated execution module is used for sending a restart command to the system when the test frequency does not reach the threshold value, and carrying out the next test;
and the system configuration module is used for calling and executing the login module, the screen capture module, the result detection module and the repeated execution module.
The working principle of the embodiment is shown in fig. 6. The method comprises the steps of firstly starting an operating system, then starting a login interface, executing a user start script, calling a login module by a system configuration module to the user start script to execute a working step, rewriting a login data file into an equipment file according to an input time sequence, starting a desktop loading by the system, calling and executing a screen capture module after the loading is finished, reading and analyzing the screen capture data file in a text console, rewriting data into the equipment file according to the input time sequence, carrying out screen capture operation to obtain a screen capture image, and then segmenting the screen capture image according to an application space position and detecting application display effects one by one through a calling result detection module to obtain a test result. An additional call is defined for the Galois desktop operating system through the login data file, the login module and the modification configuration file, and automatic login of the operating system is achieved. Because the additional call can rewrite the original input data into the equipment node according to the input time sequence, the automatic login behavior of the operating system is not different from the account password login behavior of the actual tester. And the automatic screen capture and result detection operations after the automatic login of the operating system are realized through the system configuration file. The method can realize repeated automatic login test of a single user of the operating system only by once deployment without manual intervention, can effectively improve the test efficiency, and saves the time of testers. The method is particularly significant for reproducing the log-in function fault problem and verifying the solution effect.
It is to be understood that the above-described embodiments of the present invention are merely illustrative of or explaining the principles of the invention and are not to be construed as limiting the invention. Therefore, any modification, equivalent replacement, improvement and the like made without departing from the spirit and scope of the present invention should be included in the protection scope of the present invention. Further, it is intended that the appended claims cover all such variations and modifications as fall within the scope and boundaries of the appended claims or the equivalents of such scope and boundaries.
Claims (9)
1. A login testing method based on a linux desktop operating system is characterized by comprising the following steps:
step S1, determining the equipment node of the input equipment;
step S2, recording login operation data written into the equipment node during login operation, and generating a login data file according to the login operation data;
step S3, recording screen capturing operation data written into the equipment node when screen capturing operation is carried out, and generating a screen capturing data file according to the screen capturing operation data;
step S4, uploading the login data file, the screenshot data file and a reference picture, wherein the reference picture is a picture when a system component icon or a customized application icon is loaded normally;
step S5, rewriting the data in the login data file into the equipment according to the input time sequence, and automatically logging in;
step S6, rewriting data in the screen capture data file into the equipment according to the input time sequence, automatically capturing the screen and acquiring a screen capture image;
step S7, comparing the screen capture image with a reference picture and recording a test result;
and step S8, repeating the steps S5-S7 until the test times reach the preset threshold value.
2. The linux desktop operating system-based login testing method of claim 1, wherein the step S2 comprises:
step S201, starting a system, and entering a graphical user login interface;
step S202, executing a terminal entering command, inputting a created account password for logging in, and entering a text console;
step S203, recording the input information of the device node, including: operation type, operation code, operation value, time difference between the last operation and the current operation;
step S204, switching to a user login graphical interface, and executing account login operation;
and S205, switching to a text console, stopping recording and saving the recorded information into a login data file.
3. The linux desktop operating system-based login testing method of claim 1, wherein the step S3 comprises:
s301, logging in a system, and entering a user graphical interface;
step S302, recording the input information of the device node, including: operation type, operation code, operation value, time difference between the last operation and the current operation;
step S303, manually carrying out screen capturing operation;
and step S304, stopping recording and saving the recording information into a screen capture data file.
4. The linux desktop operating system-based login testing method of claim 1, wherein the step S1 comprises:
step S101, checking a/proc/bu/input/device file in a system, and finding corresponding device information of an input device in the/proc/bu/input/device file through a Name field;
s102, finding a corresponding event value in the value of the Handler field;
and S103, determining a specific path of the equipment node according to the event value.
5. The linux desktop operating system-based login testing method of claim 1, wherein the step S4 comprises:
step S401, uploading the recorded login data file to a system under a home/directory, and naming the login data file as autologic data;
step S402, uploading the recorded screenshot data file to a system under a home/directory, and naming the screenshot data file as screen.
And S403, modifying the configuration file of the display manager.
6. The linux desktop operating system-based login testing method of claim 1, wherein the step S5 comprises:
s501, detecting whether the user login interface is loaded completely according to the system log;
step S502, if the loading is not completed after the set time limit is exceeded, the test is ended and a test failure result is generated, and if the loading is completed within the set time limit, the step S503 is executed;
step S503, reading and analyzing the login data file;
step S504 writes the data recorded in the log data file into the device at the input timing.
7. The linux desktop operating system-based login testing method of claim 1, wherein the step S6 comprises:
step S601, judging whether the user desktop is completely loaded through a system log;
step S602, if the loading is not completed after the set time limit is exceeded, ending the test and generating a test failure result, and if the loading is completed within the set time limit, entering step S603;
step S603, reading and analyzing the screenshot data file;
and step S604, writing the data recorded in the screen capture data file into the equipment according to the input time sequence.
8. The linux desktop operating system-based login testing method of claim 1, wherein the step S7 comprises:
step S701, detecting whether a screen capture image is generated or not;
step S702, if the screen capture image exceeds the set time limit and is not successfully generated, ending the test and generating a test failure result, and if the generation of the set time limit is finished, entering step S703;
step S703, after detecting the screen capture image, dividing the screen capture file according to the predefined application display position;
step S704, comparing whether the single application display effect after being divided is consistent with the application display effect in the reference picture one by one;
and step S705, recording a comparison test result.
9. A login testing device based on a linux desktop operating system is characterized by comprising:
the data recording module is used for recording specified input equipment information and input data information in the text type console, generating a login data file by recording login operation data written into the equipment node during login operation, and generating a screen capture data file by recording screen capture operation data written into the equipment node during screen capture operation;
the login module is used for reading and analyzing a login data file in the text type console and rewriting data into an equipment file according to an input time sequence;
the screen capture module is used for reading and analyzing a screen capture data file in the text console and rewriting data into an equipment file according to an input time sequence;
the result detection module is used for comparing the screen capture image with the reference picture and recording a test result;
the repeated execution module is used for sending a restart command to the system when the test frequency does not reach the threshold value, and carrying out the next test;
and the system configuration module is used for calling and executing the login module, the screen capture module, the result detection module and the repeated execution module.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111414992.9A CN114153726B (en) | 2021-11-25 | 2021-11-25 | Login test method and device based on linux desktop operating system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111414992.9A CN114153726B (en) | 2021-11-25 | 2021-11-25 | Login test method and device based on linux desktop operating system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114153726A true CN114153726A (en) | 2022-03-08 |
| CN114153726B CN114153726B (en) | 2024-05-17 |
Family
ID=80457631
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111414992.9A Active CN114153726B (en) | 2021-11-25 | 2021-11-25 | Login test method and device based on linux desktop operating system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114153726B (en) |
Citations (18)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101241466A (en) * | 2007-02-08 | 2008-08-13 | 深圳迈瑞生物医疗电子股份有限公司 | Embedded software test method and system |
| US7478436B1 (en) * | 2008-01-17 | 2009-01-13 | International Business Machines Corporation | System and method for providing last log-in screen shots for security confirmation |
| TW201201014A (en) * | 2010-06-30 | 2012-01-01 | Phoenix Tech Ltd | Adapter and debug method using the same |
| US20140344907A1 (en) * | 2011-11-21 | 2014-11-20 | Beijing Qihoo Technology Company Limited | Auto login method and device |
| CN107844717A (en) * | 2016-09-21 | 2018-03-27 | 中兴通讯股份有限公司 | Safe input system, method and intelligent terminal |
| JP2018060490A (en) * | 2016-09-30 | 2018-04-12 | 株式会社日本総合研究所 | Customer support system, management server, and management method using sns's picture symbols |
| CN108920380A (en) * | 2018-07-20 | 2018-11-30 | 百度在线网络技术（北京）有限公司 | Test method, device, server, equipment and the storage medium of the software compatibility |
| CN109388556A (en) * | 2017-08-11 | 2019-02-26 | 航天信息股份有限公司 | A kind of analysis method and device of test process |
| US20190129823A1 (en) * | 2017-10-28 | 2019-05-02 | Facebook, Inc. | Analyzing screenshots to detect application issues |
| CN109901955A (en) * | 2017-12-07 | 2019-06-18 | 上海擎感智能科技有限公司 | A kind of method and system for testing power-on screen state |
| CN110896497A (en) * | 2019-10-30 | 2020-03-20 | 厦门天锐科技股份有限公司 | Image processing method, video playing method and device |
| CN110968476A (en) * | 2019-11-15 | 2020-04-07 | 苏州浪潮智能科技有限公司 | Method and device for automatically monitoring login information of Linux system |
| US10635574B1 (en) * | 2018-11-06 | 2020-04-28 | Login VSI B.V. | Screenshot testing of applications on windows desktop environments |
| CN111127342A (en) * | 2019-12-05 | 2020-05-08 | Oppo广东移动通信有限公司 | Image processing method and device, storage medium and terminal equipment |
| CN111858321A (en) * | 2020-07-09 | 2020-10-30 | 麒麟软件有限公司 | Xdotool-based automatic testing method |
| CN112598074A (en) * | 2020-12-28 | 2021-04-02 | 深圳市欢太科技有限公司 | Image processing method and device, computer readable storage medium and electronic device |
| CN113468076A (en) * | 2021-08-19 | 2021-10-01 | 平安普惠企业管理有限公司 | Application program exception testing method, device, equipment and storage medium |
| CN113553226A (en) * | 2021-07-23 | 2021-10-26 | 曙光信息产业股份有限公司 | Startup and shutdown testing method and device, testing system, electronic equipment and storage medium |
-
2021
- 2021-11-25 CN CN202111414992.9A patent/CN114153726B/en active Active
Patent Citations (18)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101241466A (en) * | 2007-02-08 | 2008-08-13 | 深圳迈瑞生物医疗电子股份有限公司 | Embedded software test method and system |
| US7478436B1 (en) * | 2008-01-17 | 2009-01-13 | International Business Machines Corporation | System and method for providing last log-in screen shots for security confirmation |
| TW201201014A (en) * | 2010-06-30 | 2012-01-01 | Phoenix Tech Ltd | Adapter and debug method using the same |
| US20140344907A1 (en) * | 2011-11-21 | 2014-11-20 | Beijing Qihoo Technology Company Limited | Auto login method and device |
| CN107844717A (en) * | 2016-09-21 | 2018-03-27 | 中兴通讯股份有限公司 | Safe input system, method and intelligent terminal |
| JP2018060490A (en) * | 2016-09-30 | 2018-04-12 | 株式会社日本総合研究所 | Customer support system, management server, and management method using sns's picture symbols |
| CN109388556A (en) * | 2017-08-11 | 2019-02-26 | 航天信息股份有限公司 | A kind of analysis method and device of test process |
| US20190129823A1 (en) * | 2017-10-28 | 2019-05-02 | Facebook, Inc. | Analyzing screenshots to detect application issues |
| CN109901955A (en) * | 2017-12-07 | 2019-06-18 | 上海擎感智能科技有限公司 | A kind of method and system for testing power-on screen state |
| CN108920380A (en) * | 2018-07-20 | 2018-11-30 | 百度在线网络技术（北京）有限公司 | Test method, device, server, equipment and the storage medium of the software compatibility |
| US10635574B1 (en) * | 2018-11-06 | 2020-04-28 | Login VSI B.V. | Screenshot testing of applications on windows desktop environments |
| CN110896497A (en) * | 2019-10-30 | 2020-03-20 | 厦门天锐科技股份有限公司 | Image processing method, video playing method and device |
| CN110968476A (en) * | 2019-11-15 | 2020-04-07 | 苏州浪潮智能科技有限公司 | Method and device for automatically monitoring login information of Linux system |
| CN111127342A (en) * | 2019-12-05 | 2020-05-08 | Oppo广东移动通信有限公司 | Image processing method and device, storage medium and terminal equipment |
| CN111858321A (en) * | 2020-07-09 | 2020-10-30 | 麒麟软件有限公司 | Xdotool-based automatic testing method |
| CN112598074A (en) * | 2020-12-28 | 2021-04-02 | 深圳市欢太科技有限公司 | Image processing method and device, computer readable storage medium and electronic device |
| CN113553226A (en) * | 2021-07-23 | 2021-10-26 | 曙光信息产业股份有限公司 | Startup and shutdown testing method and device, testing system, electronic equipment and storage medium |
| CN113468076A (en) * | 2021-08-19 | 2021-10-01 | 平安普惠企业管理有限公司 | Application program exception testing method, device, equipment and storage medium |
Non-Patent Citations (1)
| Title |
|---|
| 赵娜;孔洁;邢家梁;: "一种基于archiso的自生系统设计", 电脑与信息技术, no. 06, 15 December 2019 (2019-12-15) * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114153726B (en) | 2024-05-17 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102736978B (en) | A kind of method and device detecting the installment state of application program | |
| TWI533123B (en) | Method and system for automated test and result comparison | |
| WO2019161619A1 (en) | Automatic interface test method and apparatus, and device and computer-readable storage medium | |
| CN111124919A (en) | User interface testing method, device, equipment and storage medium | |
| CN107608609B (en) | Event object sending method and device | |
| US8448138B2 (en) | Recording user-driven events within a computing system | |
| CN106126424A (en) | A kind of visual automated testing method of script, device and mobile terminal | |
| CN115080398A (en) | Automatic interface test system and method | |
| CN115658529A (en) | Automatic testing method for user page and related equipment | |
| CN108874441B (en) | Board card configuration method, device, server and storage medium | |
| CN104320793A (en) | Mobile phone short message automated test method and system | |
| CN112231206A (en) | Script editing method for application program test, computer readable storage medium and test platform | |
| CN116166525A (en) | Method and device for generating test script | |
| Usman et al. | Test case generation from android mobile applications focusing on context events | |
| CN111274130A (en) | Automatic testing method, device, equipment and storage medium | |
| CN111190791A (en) | Application exception reporting method and device and electronic equipment | |
| WO2022054101A1 (en) | Method and system for automated software accessibility testing | |
| CN113742224A (en) | Test system, method, device, computer equipment and storage medium | |
| CN112650673A (en) | Method and device for creating test case in transaction tracking system and electronic equipment | |
| CN114153726B (en) | Login test method and device based on linux desktop operating system | |
| CN115454856B (en) | Multi-application security detection method, device, medium and electronic equipment | |
| CN111737129B (en) | Service control method, device, computer readable medium and electronic equipment | |
| CN108984386A (en) | Test method, device and the storage medium of application program search | |
| CN110806981B (en) | Application program testing method, device, equipment and storage medium | |
| CN111327746B (en) | Method and device for determining pressure abnormity of mobile terminal |
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 |