CN115373771A - Method, system and related device for debugging field data of UI (user interface) - Google Patents
Method, system and related device for debugging field data of UI (user interface) Download PDFInfo
- Publication number
- CN115373771A CN115373771A CN202110551276.9A CN202110551276A CN115373771A CN 115373771 A CN115373771 A CN 115373771A CN 202110551276 A CN202110551276 A CN 202110551276A CN 115373771 A CN115373771 A CN 115373771A
- Authority
- CN
- China
- Prior art keywords
- data
- debugging
- field data
- interface
- source data
- 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.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/451—Execution arrangements for user interfaces
-
- 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/362—Software debugging
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Human Computer Interaction (AREA)
- Stored Programmes (AREA)
Abstract
The application provides a method for debugging field data of a UI (user interface), which comprises the following steps: receiving source data of a UI (user interface), and determining target field data to be debugged in the source data; modifying the data of the target field to generate debugging source data; after a new UI interface is generated by rendering debugging source data, judging whether the new UI interface is abnormal or not; and if so, determining that the target field data is an abnormal field. The method and the device can directly determine the target field data as the abnormal field. The method has the advantages that the metadata does not need to be modified manually, whether the UI interface changes or not does not need to be verified manually, the debugging cost of the UI interface source data can be effectively reduced, and meanwhile, the debugging efficiency is greatly improved. The application also provides a system for debugging the field data of the UI interface, a computer readable storage medium and electronic equipment, which have the beneficial effects.
Description
Technical Field
The present application relates to the field of computers, and in particular, to a method, a system, and a related device for debugging field data of a UI interface.
Background
In the development and debugging process of the mobile terminal, field data of the UI interface often needs to be modified, then the UI interface is prompted to be refreshed, whether the UI interface is abnormal or not is judged, and the method is used for verifying whether adverse effects are generated on the UI interface when the field data change or not. The current debugging process depends on manual field modification, however, when the data of the field of the UI interface is more, the efficiency of manually modifying the field for debugging the UI interface is low, and because the rendering of the UI interface occupies a large amount of time, the efficiency of the debugging process is extremely low.
Disclosure of Invention
The application aims to provide a method for debugging field data of a UI (user interface), a system for debugging field data of the UI, a computer readable storage medium and electronic equipment, which can improve the debugging efficiency of the UI.
In order to solve the technical problem, the application provides a method for debugging field data of a UI interface, and the specific technical scheme is as follows:
receiving source data of a UI (user interface), and determining target field data to be debugged in the source data;
modifying the target field data to generate debugging source data;
after the debugging source data is rendered to generate a new UI (user interface), judging whether the new UI is abnormal or not;
and if so, determining that the target field data is an abnormal field.
Optionally, the determining whether the new UI interface is abnormal includes:
performing picture screenshot on the new UI to obtain a new UI diagram;
and carrying out image analysis on the new UI interface diagram, and judging whether the new UI interface diagram has boundary abnormity.
Optionally, the modifying the target field data and generating the debugging source data includes:
modifying the target field data by adopting a preset modification mode to generate debugging source data; the preset modification mode comprises at least one of character string length change, shaping number change and Boolean value inversion.
Optionally, determining the target field data to be debugged in the source data includes:
determining the debugging sequence of each field data in the source data;
and determining target field data to be debugged in the source data according to the debugging sequence.
Optionally, determining a debugging order of each field data in the source data includes:
performing data structure conversion on the source data to obtain source data in a one-dimensional data format;
determining a parent-child relationship between field data according to the key number relationship chain in the source data in the one-dimensional data format;
and determining the debugging sequence among the field data according to the parent-child relationship.
Optionally, determining the target field data to be debugged in the source data according to the debugging sequence includes:
determining the maximum key number of the modified field data according to the key number relation chain;
and taking unmodified field data corresponding to the minimum key number which is greater than the maximum key number in the debugging sequence as target field data to be debugged in the source data.
Optionally, if there is no exception in the new UI interface, the method further includes:
determining second target field data subsequent to the target field data in the debugging order;
and taking the second target field data as the target field data, returning to execute the step of performing data modification on the target field data and generating debugging source data.
The present application further provides a system for debugging UI field data, including:
the data receiving module is used for receiving source data of a UI (user interface) and determining target field data to be debugged in the source data;
the data modification module is used for modifying the target field data to generate debugging source data;
the abnormity judgment module is used for judging whether the new UI interface is abnormal or not after the new UI interface is generated by rendering the debugging source data;
and the field positioning module is used for determining the target field data as an abnormal field when the judgment result of the abnormal judgment module is yes.
The present application also provides a computer-readable storage medium having stored thereon a computer program which, when being executed by a processor, carries out the steps of the method as described above.
The present application further provides an electronic device, comprising a memory and a processor, wherein the memory stores a computer program, and the processor implements the steps of the method described above when calling the computer program in the memory.
The application provides a method for debugging field data of a UI (user interface), which comprises the following steps: receiving source data of a UI (user interface), and determining target field data to be debugged in the source data; modifying the target field data to generate debugging source data; after the debugging source data is rendered to generate a new UI, judging whether the new UI is abnormal or not; and if yes, determining that the target field data is an abnormal field.
According to the method and the device, after source data of a UI (user interface) are received, target field data to be debugged are determined, the target field data are modified and the UI is debugged, and if the new UI corresponding to the debugging source data is abnormal, the target field data can be directly determined to be an abnormal field. The method has the advantages that the metadata does not need to be modified manually, whether the UI interface changes or not does not need to be verified manually, the debugging cost of the UI interface source data can be effectively reduced, and meanwhile, the debugging efficiency is greatly improved.
The application also provides a debugging system of the UI interface field data, a computer readable storage medium and an electronic device, which have the beneficial effects and are not repeated herein.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, it is obvious that the drawings in the following description are only embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to the provided drawings without creative efforts.
Fig. 1 is a flowchart of a method for debugging field data of a UI interface according to an embodiment of the present disclosure;
fig. 2 is a flowchart of another method for debugging field data of a UI interface according to an embodiment of the present disclosure;
fig. 3 is a schematic structural diagram of a system for debugging field data of a UI interface according to an embodiment of the present disclosure;
fig. 4 is a schematic structural diagram of an electronic device according to an embodiment of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, 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 some embodiments of the present application, but not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
Currently, in the process of developing and debugging the UI interface, debugging and verification need to be performed on field data of the UI interface to determine whether the field data is modified to cause an abnormality of the UI interface, for example, a boundary of the UI interface may be abnormal, or data coverage occurs. However, the current debugging mainly depends on manual modification, manual verification is performed on a UI interface obtained by rendering modified data, little pressure is caused on debugging personnel, and the debugging efficiency is low.
In order to solve the above problems, the present application provides a method for debugging field data of a UI interface, which has the following specific technical scheme:
s101: receiving source data of a UI (user interface), and determining target field data to be debugged in the source data;
the embodiment can be applied to all electronic devices, particularly mobile terminals, which need to perform UI interface debugging, and can be implemented by a server or a third-party terminal device connected with the electronic device containing the UI interface. For convenience of description, the electronic device including the UI interface is hereinafter referred to as a device under test, and the electronic device for performing the present embodiment and subsequent embodiments is referred to as a debugging device. Of course, the connection relationship between the two devices is not limited, and only the devices need to be able to transmit data such as source data.
This step requires first receiving source data of the UI interface. There is no limitation on how to receive the source data of the UI interface. The source data of the UI interface can be received through any feasible communication mode or data transmission mode between the debugging equipment and the tested equipment. In addition, before receiving the source data of the UI interface, a request for sending source data to the device under test may be sent first, and then the source data of the UI interface may be received.
The present embodiment does not limit the specific content of the source data, and may include display data included in the UI interface and data of an application required in the rendering process.
After the source data is obtained, the target field data to be debugged in the source data needs to be determined. As field data are needed to be debugged and verified one by one during debugging, the target field data needed to be verified in the debugging process needs to be determined in the step. In this embodiment, how to determine the target field data is not specifically limited, for example, the target field data to be debugged in the debugging process may be determined according to a preset debugging order, and the debugged field data may also be marked, so as to select the target field data from the field data that does not include the mark.
S102: modifying the target field data to generate debugging source data;
this step is intended to perform data modification on the target field data, thereby generating debug source data. The method for modifying data is not specifically limited, and a preset modification mode may be adopted to modify a field to generate debug source data. The predetermined modification includes, but is not limited to, at least one of a string length change, a reshaped digit change, and a boolean value inversion. For example, if a character string length change is selected, the character string length expansion may be performed on the target field data to test whether the expanded field data will cause the boundary of the UI interface to be out of bounds after rendering. Of course, when data modification is performed, modification may be performed in a combination of multiple ways, for example, data modification may be performed on target field data by simultaneously using string length change and shaping number change.
It is easily understood that the modification in this step is usually a modification to the data parameter of the target field, and those skilled in the art can also adopt other data modification modes for debugging besides the above three modification modes, and shall also fall within the protection scope of the present application.
After the data modification, the obtained debugging source data should have a difference of only one field data compared with the source data received in step S101.
S103: after a new UI interface is generated by rendering debugging source data, judging whether the new UI interface is abnormal or not; if yes, entering S104;
the step aims to judge whether the new UI interface is abnormal or not, and how to render the debugging source data and generate the new UI interface is not particularly limited. Generally speaking, in this step, the debugging device may send the debugging source data to the device under test, and the device under test renders the debugging source data to generate a new UI interface, and then executes the determination process. If the debugging equipment is a server or electronic equipment with a UI interface rendering function, the debugging equipment can directly render according to the debugging source data to obtain a new UI interface, and therefore judgment of whether the new UI interface is abnormal is carried out. Even, the debugging device can send the debugging source data to another verification device which has the same UI rendering conditions and environment as the tested device, so that the UI interfaces corresponding to the source data and the new UI interfaces corresponding to the debugging source data are displayed on the tested device and the verification device respectively, direct comparison between the two UI interfaces is facilitated, and whether the new UI interfaces are abnormal at all can be directly determined.
The method for determining whether the new UI interface is abnormal is not particularly limited, and the new UI interface may be compared with a UI interface corresponding to the source data, or compared with a UI standard interface designed in advance. The comparison between the UI interfaces is not executed, and the new UI interface is subjected to abnormity judgment by using other configured UI interface detection models or applications, and the judgment mode can be used for judging whether the new UI interface is abnormal or not.
S104: and determining the target field data as an abnormal field.
If the new UI interface is abnormal, the target field data can be determined to be an abnormal field, namely, the abnormal field is prompted when the target field data changes, the UI interface is possibly abnormal, for example, the boundary of the UI interface is out of range, the data is covered and the like, so that operation and maintenance personnel can repair the abnormal field conveniently, and the abnormal rate of the UI interface is reduced.
Of course, if the new UI interface is not abnormal, it indicates that the target field data determined in the debugging process has not caused the UI interface to be abnormal. It is easy to understand that the more comprehensive the data modification manner adopted in step S102, the more robust the target field data can be ensured when there is no abnormality in the new UI interface.
According to the method and the device, after the source data of the UI are received, the target field data to be debugged are determined, the target field data are modified and the UI is debugged, and if the new UI corresponding to the debugging source data is abnormal, the target field data can be directly determined to be the abnormal field. The method has the advantages that the metadata does not need to be modified manually, whether the UI interface changes or not does not need to be verified manually, the debugging cost of the UI interface source data can be effectively reduced, and meanwhile, the debugging efficiency is greatly improved.
Based on the foregoing embodiment, as a preferred embodiment, after the new UI interface is generated by rendering the debugging source data, the determining process may include the following steps:
s201: performing picture screenshot on the new UI to obtain a new UI diagram;
s202: and carrying out image analysis on the new UI interface diagram, and judging whether the new UI interface diagram has boundary abnormity.
The present embodiment specifically describes a process of determining whether the new UI interface is abnormal in step S103 in the previous embodiment, and performs screen capture on the debug source data to obtain an interface picture of the new UI interface when determining. And then, carrying out image analysis on the new UI interface diagram, wherein the specific image analysis mode is not limited. For example, the new UI interface diagram may be uploaded to the cloud, and the image analysis may be performed on the new UI interface diagram by using the cloud device, or the new UI interface diagram may be compared with a UI standard interface image of a predetermined design to obtain a corresponding determination result.
Based on the foregoing embodiment, as a preferred embodiment, after receiving source data of a UI interface, the present embodiment further describes how to determine target field data to be debugged in the source data, and the process may include:
s301: determining the debugging sequence of each field data in the source data;
s302: and determining target field data to be debugged in the source data according to the debugging sequence.
That is, the debugging sequence of the field data is determined first, and it should be noted that the debugging sequence does not necessarily need to be configured in real time when determining the target field data to be debugged. Because field data need be debugged one by one in the debugging process, if the debugging sequence is determined in the first debugging process, the debugging sequence determined in the first debugging process can be directly obtained and applied in the subsequent debugging process.
In addition, how to determine the debugging sequence of each field data in the source data is not specifically limited in this embodiment, the debugging sequence may be preset, and it should be ensured that all field data can be debugged no matter what debugging sequence is adopted. Referring to fig. 2, fig. 2 is a flowchart of another method for debugging UI interface field data provided in the embodiment of the present application, at this time, a complete process of the method for debugging UI interface field data provided in the embodiment of the present application is as follows:
firstly, receiving source data of a UI (user interface);
secondly, determining the debugging sequence of each field data in the source data;
thirdly, determining target field data to be debugged in the source data according to the debugging sequence;
fourthly, modifying the data of the target field to generate debugging source data;
fifthly, judging whether the new UI interface is abnormal or not after the new UI interface is generated by rendering the debugging source data; if yes, entering a sixth step;
and sixthly, determining the target field data as an abnormal field.
The following is a preferred procedure for determining the debugging sequence based on the above embodiments, and the specific procedure is as follows:
s3011: performing data structure conversion on the source data to obtain source data in a one-dimensional data format;
after the source data is obtained, because the source data is generally json structure data, which presents a data relationship of a tree structure, in order to determine a debugging sequence, data structure conversion is performed on the source data to obtain the source data in a one-dimensional data format. The one-dimensional data format is not particularly limited, and may be an array, a queue, or the like.
S3012: determining the parent-child relationship among the field data according to a key number relationship chain in the source data in the one-dimensional data format;
in the process of converting to obtain source data in a one-dimensional data format, the key number of each field data in the source data, namely the key value in the KV (key-value) key value pair, can be determined, so that a key number relation chain is determined, which indicates the relation chain of each keyword, thereby defining the parent-child relation between each field data. For example, if a one-dimensional array is used and the obtained one-dimensional array is in the form of a & B & C & D, the parent node of field data D is field data C, the parent node of field data C is field data B, and the parent node of field data B is field data a.
S3013: and determining the debugging sequence among the field data according to the parent-child relationship.
After determining the parent-child relationship, the debugging sequence of the field data can be determined one by one. For example, if the one-dimensional array is a & B & C & D, the debugging order may be a → B → C → D, or D → C → B → a.
Of course, the above is only a process of determining a debugging sequence disclosed in this embodiment, and those skilled in the art may also determine the debugging sequence in other ways based on this embodiment, even define the debugging sequence for field data in the source data by user.
On the basis that the step S301 determines the debugging order of each field data in the source data, the step S302 may include the following steps when determining the target field data to be debugged in the source data according to the debugging order:
s3021: determining the maximum key number of the modified field data according to the key number relation chain;
s3022: and taking the unmodified field data corresponding to the minimum key number which is greater than the maximum key number in the debugging sequence as the target field data to be debugged in the source data.
In addition to the first debugging process, the target field data determined in other subsequent debugging processes are all target field data which are not debugged, when the debugging sequence is determined according to the key number relation chain, the key number which is used as the corresponding target field data can be determined firstly, the unmodified field data which is larger than the minimum key number of the maximum key number and corresponds to the minimum key number is used as the target field data to be debugged, and therefore the selected target field data are determined one by one according to the debugging sequence in the circulating debugging process, the field data are prevented from being omitted, and the integrity of the debugging process is ensured.
In other words, if there is no abnormality in the new UI interface obtained from the debugging source data, the debugging may be performed in a loop thereafter, that is, the second target field data following the target field data in the debugging order is determined, the second target field data is used as the target field data, and the debugging process in steps S102 to S104 is re-executed.
At this time, when debugging is performed for the first time, the corresponding complete execution process of the method for debugging UI field data provided by this embodiment may be as follows:
the method comprises the steps of firstly, receiving source data of a UI interface, and performing data structure conversion on the source data to obtain source data in a one-dimensional data format;
secondly, determining the parent-child relationship among the field data according to a key number relationship chain in the source data in the one-dimensional data format;
thirdly, determining the debugging sequence among the field data according to the parent-child relationship;
fourthly, determining the maximum key number of the modified field data according to the key number relation chain, and taking the unmodified field data corresponding to the minimum key number which is greater than the maximum key number in the debugging sequence as the target field data to be debugged in the source data
Fifthly, modifying the data of the target field to generate debugging source data;
sixthly, after the new UI interface is generated by rendering the debugging source data, judging whether the new UI interface is abnormal or not; if yes, entering a seventh step; if not, entering the eighth step;
and seventhly, determining the target field data as an abnormal field.
And eighthly, determining second target field data behind the target field data in the debugging sequence, taking the second target field data as the target field data, and returning to the fifth step.
The following describes a method for debugging field data of a UI interface provided by the present application with a specific application process of the present application, where a UI interface of an APP on a mobile terminal device is used as a UI interface to be debugged, and the adopted debugging device may be a notebook computer or other terminal devices with a data processing function, and the process may be as follows:
1. a user establishes connection between mobile terminal equipment and debugging equipment;
2. opening an APP by a user, and screenshot and storing an initial UI interface;
3. the method comprises the steps that the debugging equipment is controlled to request the mobile terminal equipment to acquire source data of a UI (user interface), clicking confirmation is carried out on the mobile terminal equipment, and then the debugging equipment receives the source data of the UI;
thereafter, the following debugging process is automatically completed by the debugging equipment.
If the UI interface of the APP is debugged for the first time, the following steps are executed:
determining the debugging sequence of each field data in the source data, and taking the first field data in the debugging sequence as the target field data to be debugged;
performing data modification on the target field data, wherein the data modification comprises but is not limited to character string length change, shaping number change, boolean value inversion and the like, and generating debugging source data after the data modification;
the debugging equipment sends the debugging source data to the mobile terminal equipment, the mobile terminal equipment renders the debugging source data to obtain a new UI interface, and screenshots are stored;
comparing the screenshots of the initial UI interface and the new UI interface, and judging whether the new UI interface is abnormal or not;
if yes, determining that the first field data in the debugging sequence is an abnormal field;
if not, continuing to execute debugging.
If the UI interface of the APP is not debugged for the first time, the following steps are executed:
and determining the maximum key number of the modified field data according to the key number relation chain, and taking the unmodified field data corresponding to the minimum key number which is greater than the maximum key number in the debugging sequence as the target field data.
Performing data modification on the target field data, wherein the data modification comprises but is not limited to character string length change, shaping number change, boolean value inversion and the like, and generating debugging source data after the data modification;
the debugging equipment sends the debugging source data to the mobile terminal equipment, the mobile terminal equipment renders the debugging source data to obtain a new UI interface, and screenshots are stored;
comparing screenshots of the initial UI interface and the new UI interface, and judging whether the new UI interface is abnormal or not;
if yes, determining that the first field data in the debugging sequence is an abnormal field;
and if the target field data does not exist, continuing to execute debugging until the target field data cannot be determined.
When it is determined whether the new UI interface is abnormal, the determination may be performed by using a third-party device or a cloud, which is not described herein.
As can be seen from the above, the user only needs to establish the connection between the mobile terminal device and the debugging device, the debugging process can be automatically executed, the data is not required to be manually modified, whether the UI interface is abnormal or not is manually verified, the debugging automation is realized, and the debugging efficiency of the UI interface is improved.
The following introduces a debugging system of UI field data provided in this embodiment of the application, and the debugging system described below and the debugging method of UI field data described above may be referred to in correspondence with each other.
Referring to fig. 3, fig. 3 is a schematic structural diagram of a system for debugging UI field data according to an embodiment of the present disclosure, and the present disclosure further provides a system for debugging UI field data, including:
the data receiving module 100 is configured to receive source data of a UI interface, and determine target field data to be debugged in the source data;
the data modification module 200 is configured to modify the data of the target field to generate debugging source data;
the exception judgment module 300 is configured to judge whether a new UI interface is abnormal after a new UI interface is generated by rendering the debugging source data;
and a field positioning module 400, configured to determine that the target field data is an abnormal field if the determination result of the abnormality determination module is yes.
Based on the above embodiment, as a preferred embodiment, the abnormality determining module 300 includes:
the screenshot unit is used for carrying out screenshot on the new UI to obtain a new UI diagram;
and the image analysis unit is used for carrying out image analysis on the new UI interface diagram and judging whether the new UI interface diagram has boundary abnormity.
Based on the above embodiment, as a preferred embodiment, the data modification module 200 is a module for performing field modification on target field data in a preset modification manner to generate debugging source data; the preset modification mode comprises at least one of character string length change, shaping number change and Boolean value inversion.
Based on the above embodiment, as a preferred embodiment, the data receiving module 100 includes:
the sequence determining unit is used for determining the debugging sequence of each field data in the source data;
and the field data determining unit is used for determining target field data to be debugged in the source data according to the debugging sequence.
Based on the above-described embodiment, as a preferred embodiment, the order determination unit includes:
the structure conversion subunit is used for carrying out data structure conversion on the source data to obtain source data in a one-dimensional data format;
a parent-child relationship determining subunit, configured to determine a parent-child relationship between each field data according to the key number relationship chain in the source data in the one-dimensional data format;
and the sequence determining unit is used for determining the debugging sequence among the field data according to the parent-child relationship.
Based on the foregoing embodiment, as a preferred embodiment, the field data determining unit is a unit configured to determine a maximum key number of modified field data according to the key number relationship chain, and use unmodified field data corresponding to a minimum key number that is greater than the maximum key number in a debugging order as target field data to be debugged in the source data.
Based on the foregoing embodiment, as a preferred embodiment, if there is no exception in the new UI interface, the method further includes:
the re-debugging module is used for determining second target field data behind the target field data in the debugging sequence; and taking the second target field data as the target field data, and entering the data modification module.
The present application also provides a computer readable storage medium having stored thereon a computer program which, when executed, may implement the steps provided by the above-described embodiments. The storage medium may include: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, an optical disk, or other various media capable of storing program codes.
An electronic device is also provided in the present application, and referring to fig. 4, a structure diagram of an electronic device provided in the embodiment of the present application may include, as shown in fig. 4, a processor 1410 and a memory 1420.
The processor 1410 may include one or more processing cores, such as a 4-core processor, an 8-core processor, and the like. The processor 1410 may be implemented in at least one hardware form of a DSP (Digital Signal Processing), an FPGA (Field-Programmable Gate Array), and a PLA (Programmable Logic Array). The processor 1410 may also include a main processor and a coprocessor, where the main processor is a processor for Processing data in an awake state, and is also called a Central Processing Unit (CPU); a coprocessor is a low power processor for processing data in a standby state. In some embodiments, the processor 1410 may be integrated with a GPU (Graphics Processing Unit) that is responsible for rendering and drawing content that the display screen needs to display. In some embodiments, the processor 1410 may further include an AI (Artificial Intelligence) processor for processing a computing operation related to machine learning.
Memory 1420 may include one or more computer-readable storage media, which may be non-transitory. Memory 1420 may also include high-speed random access memory, as well as non-volatile memory, such as one or more magnetic disk storage devices, flash memory storage devices. In this embodiment, the memory 1420 is at least used for storing the following computer program 1421, wherein after being loaded and executed by the processor 1410, the computer program can implement the relevant steps in the method for debugging the UI interface field data disclosed in any of the foregoing embodiments. In addition, the resources stored by memory 1420 may include, among other things, an operating system 1422 and data 1423, which may be stored as transient or persistent storage. The operating system 1422 may include Windows, linux, android, and the like.
In some embodiments, the electronic device may also include a display 1430, an input-output interface 1440, a communications interface 1450, sensors 1460, a power supply 1470, and a communications bus 1480.
Of course, the structure of the electronic device shown in fig. 4 does not constitute a limitation of the electronic device in the embodiment of the present application, and in practical applications, the electronic device may include more or less components than those shown in fig. 4, or some components may be combined.
The embodiments are described in a progressive manner in the specification, each embodiment focuses on differences from other embodiments, and the same and similar parts among the embodiments are referred to each other. For the system provided by the embodiment, the description is relatively simple because the system corresponds to the method provided by the embodiment, and the relevant points can be referred to the method part for description.
The principles and embodiments of the present application are explained herein using specific examples, which are provided only to help understand the method and the core idea of the present application. It should be noted that, for those skilled in the art, it is possible to make several improvements and modifications to the present application without departing from the principle of the present application, and such improvements and modifications also fall within the scope of the claims of the present application.
It is further noted that, in the present specification, relational terms such as first and second, and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrases "comprising a," "8230," "8230," or "comprising" does not exclude the presence of additional like elements in a process, method, article, or apparatus that comprises the element.
Claims (10)
1. A method for debugging field data of a UI (user interface) is characterized by comprising the following steps:
receiving source data of a UI (user interface), and determining target field data to be debugged in the source data;
modifying the target field data to generate debugging source data;
after the debugging source data is rendered to generate a new UI, judging whether the new UI is abnormal or not;
and if so, determining that the target field data is an abnormal field.
2. The debugging method of claim 1, wherein determining whether the new UI interface has an exception comprises:
performing picture screenshot on the new UI to obtain a new UI diagram;
and carrying out image analysis on the new UI interface diagram, and judging whether the new UI interface diagram has boundary abnormity.
3. The debugging method according to claim 1, wherein the data modifying the target field data and generating the debugging source data comprises:
modifying the target field data by adopting a preset modification mode to generate debugging source data; the preset modification mode comprises at least one of character string length change, shaping number change and Boolean value inversion.
4. The debugging method according to any one of claims 1 to 3, wherein determining target field data to be debugged in the source data comprises:
determining the debugging sequence of each field data in the source data;
and determining target field data to be debugged in the source data according to the debugging sequence.
5. The debugging method of claim 4, wherein determining the debugging order of each field datum in the source datum comprises:
performing data structure conversion on the source data to obtain source data in a one-dimensional data format;
determining a parent-child relationship between each field data according to a key number relationship chain in the source data in the one-dimensional data format;
and determining the debugging sequence among the field data according to the parent-child relationship.
6. The debugging method of claim 5, wherein determining target field data to be debugged in the source data according to the debugging order comprises:
determining the maximum key number of the modified field data according to the key number relation chain;
and taking the unmodified field data corresponding to the minimum key number which is greater than the maximum key number in the debugging sequence as the target field data to be debugged in the source data.
7. The debugging method according to claim 4, wherein if there is no exception in the new UI interface, further comprising:
determining second target field data following the target field data in the debugging order;
and taking the second target field data as the target field data, returning to execute the step of performing data modification on the target field data and generating debugging source data.
8. A system for debugging field data of a UI (user interface), comprising:
the data receiving module is used for receiving source data of a UI (user interface) and determining target field data to be debugged in the source data;
the data modification module is used for modifying the target field data to generate debugging source data;
the abnormity judgment module is used for judging whether the new UI interface is abnormal or not after the new UI interface is generated by rendering the debugging source data;
and the field positioning module is used for determining the target field data as an abnormal field when the judgment result of the abnormal judgment module is yes.
9. A computer-readable storage medium on which a computer program is stored, which computer program, when being executed by a processor, carries out the step of debugging the UI interface field data according to any one of claims 1 to 7.
10. An electronic device comprising a memory in which a computer program is stored and a processor that implements the step of debugging the UI interface field data according to any one of claims 1 to 7 when the processor calls the computer program in the memory.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110551276.9A CN115373771A (en) | 2021-05-20 | 2021-05-20 | Method, system and related device for debugging field data of UI (user interface) |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110551276.9A CN115373771A (en) | 2021-05-20 | 2021-05-20 | Method, system and related device for debugging field data of UI (user interface) |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN115373771A true CN115373771A (en) | 2022-11-22 |
Family
ID=84058504
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110551276.9A Pending CN115373771A (en) | 2021-05-20 | 2021-05-20 | Method, system and related device for debugging field data of UI (user interface) |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115373771A (en) |
-
2021
- 2021-05-20 CN CN202110551276.9A patent/CN115373771A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108959068B (en) | Software interface testing method, device and storage medium | |
| CN107562610B (en) | Method, device, terminal and medium for acquiring page loading time | |
| CN107436844B (en) | Method and device for generating interface use case aggregate | |
| CN108563579B (en) | White box testing method, device and system and storage medium | |
| CN104636254A (en) | Method and device for generating test case, testing method and testing equipment | |
| CN111209203B (en) | Model verification method based on source code | |
| CN112996020B (en) | Bluetooth-based automatic test method and device and Bluetooth test terminal | |
| CN111444103A (en) | Automatic testing method for Web page and related equipment | |
| CN107797922B (en) | Application page testing method, electronic device and electronic equipment | |
| CN112729868A (en) | Vehicle diagnosis method, device, equipment and medium | |
| CN109032612B (en) | Interface calling method and device of hybrid application and computer readable storage medium | |
| CN113821433A (en) | Method, device, equipment, medium and product for testing cloud mobile phone application program | |
| CN113360300A (en) | Interface calling link generation method, device, equipment and readable storage medium | |
| CN112650689A (en) | Test method, test device, electronic equipment and storage medium | |
| CN109522174B (en) | Method, device, terminal and storage medium for controlling adb enabling | |
| CN115373771A (en) | Method, system and related device for debugging field data of UI (user interface) | |
| CN111240972B (en) | Model verification device based on source code | |
| CN113836825A (en) | Application method of key standard and verification chip of neural network processor | |
| CN114091909A (en) | Collaborative development method, system, device and electronic equipment | |
| CN114510421A (en) | Test method, test device, chip and module equipment | |
| CN113064816A (en) | Testing device and testing method for programmable logic device software | |
| CN108170557B (en) | Method and apparatus for outputting information | |
| CN113760631A (en) | Page loading duration determination method, device, equipment and storage medium | |
| CN110704262A (en) | Dynamic service logic debugging method, system, storage medium and intelligent device | |
| CN109271188A (en) | A kind of CPLD upgrade method and relevant apparatus |
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 |