CN113448839B - Application program testing method, device, equipment and storage medium - Google Patents

Application program testing method, device, equipment and storage medium Download PDF

Info

Publication number
CN113448839B
CN113448839B CN202011556235.0A CN202011556235A CN113448839B CN 113448839 B CN113448839 B CN 113448839B CN 202011556235 A CN202011556235 A CN 202011556235A CN 113448839 B CN113448839 B CN 113448839B
Authority
CN
China
Prior art keywords
use case
case
point
current interface
interface
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
Application number
CN202011556235.0A
Other languages
Chinese (zh)
Other versions
CN113448839A (en
Inventor
牛栋
张骞
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Beijing New Oxygen World Wide Technology Consulting Co ltd
Original Assignee
Soyoung Technology Beijing Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Soyoung Technology Beijing Co Ltd filed Critical Soyoung Technology Beijing Co Ltd
Priority to CN202011556235.0A priority Critical patent/CN113448839B/en
Publication of CN113448839A publication Critical patent/CN113448839A/en
Application granted granted Critical
Publication of CN113448839B publication Critical patent/CN113448839B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/36Preventing errors by testing or debugging software
    • G06F11/3668Software testing
    • G06F11/3672Test management
    • G06F11/3684Test management for test design, e.g. generating new test cases
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/07Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/14Error detection or correction of the data by redundancy in operation
    • G06F11/1402Saving, restoring, recovering or retrying
    • G06F11/1446Point-in-time backing up or restoration of persistent data
    • G06F11/1448Management of the data involved in backup or backup restore
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/36Preventing errors by testing or debugging software
    • G06F11/3668Software testing
    • G06F11/3672Test management
    • G06F11/3688Test management for test execution, e.g. scheduling of test suites
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements 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/44Arrangements for executing specific programs
    • G06F9/451Execution arrangements for user interfaces

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Quality & Reliability (AREA)
  • Software Systems (AREA)
  • Computer Hardware Design (AREA)
  • Human Computer Interaction (AREA)
  • User Interface Of Digital Computer (AREA)

Abstract

The application provides an application program testing method, device, equipment and storage medium, wherein the method comprises the following steps: detecting a preset use case switching operation, and displaying a use case grouping list corresponding to a current interface; and refreshing the page content displayed on the current interface into the page content corresponding to the use case point according to the use case point selected by the user from the use case grouping list. According to the method and the device, the case grouping list of each interface is automatically generated according to the test cases, the case grouping list is built in the application program to be tested, and the application program to be tested can be directly called during testing, so that testing is more convenient and quicker. And the return result corresponding to the use case point to be tested is automatically modified in the test process, and the modification can be performed without a packet grabbing tool, so that the test efficiency is improved. And can switch different user roles, different states, etc. without logging in different accounts, and is not influenced by the number of the test devices and the number of the user roles, so that the test efficiency is very high.

Description

Application program testing method, device, equipment and storage medium
Technical Field
The application belongs to the technical field of testing, and particularly relates to an application program testing method, device, equipment and storage medium.
Background
With the development of the mobile internet, many application programs based on different scenes and roles are presented, and the user has high requirements on the use experience of the application programs, so that it is particularly important to test the application programs before the application programs are online.
At present, in the related art, after a tester writes a test case, a developer generates a test program capable of calling the test case by writing the program. And the tester uses the test program to call the test case to test the application program, and modifies the returned result in the test process by means of the packet grabbing tool.
However, in the testing process of the related art, the returned result needs to be modified by a packet grabbing tool, which results in low testing efficiency.
Disclosure of Invention
The application program testing method, device, equipment and storage medium automatically generate the case grouping list of each interface according to the test cases, and the case grouping list is built in the application program to be tested, so that the application program can be directly called during testing, and the testing is more convenient and faster. And the return result corresponding to the use case point to be tested is automatically modified in the test process, and the modification can be performed without a packet grabbing tool, so that the test efficiency is improved.
An embodiment of a first aspect of the present application provides an application program testing method, including:
detecting a preset use case switching operation, and displaying a use case grouping list corresponding to a current interface, wherein the use case grouping list comprises one or more use case points in the current interface;
and refreshing the page content displayed on the current interface into the page content corresponding to the use case point according to the use case point selected by the user from the use case grouping list.
In some embodiments of the present application, before detecting the preset case switching operation and displaying the case grouping list corresponding to the current interface, the method further includes:
acquiring a test case of an application program to be tested;
generating a case grouping list corresponding to each interface in the application program to be tested according to the test cases;
and the application case grouping list corresponding to each interface is built in the application program to be tested.
In some embodiments of the present application, the generating, according to the test case, a case grouping list corresponding to each interface in the application to be tested includes:
acquiring case name information of each case point in a first interface from the test case, wherein the first interface is any interface in the application program to be tested;
Respectively allocating identifiers for the use case points;
and generating an application grouping list corresponding to the first interface according to the application name information and the identifier of each application point.
In some embodiments of the present application, the use case name information includes a use case name of a use case point and a function name of a function point to which the use case point belongs;
acquiring case name information of each case point in a first interface from the test case; according to the case name information and the identifier of each case point, generating a case grouping list corresponding to the first interface, including:
acquiring the function name of each function point included in the first interface from the test case and the case name of each case point;
and generating a case grouping list corresponding to the first interface according to the function name of each function point, the case name and the identifier of each case point.
In some embodiments of the present application, the refreshing, according to a use case point selected by a user from the use case group list, page content displayed on the current interface to page content corresponding to the use case point includes:
modifying an identification field of the current interface according to a use case point selected by a user from the use case grouping list;
And refreshing the page content displayed by the current interface into the page content corresponding to the use case point according to the modified identification field.
In some embodiments of the present application, the modifying, according to a use case point selected by a user from the use case group list, an identification field of the current interface includes:
acquiring the use case name of the use case point selected by the user from the use case grouping list;
acquiring an identifier corresponding to the use case point according to the use case name;
judging whether the use case point is a multi-event use case point, if not, modifying the value of the identification field of the current interface into the acquired identifier;
if yes, converting a plurality of event identifications in the identifier into a character string, and modifying the value of the identification field of the current interface into the character string.
In some embodiments of the present application, refreshing, according to the modified identification field, the page content displayed on the current interface to the page content corresponding to the use case point includes:
acquiring source data corresponding to the use case point according to the modified identification field;
and refreshing the page content displayed by the current interface into the page content corresponding to the use case point according to the source data corresponding to the use case point.
In some embodiments of the present application, the detecting the preset case switching operation, displaying the case grouping list corresponding to the current interface, includes:
detecting a preset gesture operation, and displaying an application grouping list corresponding to a current interface, wherein the preset gesture operation comprises a shaking operation or a sliding operation; or,
and detecting clicking operation of a preset suspension key for switching use cases, and displaying a use case grouping list corresponding to the current interface.
In some embodiments of the present application, the use case grouping list includes role use case points corresponding to different user roles, and further includes:
detecting that the role case point is clicked, and acquiring source data of a home page corresponding to the clicked role case point;
and jumping to the home page corresponding to the role use case point from the current interface according to the source data of the home page.
In some embodiments of the present application, after refreshing the page content displayed on the current interface to the page content corresponding to the use case point, the method further includes:
detecting a reset instruction triggered by a preset reset key, and resetting the value of the identification field to be a value before modification;
acquiring source data corresponding to page content before page refreshing according to the reset identification field;
And refreshing the page content displayed by the current interface into the previous page content according to the acquired source data.
An embodiment of a second aspect of the present application provides an application program testing apparatus, including:
the list display module is used for detecting a preset case switching operation and displaying a case grouping list corresponding to a current interface, wherein the case grouping list comprises one or more case points in the current interface;
and the page refreshing module is used for refreshing the page content displayed on the current interface into the page content corresponding to the use case point according to the use case point selected by the user from the use case grouping list.
An embodiment of a third aspect of the present application provides an electronic device, including a memory, a processor, and a computer program stored on the memory and executable on the processor, the processor executing the computer program to implement the method of the first aspect.
An embodiment of the fourth aspect of the present application provides a computer readable storage medium having stored thereon a computer program for execution by a processor to implement the method of the first aspect.
The technical scheme provided in the embodiment of the application has at least the following technical effects or advantages:
In the embodiment of the application, the application case grouping list corresponding to each interface is automatically generated according to the test cases of the application program to be tested, the application case grouping list corresponding to each interface is built in the application program to be tested, the application case grouping list can be directly called during testing, a developer does not need to write an extra calling program to call the test cases from the outside of the application program to be tested, the testing is more convenient and quick, and the testing efficiency is improved. And the identification field of the current interface is automatically modified in the test process, so that the return result corresponding to the use case point to be tested is automatically modified, the modification can be performed without a packet grabbing tool, and the test efficiency is further improved. And in the testing process, different user roles, different states and the like can be switched without logging in different accounts, so that the testing of the application program is not influenced by the number of the testing devices and the number of the user roles, and the testing efficiency is improved.
Additional aspects and advantages of the application will be set forth in part in the description which follows and, in part, will be obvious from the description, or may be learned by practice of the application.
Drawings
Various other advantages and benefits will become apparent to those of ordinary skill in the art upon reading the following detailed description of the preferred embodiments. The drawings are only for purposes of illustrating the preferred embodiments and are not to be construed as limiting the application. Also, like reference numerals are used to designate like parts throughout the figures. In the drawings:
FIG. 1 is a flow chart of an application testing method according to an embodiment of the present application;
FIG. 2 is a schematic diagram of triggering display of a list of use case groupings of a current interface by a pan-tilt manner according to an embodiment of the present application;
FIG. 3 is a schematic diagram of triggering display of a user group list of a current interface by sliding a screen according to an embodiment of the present application;
FIG. 4 is a schematic diagram of a user grouping list for displaying a current interface through hover key triggering according to an embodiment of the present application;
FIG. 5 is a schematic diagram illustrating an interface of a switching case point according to an embodiment of the present disclosure;
FIG. 6 is a schematic diagram of an interface for switching user roles according to an embodiment of the present application;
FIG. 7 is a schematic structural diagram of an application testing apparatus according to an embodiment of the present application;
FIG. 8 is a schematic structural diagram of an electronic device according to an embodiment of the present disclosure;
fig. 9 shows a schematic diagram of a storage medium according to an embodiment of the present application.
Detailed Description
Exemplary embodiments of the present application will be described in more detail below with reference to the accompanying drawings. While exemplary embodiments of the present application are shown in the drawings, it should be understood that the present application may be embodied in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.
It is noted that unless otherwise indicated, technical or scientific terms used herein should be given the ordinary meaning as understood by one of ordinary skill in the art to which this application belongs.
An application program testing method, device, equipment and storage medium according to an embodiment of the application program are described below with reference to the accompanying drawings.
At present, in order to meet various demands of life and work of people, many application programs based on different scenes and roles are presented, and the application programs need to be tested before being online. In the related art, a tester writes a test case according to a requirement document of an application program, and a developer forms a test program capable of calling the test case by writing the program. And the tester uses the test program to call the test case to test the application program, and modifies the returned result in the test process by means of the packet grabbing tool. However, in the related art, a developer needs to write a test program capable of calling a test case, and the returned result needs to be modified by means of a packet grabbing tool, so that the test period is prolonged, and the test efficiency is low.
The embodiment of the application program testing method can automatically generate the application case grouping list corresponding to each interface in the application program to be tested according to the test cases of the application program to be tested, and the application case grouping list corresponding to each interface is built in the application program to be tested, so that the application case grouping list can be directly called from the application program to be tested in the process of testing the application program to be tested, a developer does not need to write an extra calling program to call the test cases from the outside of the application program to be tested, the calling of the application cases is more convenient and quick, and the testing efficiency is improved. And in the test process, the value of the identification field of the current interface is automatically modified into the identifier corresponding to the user-selected use case point according to the user-selected use case point, and the page content displayed on the current interface is refreshed according to the modified identification field, so that the return result corresponding to the use case point to be tested is automatically modified, the modification can be performed without a packet grabbing tool, and the test efficiency is further improved.
Before an application program to be tested is tested by the method provided by the embodiment of the application program testing method, a tester refers to a requirement document of the application program to be tested to write a test case. The method comprises the steps of importing test cases into the terminal for testing the application program, and then generating an application case grouping list corresponding to each interface in the application program to be tested through the following operations:
acquiring a test case of an application program to be tested; according to the test case, generating a case grouping list corresponding to each interface in the application program to be tested, wherein the case grouping list comprises the function name of each function point in the interface and the case name of each case point corresponding to the function point; and the application case grouping list corresponding to each interface is built in the application program to be tested.
For any interface in the application program to be tested, which is referred to as a first interface in the embodiment of the present application, the generating an application case grouping list corresponding to the first interface specifically includes:
acquiring case name information of each case point in the first interface from the test case; respectively allocating an identifier for each use case point, wherein the identifier is used for uniquely identifying the use case point; and generating a case grouping list corresponding to the first interface according to the case name information and the identifier of each case point.
The case name information comprises the case name of the case point and the function name of the function point to which the case point belongs. Specifically, acquiring a function name of each function point and a case name of each case point included in a first interface from a test case; and generating a use case grouping list corresponding to the first interface according to the function name of each function point, the use case name and the identifier of each use case point.
The test case comprises names of function modules included in each interface of the application program to be tested, the function modules in one interface are hierarchical, and each father function module may also comprise one or more sub-function modules. And acquiring the function name of the father function module in the first interface from the test case, and acquiring the function name of each sub function module included in the father function module. The obtained function name of the father function module is determined to be the function name of each function point included in the first interface, and the function name of each sub function module is determined to be the use case name of each use case point included in the first interface.
And generating a random number for each use case point through a random number generator, and taking the generated random number as an identifier corresponding to the use case point. Or, according to the number of the case points included in the function point, an identifier is allocated to the case point included in the function point in a numerical increasing manner. For example, the function point "chat function" includes two use case points "voice chat function" and "video chat function", and the identifier corresponding to the use case point "voice chat function" may be 1, and the identifier corresponding to the use case point "video chat function" may be 2.
And generating a use case grouping list corresponding to the first interface according to the function name of each function point, the use case name and the identifier of each use case point, wherein the use case grouping list comprises the function name of each function point and the use case name of each use case point in the first interface. And for each interface included in the application program to be tested, respectively generating an application case grouping list corresponding to each interface according to the mode, and then storing the application case grouping list corresponding to each interface in a memory corresponding to the application program to be tested.
Specifically, a key-value form data storage structure, such as a linked list or a hash map, is created in the memory corresponding to the application program to be tested. For the list of application case packets corresponding to each interface, the name activity. And taking an instance point instance List < TypeData > corresponding to the interface as a value, and defining an identifier type, an instance name and an instance class isTitle corresponding to each instance point in the instance data TypeData of the instance point instance List < TypeData > for each instance point included in the interface. The use case level isTitle is used for indicating whether the use case point is a parent use case or a child use case, for example, the use case point chat function includes a use case point video chat function and a voice chat function, and the use case level of the use case point chat function is a parent level, and the use case point video chat function and the voice chat function are child levels.
After the application case grouping list corresponding to each interface is assembled into the key-value form in the above manner, the application case grouping list corresponding to each interface is added into the created data storage structure, and then the application program to be tested is built in the application program to be tested. After the application program to be tested is built with the application case grouping list corresponding to each interface, as shown in fig. 1, the test is performed through the following steps:
step 101: detecting a preset case switching operation, and displaying a case grouping list corresponding to the current interface, wherein the case grouping list comprises one or more case points in the current interface.
In the process of testing the application program to be tested, a user needs to browse each interface in the application program to be tested to determine whether the display effect and the functional logic of each interface are problematic. In the process of user testing, detecting whether a preset case switching operation exists in real time, wherein the preset case switching operation can comprise a preset gesture operation or a click operation of a preset suspension key. The preset gesture operation may include a shake operation or a slide operation, where the shake operation may be an operation of shaking a terminal for testing an application or sliding a screen on a screen of the terminal according to a preset direction, and the preset direction may be from bottom to top, from top to bottom, from left to right, or from right to left, etc.
In some embodiments of the present application, if a preset gesture operation is detected, for example, a pan-tilt operation or a screen sliding operation is detected, a use case grouping list corresponding to a current interface is obtained from a memory corresponding to an application to be tested, and the use case grouping list corresponding to the current interface is displayed in a pop-up box form.
In other embodiments of the present application, if a click operation of a preset suspension key for switching use cases is detected, a use case grouping list corresponding to a current interface is obtained from a memory corresponding to an application program to be tested, and the use case grouping list corresponding to the current interface is displayed in a pop-up box form.
Specifically, when a preset gesture operation or a click operation of a preset hover key is detected, the data storage structure created in the local memory is loaded with MapList data by using the recurview. Acquiring the name of the current interface, traversing the key of the mapList, transmitting the name of the current interface through the activity.
And displaying an example grouping list corresponding to the current interface, wherein the example grouping list comprises the function name of each function point in the current interface and the example name of each example point contained in each function point. Fig. 2 shows a schematic diagram of triggering a display use case group list by a pan-tilt operation. Fig. 3 shows a schematic diagram of triggering a display use case group list by sliding a screen from bottom to top. Fig. 4 shows a schematic diagram of triggering a display case grouping list by a preset hover key.
Step 102: and refreshing the page content displayed on the current interface into the page content corresponding to the use case point according to the use case point selected by the user from the use case grouping list.
After displaying the case grouping list of the current interface through the operation of step 101, the user may select the case point to be tested from the displayed case grouping list through a click operation, and may select the case point singly or multiple. When the user clicking the case point is detected, the case name of the case point selected by the user is obtained from the displayed case grouping list. And acquiring the corresponding identifier from the case grouping list according to the case name.
Then, whether the use case point is a multi-event use case point is judged, the use case point can be divided into a single-event use case point and a multi-event use case point, the single-event use case point only comprises one use case event, and the multi-event use case point comprises a plurality of use case events. For example, the use case points for user authentication include three use case events of authentication success, authentication failure and abnormality at the same time.
For the single event case point, the corresponding identifier is the final value, and the value of the identification field of the current interface can be directly modified into the acquired identifier. For the multi-event case point, the corresponding identifier includes the event identifier corresponding to each case event included in the case point, and it is necessary to convert multiple event identifiers in the identifier into a character string, and then modify the value of the identification field of the current interface into the character string.
The value of the identification field of the current interface is the identifier of the application point corresponding to the page content displayed by the current interface. And modifying the identifier corresponding to the page content displayed on the current interface into the identifier corresponding to the use case point selected by the user, so that the identification field is automatically modified, the modification can be realized without adopting a packet grabbing tool, and the test efficiency is improved.
And finally, refreshing the page content displayed on the current interface into the page content corresponding to the use case point according to the modified identification field. Specifically, according to the modified identification field, source data corresponding to the use case point is obtained; and refreshing the page content displayed on the current interface into the page content corresponding to the use case point according to the source data corresponding to the use case point.
And modifying the identification field of the current interface into a character string converted from event identifications of a plurality of case events for the multi-event case point, and displaying page contents corresponding to each case event in the case point by the current interface after refreshing the interface.
The test is performed before the application to be tested is brought on line, and the source data of the application to be tested is locally set. After the identification field of the current interface is automatically modified through the operation of step 102, the source data corresponding to the identification field is obtained from the local according to the value of the modified identification field, and the obtained source data is the source data corresponding to the use case point selected by the user. And carrying out page rendering according to the source data, and refreshing the page content displayed on the current interface into the page content corresponding to the use case point selected by the user.
As shown in fig. 5, the preset hover key in the (a) diagram triggers and displays the use case grouping list in the (b), and if the user clicks the use case point "video+chat" in the use case grouping list, the current interface refreshes and displays the page content corresponding to the use case point "video+chat", that is, the page content displayed in the (c) diagram, where the bottom of the page has two keys of "video facial diagnosis" and "chat".
In other embodiments of the present application, the use case grouping list of each interface may further include role use case points corresponding to different user roles in the application to be tested. For example, for an application to be tested in the medical field, the user roles may include doctor and patient, and the role use case point "doctor" and "patient" may be included in the use case group list.
If the user needs to switch the user roles to test the functions of other user roles, the user can click on the role use case point in the use case grouping list. When the clicked role case point is detected, the case name of the clicked role case point is obtained from the case grouping list displayed currently, and an identifier corresponding to the case name is obtained. And acquiring the source data of the top page corresponding to the identifier from the source data of the local application program to be tested according to the acquired identifier. And obtaining the source data of the home page corresponding to the clicked role use case point, and jumping to the home page corresponding to the role use case point from the current interface according to the source data of the home page.
As shown in fig. 6, the use case navigation list displayed on the current interface in the (a) diagram includes a role use case point "doctor" and a role use case point "patient", and if the user clicks the role use case point "patient", the first page corresponding to the patient in the (B) diagram is displayed in a skip mode.
Because the role case points are set in the case grouping list corresponding to each interface, when a user wants to switch roles, the user can directly trigger the case grouping list of the current interface by shaking a screen, sliding a screen or clicking a preset suspension key, and then click the role case point in the case grouping list, so that the user can directly jump to the first page corresponding to the role case point, and the function of the role case point can be tested. Therefore, different user roles can be switched without exiting the current account, multi-role switching in a short time is realized, and the testing efficiency is improved.
Because some function modules have multiple states, such as authentication functions including authentication success, authentication failure, abnormality and the like, payment functions including payment success, payment failure, network abnormality and the like. In order to conveniently switch multiple states of the functional module, other embodiments of the present application further set use case points of different states, which are included in the functional points, in the use case group list of the interface. For example, the use case group list in fig. 5 (b) includes function points "authenticated and unauthenticated, abnormal state", which include three state use case points of "authenticated homepage function", "unauthenticated homepage function", and "abnormal homepage box".
After displaying the case grouping list corresponding to the current interface in step 101, if the user needs to switch different states of a certain function point, the user may click on a state case point included in the function point in the case grouping list. When the state case point is detected to be clicked, the case name of the clicked state case point is obtained from the case grouping list displayed currently, and an identifier corresponding to the case name is obtained. And acquiring the source data corresponding to the identifier from the source data of the local application program to be tested according to the acquired identifier. And acquiring the source data corresponding to the clicked state case point, and refreshing the page content displayed on the current interface into the page content corresponding to the clicked state case point according to the source data.
Because the state case points are set in the case grouping list corresponding to the interface, when a user wants to switch different states of the function points, the user can directly trigger the case grouping list of the current interface by shaking a screen, sliding the screen or clicking a preset suspension key, and then click the state case points in the case grouping list, so that page contents corresponding to the state case points to be tested are refreshed, the state case points are tested, multi-state switching in a short time is realized, and the test efficiency is improved.
In other embodiments of the present application, after clicking a certain case point in the case grouping list to refresh the page content displayed by the current interface, the user may need to return to viewing the previous page content, and the user may trigger displaying the case grouping list of the current interface by shaking a screen, sliding a screen, or clicking a preset hover key, and then click the corresponding case point of the previous page content in the case grouping list, so that the current interface refreshes the page again to display the previous page content. However, since the previous page content may correspond to one or more use case points, the user reselects the previous use case point is cumbersome and error-prone.
In order to improve efficiency of returning to view of the page content before and to avoid returning to view errors, the embodiment of the present application also sets a reset key in a pop-up box for displaying the use case group list, such as the key "reset" shown in (b) in fig. 5. When the user needs to return to viewing the previous page content, the user triggers the user case grouping list of the current interface to be displayed by shaking a screen, sliding a screen or clicking a preset hover key, and then clicks a reset key set in a pop-up box. And when a reset instruction triggered by a preset reset key is detected, resetting the value of the identification field of the current interface to a value before modification, namely resetting the value to the identifier of the application case point corresponding to the page content displayed before page refreshing. And acquiring source data corresponding to the page content before page refreshing according to the reset identification field. And refreshing the page content displayed by the current interface into the previous page content according to the acquired source data.
In the embodiment of the application, in order to avoid confusion of source data of an application program caused by data modification in the test process, the source data of the application program is backed up before the application program test is performed. The application program testing process of the embodiment of the application program is carried out on the basis of the backup source data.
However, when the user switches the use case point in step 102, the identification field of the current interface is modified, and the source data of the backup is different from the original source data of the application program after the modification. In order to avoid data confusion and ensure data consistency, when the identification field of the current interface is reset, the source data corresponding to the page content before page refreshing is acquired from the original source data of the application program according to the reset identification field. That is, in step 102, source data corresponding to the use case point selected by the user is obtained from the backed up source data, and in the resetting operation, source data corresponding to the page content before the page refresh is obtained from the original source data.
In other embodiments of the present application, to avoid data confusion and ensure data consistency, the identification field of the current interface may be restored to the value before the switch after each switch of the use case point. Therefore, the backup source data corresponding to the application program can be ensured not to be changed, and when the identification field of the current interface is reset, the source data corresponding to the page content before page refreshing can be obtained from the backup source data of the application program according to the identification field after the reset. That is, in step 102, source data corresponding to the use case point selected by the user is obtained from the backed up source data, and the reset operation is also to obtain source data corresponding to the page content before the page refresh from the backed up source data.
For example, assuming that the value of the identification field of the current interface is 001 and the value of the identifier of the use case point selected by the user is 002, the value of the identification field of the current interface is modified to 002, and the content of the current interface is refreshed to the page content corresponding to the use case point selected by the user, namely, the page content corresponding to 002 according to the identification field 002. After the user-selected use case point is tested, the value of the identification field of the current interface can be restored to 001 before the user-selected use case point is tested, and the backup source data corresponding to the application program is ensured not to be changed.
The application program testing method provided by the embodiment of the application program testing method can be suitable for any program testing scene, and four application scenes are given below by way of example. Firstly, program developers perform self-test on a page, functional logic and the like which are preliminarily developed; secondly, before the application program is on line, testing pages, functional logic and the like corresponding to each user role according to the test cases; thirdly, performing product acceptance test on the application program; fourth, interactive walkthrough is performed on the UI (User Interface) of the application.
The method provided by the embodiment of the application can be applied to a debugging environment and an online environment. The current running environment is a debugging environment or an online environment is indicated by a preset field for identifying the running environment. For example, the field for identifying the running environment may be issuppusecase, and if the value of the field issuppusecase is set to true, it indicates that the running environment is a debug environment, and supports use of the local test case. If the value of issuppUseCAse is set to false, it indicates that the running environment is an online environment.
For a debug environment, the source data of the application to be tested is locally set. In the online environment, source data of an application program to be tested is stored in a server, and the source data corresponding to an example point is required to be obtained from the server in the test process. In the embodiment of the present application, whether the source data is acquired is indicated by a preset field for identifying whether the source data is already acquired, for example, the field may be isAlreadyGetData, where a value of true indicates that the source data is already acquired, and a value of false indicates that the source data is not acquired.
In the testing process by the method provided by the embodiment of the application, after a user clicks a certain use case point, the identification field of the current interface is modified into the identifier corresponding to the clicked use case point, and corresponding source data is obtained according to the identifier. And if the current running environment is a debugging environment, locally acquiring the source data corresponding to the identifier. And if the current running environment is an online environment, acquiring source data corresponding to the identifier from a server. After the source data corresponding to the identifier is acquired, the field isAlreadyGetData is assigned as true. When the running environment is an online environment and the subsequent user clicks the use case point again, the source data corresponding to the use case point is determined to be obtained before according to the assignment of the field isalreadyGetData as true, so that the source data corresponding to the use case point obtained before is directly utilized, the acquisition from the server is not repeated, the data difference caused by frequently and manually triggering the use case point to request a network is avoided, and meanwhile, the cost of the server is saved.
In the embodiment of the application, the application case grouping list corresponding to each interface is automatically generated according to the test cases of the application program to be tested, the application case grouping list corresponding to each interface is built in the application program to be tested, the application case grouping list can be directly called during testing, a developer does not need to write an extra calling program to call the test cases from the outside of the application program to be tested, the testing is more convenient and quick, and the testing efficiency is improved. And the identification field of the current interface is automatically modified in the test process, so that the return result corresponding to the use case point to be tested is automatically modified, the modification can be performed without a packet grabbing tool, and the test efficiency is further improved. And in the testing process, different user roles, different states and the like can be switched without logging in different accounts, so that the testing of the application program is not influenced by the number of the testing devices and the number of the user roles, and the testing efficiency is improved.
The embodiment of the application also provides an application program testing device, which is used for executing the application program testing method described in any one of the embodiments, referring to fig. 7, and the device includes:
the list display module 701 is configured to detect a preset case switching operation, and display a case grouping list corresponding to the current interface, where the case grouping list includes one or more case points in the current interface;
And the page refreshing module 702 is configured to refresh the page content displayed on the current interface to the page content corresponding to the use case point according to the use case point selected by the user from the use case group list.
The apparatus further comprises: the case grouping list generation module is used for acquiring test cases of the application program to be tested; generating an application case grouping list corresponding to each interface in the application program to be tested according to the test cases; and the application case grouping list corresponding to each interface is built in the application program to be tested.
The case grouping list generation module is specifically configured to obtain case name information of each case point in a first interface from a test case, where the first interface is any interface in an application to be tested; respectively allocating identifiers to each use case point; and generating a case grouping list corresponding to the first interface according to the case name information and the identifier of each case point.
The case name information comprises the case name of the case point and the function name of the function point to which the case point belongs; the use case grouping list generation module is specifically used for acquiring the function name of each function point in the first interface and the use case name of each use case point from the test use cases; and generating a use case grouping list corresponding to the first interface according to the function name of each function point, the use case name and the identifier of each use case point.
The page refreshing module 702 is configured to modify an identification field of the current interface according to a use case point selected by a user from the use case group list; and refreshing the page content displayed on the current interface into the page content corresponding to the use case point according to the modified identification field.
The page refreshing module 702 is specifically configured to obtain, from the use case grouping list, a use case name of a use case point selected by a user; acquiring an identifier corresponding to the use case point according to the use case name; judging whether the use case point is a multi-event use case point, if not, modifying the value of the identification field of the current interface into the acquired identifier; if so, converting a plurality of event identifications in the identifier into a character string, and modifying the value of the identification field of the current interface into the character string.
The page refreshing module 702 is configured to obtain source data corresponding to the use case point according to the modified identification field; and refreshing the page content displayed on the current interface into the page content corresponding to the use case point according to the source data corresponding to the use case point.
The list display module 701 is configured to detect a preset gesture operation, and display an application grouping list corresponding to a current interface, where the preset gesture operation includes a shake operation or a slide operation; or detecting clicking operation of a preset suspension key for switching the use cases, and displaying a use case grouping list corresponding to the current interface.
In this embodiment of the present application, the use case group list includes role use case points corresponding to different user roles, and the apparatus further includes: the role switching module is used for detecting that the role case point is clicked and acquiring source data of a home page corresponding to the clicked role case point; and according to the source data of the home page, jumping from the current interface to the home page corresponding to the role use case point.
The apparatus further comprises: the reset module is used for detecting a reset instruction triggered by a preset reset key and resetting the value of the identification field to a value before modification; acquiring source data corresponding to page content before page refreshing according to the reset identification field; and refreshing the page content displayed by the current interface into the previous page content according to the acquired source data.
The application program testing device provided by the above embodiment of the present application and the application program testing method provided by the embodiment of the present application have the same beneficial effects as the method adopted, operated or implemented by the application program stored therein, because of the same inventive concept.
The embodiment of the application also provides the electronic equipment for executing the application program testing method. Referring to fig. 8, a schematic diagram of an electronic device according to some embodiments of the present application is shown. As shown in fig. 8, the electronic device 8 includes: a processor 800, a memory 801, a bus 802 and a communication interface 803, the processor 800, the communication interface 803 and the memory 801 being connected by the bus 802; the memory 801 stores a computer program executable on the processor 800, and the processor 800 executes the application program test method according to any one of the foregoing embodiments of the present application when the computer program is executed.
The memory 801 may include a high-speed random access memory (RAM: random Access Memory), and may further include a non-volatile memory (non-volatile memory), such as at least one magnetic disk memory. The communication connection between the system network element and at least one other network element is implemented via at least one communication interface 803 (which may be wired or wireless), the internet, a wide area network, a local network, a metropolitan area network, etc. may be used.
Bus 802 may be an ISA bus, a PCI bus, or an EISA bus, among others. The buses may be classified as address buses, data buses, control buses, etc. The memory 801 is configured to store a program, and the processor 800 executes the program after receiving an execution instruction, and the application program testing method disclosed in any of the foregoing embodiments of the present application may be applied to the processor 800 or implemented by the processor 800.
The processor 800 may be an integrated circuit chip with signal processing capabilities. In implementation, the steps of the methods described above may be performed by integrated logic circuitry in hardware or instructions in software in processor 800. The processor 800 may be a general-purpose processor, including a central processing unit (Central Processing Unit, CPU for short), a network processor (Network Processor, NP for short), etc.; but may also be a Digital Signal Processor (DSP), application Specific Integrated Circuit (ASIC), an off-the-shelf programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components. The disclosed methods, steps, and logic blocks in the embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of a method disclosed in connection with the embodiments of the present application may be embodied directly in hardware, in a decoded processor, or in a combination of hardware and software modules in a decoded processor. The software modules may be located in a random access memory, flash memory, read only memory, programmable read only memory, or electrically erasable programmable memory, registers, etc. as well known in the art. The storage medium is located in the memory 801, and the processor 800 reads information in the memory 801 and performs the steps of the above method in combination with its hardware.
The electronic device provided by the embodiment of the application and the application testing method provided by the embodiment of the application are the same in inventive concept, and have the same beneficial effects as the method adopted, operated or implemented by the electronic device.
The present embodiment also provides a computer readable storage medium corresponding to the application program testing method provided in the foregoing embodiment, referring to fig. 9, the computer readable storage medium is shown as an optical disc 30, on which a computer program (i.e. a program product) is stored, where the computer program, when executed by a processor, performs the application program testing method provided in any of the foregoing embodiments.
It should be noted that examples of the computer readable storage medium may also include, but are not limited to, a phase change memory (PRAM), a Static Random Access Memory (SRAM), a Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), a Read Only Memory (ROM), an Electrically Erasable Programmable Read Only Memory (EEPROM), a flash memory, or other optical or magnetic storage medium, which will not be described in detail herein.
The computer readable storage medium provided by the above embodiments of the present application has the same advantages as the method adopted, operated or implemented by the application program stored therein, because of the same inventive concept as the application program testing method provided by the embodiments of the present application.
It should be noted that:
in the description provided herein, numerous specific details are set forth. However, it is understood that embodiments of the present application may be practiced without these specific details. In some instances, well-known structures and techniques have not been shown in detail in order not to obscure an understanding of this description.
Similarly, it should be appreciated that in the foregoing description of exemplary embodiments of the application, various features of the application are sometimes grouped together in a single embodiment, figure, or description thereof for the purpose of streamlining the application and aiding in the understanding of one or more of the various inventive aspects. However, the disclosed method should not be construed as reflecting the following schematic diagram: i.e., the claimed application requires more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive aspects lie in less than all features of a single foregoing disclosed embodiment. Thus, the claims following the detailed description are hereby expressly incorporated into this detailed description, with each claim standing on its own as a separate embodiment of this application.
Furthermore, those skilled in the art will appreciate that while some embodiments described herein include some features but not others included in other embodiments, combinations of features of different embodiments are meant to be within the scope of the present application and form different embodiments. For example, in the following claims, any of the claimed embodiments can be used in any combination.
The foregoing is merely a preferred embodiment of the present application, but the scope of the present application is not limited thereto, and any changes or substitutions easily contemplated by those skilled in the art within the technical scope of the present application should be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims (12)

