CN114153726B - 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
- CN114153726B CN114153726B CN202111414992.9A CN202111414992A CN114153726B CN 114153726 B CN114153726 B CN 114153726B CN 202111414992 A CN202111414992 A CN 202111414992A CN 114153726 B CN114153726 B CN 114153726B
- Authority
- CN
- China
- Prior art keywords
- login
- data file
- screen capturing
- test
- operating system
- 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
- 238000010998 test method Methods 0.000 title claims abstract description 16
- 238000012360 testing method Methods 0.000 claims abstract description 51
- 238000000034 method Methods 0.000 claims abstract description 14
- 230000000694 effects Effects 0.000 claims abstract description 11
- 230000011218 segmentation Effects 0.000 claims description 3
- 238000001514 detection method Methods 0.000 abstract description 11
- 238000012795 verification Methods 0.000 abstract description 5
- 230000000306 recurrent effect Effects 0.000 abstract description 4
- 238000012986 modification Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 238000010586 diagram Methods 0.000 description 2
- 230000008569 process Effects 0.000 description 2
- 230000002159 abnormal effect Effects 0.000 description 1
- 238000013459 approach Methods 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
- 238000012545 processing Methods 0.000 description 1
- 230000026676 system process Effects 0.000 description 1
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 test method and a login test device based on a linux desktop operating system. The calling can write the original input data into the equipment node again according to the input time sequence, so that the automatic login behavior of the operating system and the account password login behavior of the actual tester are indistinguishable. The operation of automatic screen capturing and result detection after the automatic login of the operating system is realized. According to the method, the repeated automatic login test of a single user of the operating system can be realized by only one-time deployment, manual intervention is not needed, the test efficiency can be effectively improved, and the time of a tester is saved. Especially has important significance for the login function fault problem and verification solution effect of the recurrent occurrence.
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 the desktop operating system product, in order to ensure the correctness and stability of the system login function, the situation that the loading of system component icons or customized application icons on the desktop is abnormal in probability after a user logs in the system is avoided, and login test is required to be repeated in the test process. Conventional test tools are mostly run in a graphical system environment where users have 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 yet, and most application software, especially graphic software, operates according to a specific user environment, and no operating condition exists. The current test method for the graphical interface login of the operating system mainly adopts manual password input login, and the correctness of desktop loading is judged manually. Not only does this approach require significant time costs by the tester, but it also does not facilitate the reproduction of sporadic problems and verification solutions.
Disclosure of Invention
In order to solve the problems in the prior art, the invention provides a login test method and device based on a linux desktop operating system, and solves the problems of low manual efficiency and easy error in the existing system login test.
In order to achieve the above object, a first aspect of the present invention provides a login test method based on a linux desktop operating system, including the following steps:
step S1, determining equipment nodes of input equipment;
s2, recording login operation data written into the equipment node when login operation is performed, and generating a login data file according to the login operation data;
s3, recording screen capturing operation data written into the equipment node when the screen capturing operation is performed, and generating a screen capturing data file according to the screen capturing operation data;
step S4, uploading the login data file, the screen capturing data file and a reference picture, wherein the reference picture is a picture when a system component icon or a customized application icon is normally loaded;
s5, rewriting data in the login data file into equipment according to an input time sequence, and automatically logging in;
S6, rewriting data in the screen capturing data file into the equipment according to the input time sequence, automatically capturing a screen and acquiring a screen capturing image;
s7, comparing the screen capturing image with a reference picture and recording a test result;
And S8, repeating the steps S5-S7 until the test times reach a preset threshold value.
Wherein, the step S2 includes:
Step S201, starting the system, and entering a user graphic login interface;
step S202, executing an entering terminal command, inputting an established account password, logging in, and entering a text control console;
Step S203, recording input information of a device node, including: operation type, operation code, operation value, time difference between last operation and current operation;
step S204, switching to a user login graphical interface, and executing account login operation;
Step S205, switching to a text console, stopping recording and storing the recording information as a login data file.
Wherein, the step S3 includes:
step S301, logging in a system, and entering a user graphical interface;
Step S302, recording input information of a device node, including: operation type, operation code, operation value, time difference between last operation and current operation;
Step S303, manually performing screen capturing operation;
And step S304, stopping recording and storing the recording information into a screen capturing data file.
Wherein, the step S1 includes:
s101, checking a per proc/bu/input/device file in a system, and finding corresponding device information of an input device in the per proc/bu/input/device file through a Name field;
step S102, finding a corresponding event value in the value of the Handler field;
And step 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/home/directory, and naming the login data file as autolog.
Step S402, uploading a recorded screen capture data file to a system/home/directory, and naming the screen capture data file as screen capture.
Step S403, modifying the configuration file of the display manager.
Wherein, the step S5 includes:
step S501, detecting whether a user login interface is loaded according to a system log;
step S502, if the loading is not completed beyond the set time limit, ending the test and generating a test failure result, and if the loading is completed within the set time limit, entering step S503;
Step S503, reading and analyzing the login data file;
step S504, writing the data recorded in the login data file into the equipment according to the input time sequence.
Wherein, the step S6 includes:
step S601, judging whether the desktop of the user is loaded completely or not through a system log;
step S602, if the loading is not completed beyond the set time limit, 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 screen capturing data file;
step S604, writing the data recorded in the screen capturing data file into the device according to the input time sequence.
Wherein, the step S7 includes:
step S701, detecting whether a screen capturing image is generated or not;
Step S702, if the screen capturing image exceeds the set time limit and is not successfully generated, ending the test and generating a test failure result, and if the screen capturing image is generated in the set time limit, entering step S703;
Step 703, after detecting the screen capturing image, dividing the screen capturing file according to a predefined application display position;
Step S704, comparing whether the single application display effect after segmentation is consistent with the application display effect in the reference picture one by one;
step S705, record the comparison test result.
The second aspect of the present invention provides a login test device based on a linux desktop operating system, including:
The data recording module is used for recording appointed input equipment information and input data information on the text control console, generating a login data file by recording login operation data written into the equipment node when login operation is performed, and generating a screen capture data file by recording screen capture operation data written into the equipment node when screen capture operation is performed;
the login module is used for reading and analyzing a login data file at the text control console and rewriting data into the equipment file according to an input time sequence;
The screen capturing module is used for reading and analyzing the screen capturing data file at the text control console and rewriting the data into the equipment file according to the input time sequence;
the result detection module is used for comparing the screen capturing image with the reference picture and recording a test result;
the repeated execution module is used for sending a restarting command to the system when the test times do not reach the threshold value, and carrying out the next test;
The system configuration module is used for calling and executing the login module, the screen capturing module, the result detection module and the repeated execution module.
From the above technical solution, the technical solution of the present invention has the following advantages:
according to the login test method and device based on the linux desktop operating system, the input data of the equipment node during the operation of automatic screen capturing and result detection are recorded and stored, and then the stored input data are called, so that the automatic login of the operating system is realized. The calling can write the original input data into the equipment node again according to the input time sequence, so that the automatic login behavior of the operating system and the account password login behavior of the actual tester are indistinguishable. The operation of automatic screen capturing and result detection after the automatic login of the operating system is realized. According to the method, the repeated automatic login test of a single user of the operating system can be realized by only one-time deployment, manual intervention is not needed, the test efficiency can be effectively improved, and the time of a tester is saved. Especially has important significance for the login function fault problem and verification solution effect of the recurrent occurrence.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings that are needed for the description of the embodiments will be briefly described below, it being obvious that the drawings in the following description are only some embodiments of the present invention, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a flowchart of a login test method based on a linux desktop operating system in an embodiment of the present invention;
FIG. 2 is a flowchart showing step S5 in an embodiment of the present invention;
FIG. 3 is a flowchart showing step S6 in an embodiment of the present invention;
FIG. 4 is a flowchart showing step S7 in an embodiment of the present invention;
FIG. 5 is a block diagram of a login test device based on a linux desktop operating system in an embodiment of the present invention;
fig. 6 is a schematic diagram of a login test device based on a linux desktop operating system according to an embodiment of the present invention.
Detailed Description
In order to make the present application better understood by those skilled in the art, the following description will clearly and completely describe the technical solutions in the embodiments of the present application with reference to the accompanying drawings, and it is apparent that the described embodiments are only some embodiments of the present application, not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.
In order to facilitate understanding of the scheme of the invention, a touch notebook computer is taken as an example, and a linux desktop operating system, specifically, a Galaxy kylin desktop operating system is installed in the computer, and simultaneously supports a touch screen, a keyboard, a mouse and the like as input devices. The touch screen is used as an account password input device, and the screen capturing operation key is PtrSc keys in a notebook keyboard. Hereinafter, the Galaxy kylin desktop operating system is simply called as kylin desktop system. Referring to fig. 1, a login test method based on a linux desktop operating system in this embodiment includes:
step S1, determining a device node of the input device. This step aims at finding the corresponding device node in the kylin desktop system of the input device performing the login operation and performing the screen capture operation.
The kylin desktop system inherits the characteristics of an input subsystem in the Linux operating system. The device node is an integral part of the input subsystem. The input subsystem manages the external input devices of the entire kylin desktop system. The input subsystem feeds back the received data to the upper layer application through the device node. When the external input device performs input operation, the input subsystem writes input data into the device node, and then the upper layer application reads and processes the data in the device node, so that interaction with the external input device is realized.
The core of the method for realizing the automatic login of the user account passwords is to simulate the operation of logging in the Galois kylin desktop operating system by using the account passwords by a tester by writing data into equipment nodes.
The step S1 specifically comprises the following steps:
Step S101, checking/proc/bus/input/devices files, and finding corresponding device information of the input devices in the/proc/bus/input/devices files through a Name field.
The/proc/bus/input/devices is a file within the input subsystem into which all device information registered in the operating system kernel is written. The device information in the file includes a Name field and Handlers fields, the Name includes the Name of the device, and the Handlers includes the event value related to the device node.
In this 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
The first part of information belongs to the keyboard device and the second part of information belongs to the touch screen device according to the Name field.
Step S102, finding the corresponding event value in the value of Handlers field. According to Handers fields in the device information, the keyboard device corresponds to event4, and the touch screen corresponds to event8.
Step S103, determining a specific path of the equipment node according to the event value. In the kylin desktop system, the directories of the device nodes are all/dev/input/. The event value corresponding to each device node is a specific file name. According to the judgment that the event value in step S102 can be used, 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 S2, recording login operation data written into the equipment node when the login operation is performed, and generating a login data file according to the login operation data. The step aims at recording input information of a device node corresponding to the touch screen when a tester logs in by using the touch screen.
The step S2 specifically comprises the following steps:
Step S201, starting a kylin desktop system, and entering a user graphic login interface;
Step S202, pressing Ctrl+Alt+F1, inputting the established account password, logging in, and entering a text control console;
Step S203, starting a data recording module, recording/dev/input/event 8 file input information, including: the operation type, the operation code, the operation value, the time difference between the last operation and the current operation and other data;
Step S204, pressing Ctrl+Alt+F7, switching to a user login graphical interface, and manually executing account login operation by using the touch screen device;
step S205, pressing Ctrl+Alt+F1, switching to a text console, stopping the data recording module and storing the recording information as a login data file.
And S3, recording screen capturing operation data written into the equipment node when the screen capturing operation is performed, and generating a screen capturing data file according to the screen capturing operation data. This step is intended to record the input information of the device node corresponding to the keyboard when the tester presses the PtrSc key to perform the screen capturing.
The step S3 specifically comprises the following steps:
Step S301, logging in a kylin desktop system, and entering a user graphical interface;
step S302, starting a data recording module, recording input information of a device node/dev/input/event 4, including: operation type, operation code, operation value, time difference between last operation and current operation;
step S303, pressing PtrSc keys on a keyboard to perform screen capturing operation;
And step S304, stopping the data recording module and storing the recording information into a screen capturing 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 normally loaded. In addition, the configuration file parameters of the display manager are modified to enable the system to simultaneously execute a login module when entering a login interface, the login module executes step S5 when working, and the login module rewrites data in the login data file into the device according to the input time sequence when logging in, so that the account password automatic login of the kylin desktop system is realized.
The step S4 specifically comprises the following steps:
step S401, uploading the recorded login data file to a system/home/directory, and naming the login data file as autolog.
Step S402, uploading the recorded screen capture data file to a system/home/directory, and naming the screen capture data file as screen capture.
Step S403, modifying the configuration file of the display manager. Modifying the configuration file/etc/lightdm/lighttm.conf, setting the greeter-setup-script parameter value in the configuration item [ set: ] in the configuration file as the calling method of the login module, and executing step S5 by calling the login module.
And S5, rewriting the data in the login data file into the equipment according to the input time sequence, and automatically logging in.
Referring to fig. 2, step S5 specifically includes:
step S501, detecting whether a user login interface is loaded according to a system log;
step S502, if the loading is not completed after the timeout, recording a failure test result;
step S503, after loading the user login interface, reading and analyzing login data file autolog. Data;
Step S504, rewriting the data recorded in the login data file into the device according to the input time sequence.
And S6, rewriting data in the screen capturing data file into the equipment according to the input time sequence, automatically capturing the screen and acquiring a screen capturing image. The method aims at enabling a user to automatically call a screen capturing module after logging in a kylin desktop system, reading, analyzing and processing a screen capturing data file, and rewriting data in the screen capturing data file into equipment according to an input time sequence during logging in, so that automatic screen capturing after logging in of the user is achieved.
The method for writing the screen capturing module calling method into the user login self-starting script comprises the following steps: and adding the screen capturing 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 desktop of the user is loaded completely or not through a system log;
Step S602, if the loading is not completed after the timeout, recording a failure test result;
Step S603, after desktop loading is completed, reading and analyzing a screen capture data file screen shot.
Step S604, rewriting the data recorded in the screen capturing data file into the device according to the input time sequence.
And S7, comparing the screen capturing image with a reference picture and recording a test result. The step aims at detecting whether the display of each application in the desktop is correct after the user logs in the kylin desktop system. Referring to fig. 4, step S7 specifically includes:
step S701, detecting whether a screen capturing image is generated or not;
Step S702, if the screen capturing image exceeds the set time limit and is not successfully generated, ending the test and generating a test failure result, and if the screen capturing image is generated in the set time limit, entering step S703;
Step 703, after detecting the screen capturing image, dividing the screen capturing file according to a predefined application display position;
step S704, comparing whether the single application display effect after segmentation is consistent with the application display effect in the reference picture one by one.
And S8, repeating the steps S5-S7 until the test times reach a preset threshold value.
According to 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 capturing and result detection and then calling the stored input data. The calling can write the original input data into the equipment node again according to the input time sequence, so that the automatic login behavior of the operating system and the account password login behavior of the actual tester are indistinguishable. The operation of automatic screen capturing and result detection after the automatic login of the operating system is realized. According to the method, the repeated automatic login test of a single user of the operating system can be realized by only one-time deployment, manual intervention is not needed, the test efficiency can be effectively improved, and the time of a tester is saved. Especially has important significance for the login function fault problem and verification solution effect of the recurrent occurrence.
Referring to fig. 5, the embodiment of the invention further provides a login test device based on the linux desktop operating system, which includes:
The data recording module is used for recording appointed input equipment information and input data information on the text control console, generating a login data file by recording login operation data written into the equipment node when login operation is performed, and generating a screen capture data file by recording screen capture operation data written into the equipment node when screen capture operation is performed;
the login module is used for reading and analyzing a login data file at the text control console and rewriting data into the equipment file according to an input time sequence;
The screen capturing module is used for reading and analyzing the screen capturing data file at the text control console and rewriting the data into the equipment file according to the input time sequence;
the result detection module is used for comparing the screen capturing image with the reference picture and recording a test result;
the repeated execution module is used for sending a restarting command to the system when the test times do not reach the threshold value, and carrying out the next test;
The system configuration module is used for calling and executing the login module, the screen capturing module, the result detection module and the repeated execution module.
The working principle of this embodiment is seen in fig. 6. Firstly starting an operating system, then starting a login interface, executing a user starting script, calling the login module by a system configuration module to the user starting script to execute a working step, rewriting a login data file into an equipment file according to an input time sequence, starting to load a desktop by the system, calling and executing a screen capturing module after loading is completed, reading and analyzing the screen capturing data file by a text control console, rewriting data into the equipment file according to the input time sequence, carrying out screen capturing operation to obtain a screen capturing image, and then dividing the screen capturing image according to an application space position by calling a result detection module and detecting application display effects one by one to obtain a test result. An additional call is defined for the Galaxy kylin 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 re-write the original input data into the equipment node according to the input time sequence, the automatic login behavior of the operating system and the account password login behavior of the actual tester are indistinguishable. Through the system configuration file, the operation of automatic screen capturing and result detection after the automatic login of the operating system is realized. According to the method, the repeated automatic login test of a single user of the operating system can be realized by only one-time deployment, manual intervention is not needed, the test efficiency can be effectively improved, and the time of a tester is saved. Especially has important significance for the login function fault problem and verification solution effect of the recurrent occurrence.
It is to be understood that the above-described embodiments of the present invention are merely illustrative of or explanation of the principles of the present invention and are in no way limiting of the invention. Accordingly, any modification, equivalent replacement, improvement, etc. made without departing from the spirit and scope of the present invention should be included in the scope of the present invention. Furthermore, the appended claims are intended to cover all such changes and modifications that fall within the scope and boundary of the appended claims, or equivalents of such scope and boundary.
Claims (8)
1. A login test method based on a linux desktop operating system is characterized by comprising the following steps:
step S1, determining equipment nodes of input equipment;
s2, recording login operation data written into the equipment node when login operation is performed, and generating a login data file according to the login operation data;
s3, recording screen capturing operation data written into the equipment node when the screen capturing operation is performed, and generating a screen capturing data file according to the screen capturing operation data;
Step S4, uploading the login data file, the screen capturing data file and a reference picture, wherein the reference picture is a picture when a system component icon or a customized application icon is normally loaded; and modifying the display manager profile parameters, modifying the profile/etc/lightdm/lighttm. Conf, and adding the configuration item [ set: The greeter-setup-script parameter value in the ] is set as a calling method of the login module, so that automatic login can be realized during subsequent login;
S5, reading and analyzing the login data file, rewriting data in the login data file into corresponding equipment nodes according to an input time sequence, and performing automatic login;
S6, reading and analyzing the screen capturing data file, rewriting data in the screen capturing data file into corresponding equipment nodes according to an input time sequence, automatically capturing a screen and acquiring a screen capturing image;
Step S7, comparing the screen capturing image with a reference picture and recording a test result, wherein the step comprises the following steps:
step S701, detecting whether a screen capturing image is generated or not;
Step S702, if the screen capturing image exceeds the set time limit and is not successfully generated, ending the test and generating a test failure result, and if the screen capturing image is generated in the set time limit, entering step S703;
Step 703, after detecting the screen capturing image, dividing the screen capturing file according to a predefined application display position;
Step S704, comparing whether the single application display effect after segmentation is consistent with the application display effect in the reference picture one by one;
Step S705, recording a comparison test result;
And S8, repeating the steps S5-S7 until the test times reach a preset threshold value.
2. The login test method based on the linux desktop operating system according to claim 1, wherein the step S2 includes:
Step S201, starting the system, and entering a user graphic login interface;
step S202, executing an entering terminal command, inputting an established account password, logging in, and entering a text control console;
Step S203, recording input information of a device node, including: operation type, operation code, operation value, time difference between last operation and current operation;
step S204, switching to a user login graphical interface, and executing account login operation;
Step S205, switching to a text console, stopping recording and storing the recording information as a login data file.
3. The login test method based on the linux desktop operating system according to claim 1, wherein the step S3 includes:
step S301, logging in a system, and entering a user graphical interface;
Step S302, recording input information of a device node, including: operation type, operation code, operation value, time difference between last operation and current operation;
Step S303, manually performing screen capturing operation;
And step S304, stopping recording and storing the recording information into a screen capturing data file.
4. The login test method based on the linux desktop operating system according to claim 1, wherein the step S1 includes:
S101, checking a per proc/bus/input/device file in a system, and finding corresponding device information of an input device in the per proc/bus/input/device file through a Name field;
step S102, finding a corresponding event value in the value of the Handler field;
And step S103, determining a specific path of the equipment node according to the event value.
5. The login test method based on the linux desktop operating system according to claim 1, wherein the step S4 includes:
Step S401, uploading the recorded login data file to a system/home/directory, and naming the login data file as autolog.
Step S402, uploading a recorded screen capture data file to a system/home/directory, and naming the screen capture data file as screen capture.
Step S403, modifying the configuration file of the display manager.
6. The login test method based on the linux desktop operating system according to claim 1, wherein the step S5 includes:
step S501, detecting whether a user login interface is loaded according to a system log;
step S502, if the loading is not completed beyond the set time limit, ending the test and generating a test failure result, and if the loading is completed within the set time limit, entering step S503;
Step S503, reading and analyzing the login data file;
step S504, writing the data recorded in the login data file into the equipment according to the input time sequence.
7. The login test method based on the linux desktop operating system according to claim 1, wherein the step S6 includes:
step S601, judging whether the desktop of the user is loaded completely or not through a system log;
step S602, if the loading is not completed beyond the set time limit, 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 screen capturing data file;
step S604, writing the data recorded in the screen capturing data file into the device according to the input time sequence.
8. A login test device based on a linux desktop operating system for implementing the method of any one of claims 1-7.
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 CN114153726A (en) | 2022-03-08 |
| CN114153726B true 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 (16)
| 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 |
| 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 |
| 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 |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102495855B (en) * | 2011-11-21 | 2013-09-25 | 奇智软件（北京）有限公司 | Automatic login method and device |
| US10489238B2 (en) * | 2017-10-28 | 2019-11-26 | Facebook, Inc. | Analyzing screenshots to detect application issues |
-
2021
- 2021-11-25 CN CN202111414992.9A patent/CN114153726B/en active Active
Patent Citations (16)
| 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 |
| 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 |
| 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的自生系统设计;赵娜;孔洁;邢家梁;;电脑与信息技术;20191215(06);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114153726A (en) | 2022-03-08 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102736978B (en) | A kind of method and device detecting the installment state of application program | |
| CN106951345B (en) | Consistency test method and device for disk data of virtual machine | |
| US8627296B1 (en) | Unified unit and integration test with automatic mock creation | |
| WO2019161619A1 (en) | Automatic interface test method and apparatus, and device and computer-readable storage medium | |
| US11709591B2 (en) | Flowchart-style diagramming tool to build automated workflows | |
| US8448138B2 (en) | Recording user-driven events within a computing system | |
| CN107608609B (en) | Event object sending method and device | |
| CN111858321A (en) | Xdotool-based automatic testing method | |
| CN108874441B (en) | Board card configuration method, device, server and storage medium | |
| KR20190135337A (en) | Method and system for detecting memory errors | |
| CN104320793A (en) | Mobile phone short message automated test method and system | |
| WO2018049883A1 (en) | File operation method and device | |
| US10318731B2 (en) | Detection system and detection method | |
| US11188449B2 (en) | Automated exception resolution during a software development session based on previous exception encounters | |
| CN102982217A (en) | Processing method and device of screen print | |
| CN110737558A (en) | Method and device for automatically deploying efi shell system to execute test, computer equipment and storage medium | |
| Usman et al. | Test case generation from android mobile applications focusing on context events | |
| CN114153726B (en) | Login test method and device based on linux desktop operating system | |
| CN109491825B (en) | Method, device, storage medium and terminal for positioning abnormal starting problem | |
| CN108009039B (en) | Terminal information recording method, device, storage medium and electronic equipment | |
| WO2022054101A1 (en) | Method and system for automated software accessibility testing | |
| CN111327746B (en) | Method and device for determining pressure abnormity of mobile terminal | |
| US9122551B2 (en) | Methods and systems for generating read-only operating systems | |
| CN111625459A (en) | Application program testing method and device, computer equipment and storage medium | |
| CN110597724A (en) | Calling method and device of application security test component, server and storage medium |
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 |