1. An application testing method, comprising:
detecting a preset use case switching operation, and displaying a use case grouping list corresponding to a current interface, wherein the use case grouping list comprises one or more use case points in the current interface;
refreshing the page content displayed on the current interface into the page content corresponding to the use case point according to the use case point selected by the user from the use case grouping list;
The refreshing the page content displayed on the current interface to the page content corresponding to the use case point according to the use case point selected by the user from the use case grouping list comprises the following steps:
modifying an identification field of the current interface according to a use case point selected by a user from the use case grouping list; the value of the identification field is an identifier of an application point corresponding to the page content displayed on the current interface; modifying the identification field comprises modifying an identifier corresponding to the page content displayed on the current interface into an identifier corresponding to the use case point selected by the user; and refreshing the page content displayed by the current interface into the page content corresponding to the use case point according to the modified identification field.
2. The method of claim 1, wherein before detecting the preset case switching operation and displaying the case grouping list corresponding to the current interface, further comprises:
acquiring a test case of an application program to be tested;
generating a case grouping list corresponding to each interface in the application program to be tested according to the test cases;
and the application case grouping list corresponding to each interface is built in the application program to be tested.
3. The method of claim 2, wherein the generating, according to the test cases, a case grouping list corresponding to each interface in the application to be tested includes:
acquiring case name information of each case point in a first interface from the test case, wherein the first interface is any interface in the application program to be tested;
respectively allocating identifiers for the use case points;
and generating an application grouping list corresponding to the first interface according to the application name information and the identifier of each application point.
4. A method according to claim 3, wherein the use case name information includes a use case name of the use case point and a function name of a function point to which the use case point belongs;
acquiring case name information of each case point in a first interface from the test case; according to the case name information and the identifier of each case point, generating a case grouping list corresponding to the first interface, including:
acquiring the function name of each function point included in the first interface from the test case and the case name of each case point;
and generating a case grouping list corresponding to the first interface according to the function name of each function point, the case name and the identifier of each case point.
5. The method of claim 1, wherein modifying the identification field of the current interface according to the use case point selected by the user from the use case group list comprises:
acquiring the use case name of the use case point selected by the user from the use case grouping list;
acquiring an identifier corresponding to the use case point according to the use case name;
judging whether the use case point is a multi-event use case point, if not, modifying the value of the identification field of the current interface into the acquired identifier;
if yes, converting a plurality of event identifications in the identifier into a character string, and modifying the value of the identification field of the current interface into the character string.
6. The method according to claim 1, wherein refreshing the page content displayed by the current interface to the page content corresponding to the use case point according to the modified identification field includes:
acquiring source data corresponding to the use case point according to the modified identification field;
and refreshing the page content displayed by the current interface into the page content corresponding to the use case point according to the source data corresponding to the use case point.
7. The method according to any one of claims 1-6, wherein the detecting the preset case switching operation and displaying the case grouping list corresponding to the current interface include:
detecting a preset gesture operation, and displaying an application grouping list corresponding to a current interface, wherein the preset gesture operation comprises a shaking operation or a sliding operation; or,
and detecting clicking operation of a preset suspension key for switching use cases, and displaying a use case grouping list corresponding to the current interface.
8. The method according to any one of claims 1-6, wherein the use case group list includes role use case points corresponding to different user roles, and further includes:
detecting that the role case point is clicked, and acquiring source data of a home page corresponding to the clicked role case point;
and jumping to the home page corresponding to the role use case point from the current interface according to the source data of the home page.
9. The method according to any one of claims 1-6, wherein after refreshing the page content displayed by the current interface to the page content corresponding to the use case point, the method further includes:
detecting a reset instruction triggered by a preset reset key, and resetting the value of the identification field to be a value before modification;
Acquiring source data corresponding to page content before page refreshing according to the reset identification field;
and refreshing the page content displayed by the current interface into the previous page content according to the acquired source data.
10. An application testing apparatus, comprising:
the list display module is used for detecting a preset case switching operation and displaying a case grouping list corresponding to a current interface, wherein the case grouping list comprises one or more case points in the current interface;
the page refreshing module is used for refreshing the page content displayed on the current interface into the page content corresponding to the use case point according to the use case point selected by the user from the use case grouping list;
the page refreshing module is used for modifying the identification field of the current interface according to the use case point selected by the user from the use case grouping list; the value of the identification field is an identifier of an application point corresponding to the page content displayed on the current interface; modifying the identification field comprises modifying an identifier corresponding to the page content displayed on the current interface into an identifier corresponding to the use case point selected by the user; and refreshing the page content displayed by the current interface into the page content corresponding to the use case point according to the modified identification field.
11. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor runs the computer program to implement the method of any one of claims 1-9.
12. A computer readable storage medium having stored thereon a computer program, wherein the program is executed by a processor to implement the method of any of claims 1-9.
CN202011556235.0A 2020-12-24 2020-12-24 Application program testing method, device, equipment and storage medium Active CN113448839B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202011556235.0A CN113448839B (en) 2020-12-24 2020-12-24 Application program testing method, device, equipment and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202011556235.0A CN113448839B (en) 2020-12-24 2020-12-24 Application program testing method, device, equipment and storage medium

Publications (2)

Publication Number Publication Date
CN113448839A CN113448839A (en) 2021-09-28
CN113448839B true CN113448839B (en) 2024-01-26

Family

ID=77808672

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202011556235.0A Active CN113448839B (en) 2020-12-24 2020-12-24 Application program testing method, device, equipment and storage medium

Country Status (1)

Country Link
CN (1) CN113448839B (en)

Citations (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5671351A (en) * 1995-04-13 1997-09-23 Texas Instruments Incorporated System and method for automated testing and monitoring of software applications
CN103377127A (en) * 2012-04-28 2013-10-30 阿里巴巴集团控股有限公司 Development testing system, testing method and device for webpage product
CN107122301A (en) * 2017-04-27 2017-09-01 武汉斗鱼网络科技有限公司 Interface detection method and device
CN108733571A (en) * 2018-05-28 2018-11-02 北京五八信息技术有限公司 A kind of test method, device, equipment and computer readable storage medium
CN109271316A (en) * 2018-08-28 2019-01-25 惠州Tcl移动通信有限公司 Android device and its automated testing method, memory
CN110008117A (en) * 2019-03-12 2019-07-12 深圳壹账通智能科技有限公司 Page test method, device, computer equipment and storage medium
CN110096431A (en) * 2019-03-19 2019-08-06 深圳壹账通智能科技有限公司 Page permissions test method, device, computer equipment and storage medium
CN110427323A (en) * 2019-07-29 2019-11-08 天津车之家数据信息技术有限公司 A kind of application testing method, device, proxy server and system
CN110765001A (en) * 2019-09-06 2020-02-07 赛诺贝斯(北京)营销技术股份有限公司 Modularized automatic test method and device for application system
CN110875858A (en) * 2018-08-31 2020-03-10 北京京东尚科信息技术有限公司 Application test data capturing method, system, equipment and storage medium
CN111897740A (en) * 2020-08-24 2020-11-06 北京字节跳动网络技术有限公司 User interface testing method and device, electronic equipment and computer readable medium

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7664989B2 (en) * 2005-10-24 2010-02-16 Infosys Technologies Ltd. Automated software testing architecture using a multi-level framework
US20180052666A1 (en) * 2016-08-22 2018-02-22 Microsoft Technology Licensing, Llc Adaptive Recursive User Interface Testing Automation Framework

Patent Citations (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5671351A (en) * 1995-04-13 1997-09-23 Texas Instruments Incorporated System and method for automated testing and monitoring of software applications
CN103377127A (en) * 2012-04-28 2013-10-30 阿里巴巴集团控股有限公司 Development testing system, testing method and device for webpage product
CN107122301A (en) * 2017-04-27 2017-09-01 武汉斗鱼网络科技有限公司 Interface detection method and device
CN108733571A (en) * 2018-05-28 2018-11-02 北京五八信息技术有限公司 A kind of test method, device, equipment and computer readable storage medium
CN109271316A (en) * 2018-08-28 2019-01-25 惠州Tcl移动通信有限公司 Android device and its automated testing method, memory
CN110875858A (en) * 2018-08-31 2020-03-10 北京京东尚科信息技术有限公司 Application test data capturing method, system, equipment and storage medium
CN110008117A (en) * 2019-03-12 2019-07-12 深圳壹账通智能科技有限公司 Page test method, device, computer equipment and storage medium
CN110096431A (en) * 2019-03-19 2019-08-06 深圳壹账通智能科技有限公司 Page permissions test method, device, computer equipment and storage medium
CN110427323A (en) * 2019-07-29 2019-11-08 天津车之家数据信息技术有限公司 A kind of application testing method, device, proxy server and system
CN110765001A (en) * 2019-09-06 2020-02-07 赛诺贝斯(北京)营销技术股份有限公司 Modularized automatic test method and device for application system
CN111897740A (en) * 2020-08-24 2020-11-06 北京字节跳动网络技术有限公司 User interface testing method and device, electronic equipment and computer readable medium

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
Towards automated translation between generations of GUI-based tests for mobile devices;Luca Ardito等;《International Symposium on Software Testing and Analysis》;46-53 *
网络环境下软件测试自动化技术的研究与应用;李军;《中国优秀硕士学位论文全文数据库 信息科技辑》;I138-101 *
面向移动互联网应用的测试方法研究与设计;宋艳敏;《中国优秀硕士学位论文全文数据库 信息科技辑》;I138-674 *

Also Published As

Publication number Publication date
CN113448839A (en) 2021-09-28

Similar Documents

Publication Publication Date Title
CN102419729B (en) Parallel test execution
US20170147480A1 (en) Test script generation
CN107729246B (en) Auxiliary test method, device and equipment for target application and storage medium
CN105824830B (en) Method, client and equipment for displaying page
CN112181554B (en) Interactive interface display method, device, electronic device and storage medium
CN112783761A (en) Method, device and system for testing cold start duration of application program
US11409623B2 (en) Integrated circuit (IC) power-up testing method and device, and electronic equipment
CN111881393A (en) Page rendering method, device, medium and electronic equipment
CN112925718A (en) Call stack backtracking method, device, equipment and medium
CN113672323A (en) Page display method and device
CN109828926B (en) Method and device for judging whether application interface is loaded abnormally
CN112052157B (en) Method, device and system for constructing test message
CN113448839B (en) Application program testing method, device, equipment and storage medium
CN111538667A (en) Page testing method and device
CN110020264B (en) Method and device for determining invalid hyperlinks
WO2023273621A1 (en) Script generation method and apparatus, device and medium
CN114328062B (en) Method, device and storage medium for checking cache consistency
CN111258875A (en) Interface test method and system, electronic device and storage medium
CN113051153B (en) Application software vulnerability scanning method and related equipment
CN114420190A (en) EMMC loss degree detection method and device, electronic equipment and storage medium
CN114238934A (en) Equipment information acquisition method, device, equipment and medium
CN109558319B (en) Method and device for testing Web page control and storage medium
CN112559346A (en) Service testing method and device
CN110888649B (en) Application deployment method, application baseline creation method and device
CN112579938A (en) Page loading method and device, storage medium and electronic equipment

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
TR01 Transfer of patent right

Effective date of registration: 20240508

Address after: 100102 room 1201, 12 / F, building 8, yard 34, Chuangyuan Road, Chaoyang District, Beijing

Patentee after: Beijing new oxygen world wide Technology Consulting Co.,Ltd.

Country or region after: China

Address before: 100102 room 901, 9 / F, room 1001, 10 / F, building 8, yard 34, Chuangyuan Road, Chaoyang District, Beijing

Patentee before: Beijing New Oxygen Technology Co.,Ltd.

Country or region before: China

TR01 Transfer of patent right