Application testing methods, apparatus, electronic equipment and media

Abstract

This disclosure relates to an application testing method, apparatus, electronic device, and medium. The application testing method includes: identifying applications under test that failed tests; and, if updates exist to the applications under test, performing runtime tests on the updated applications to obtain a first test result. By automating runtime tests on the applications under test, manual testing by testers is eliminated, thereby improving the efficiency of application testing. Furthermore, since runtime tests are performed only on applications under test that failed tests and have been updated, the number of application tests is reduced and invalid tests are avoided, further improving the efficiency of application testing.

Description

Technical Field

[0001] This disclosure relates to the field of testing technology, and in particular to an application testing method, apparatus, electronic device, and medium. Background Technology

[0002] To improve user experience and promptly identify application malfunctions, application runtime testing is necessary. However, since application runtime testing is performed manually by testers, it consumes a significant amount of time, resulting in low application testing efficiency. Summary of the Invention

[0003] To overcome the problems existing in related technologies, this disclosure provides an application testing method, apparatus, electronic device, and medium.

[0004] According to a first aspect of the present disclosure, an application testing method is provided, the application testing method comprising:

[0005] Identify the application under test that failed the test;

[0006] If the application under test is updated, the updated application under test is run and tested to obtain the first test result.

[0007] In some embodiments of this disclosure, determining the application under test that failed the test includes:

[0008] Get the list of first applications;

[0009] The applications in the first application list are identified as the applications to be tested.

[0010] In some embodiments of this disclosure, the first application list is based on test settings of the application by testers; and / or, the first application list is based on user feedback settings of the application; and / or, the first application list is based on second test results of the application at a historical time.

[0011] In some embodiments of this disclosure, before determining the application under test that has failed the test, the application testing method further includes:

[0012] Determine the status of the applications in the first application list in the first tab of the app store;

[0013] Remove the application whose status is "passed the test" from the first application list.

[0014] In some embodiments of this disclosure, after determining the status of applications in the first application list under a first tab in the app store, the application testing method further includes:

[0015] If the state of the first tag is different from the state of the corresponding second tag in the database, the state of the second tag is adjusted to the state of the first tag. The state of the second tag is the second test result of the application in the first application list at a historical moment.

[0016] In some embodiments of this disclosure, before determining the application under test that has failed the test, the application testing method further includes:

[0017] If the operating system is updated, the applications in the app store are run and tested on the updated operating system to obtain a third test result.

[0018] The process of identifying applications that fail the test includes:

[0019] The application that fails the third test is identified as the application to be tested.

[0020] In some embodiments of this disclosure, after running the updated application under test and obtaining a first test result, the application testing method further includes:

[0021] Update the status of the application under test in the first tab of the app store and / or the status of the second tab in the database to the first test result.

[0022] In some embodiments of this disclosure, after running the updated application under test and obtaining a first test result, the application testing method further includes:

[0023] The application under test that fails the first test is added to the second application list, which is used for subsequent running tests of the application under test.

[0024] In some embodiments of this disclosure, the application testing method further includes:

[0025] In response to the user's installation of the application under test from the app store, a prompt message is sent to the user, indicating that the application under test is malfunctioning.

[0026] According to a second aspect of the present disclosure, an application testing apparatus is provided, the application testing apparatus comprising:

[0027] A determination module, configured to determine applications under test that fail the test;

[0028] A testing module is configured to run tests on the updated application under test when the application under test is updated, and obtain a first test result.

[0029] According to a third aspect of the present disclosure, an electronic device is provided, the electronic device comprising:

[0030] processor;

[0031] Memory used to store the processor's executable instructions;

[0032] The processor is configured to execute the application testing method described above.

[0033] According to a fourth aspect of the present disclosure, a non-transitory computer-readable storage medium is provided, wherein when instructions in the storage medium are executed by a processor of a terminal, the terminal is enabled to perform the application testing method as described above.

[0034] The technical solutions provided by the embodiments of this disclosure may include the following beneficial effects:

[0035] If an application fails a test due to malfunction, it needs to be tested again to identify the application under test that failed. If an update to the application under test exists, the updated application may run correctly and pass the test. Running the test on the updated application under test yields the first test result, thus achieving automated testing. By automating the testing of the application under test, manual testing by testers is eliminated, improving the efficiency of application testing. Furthermore, since testing is only performed on applications that failed the test and have been updated, the number of application tests is reduced, and invalid tests are avoided, further improving the efficiency of application testing.

[0036] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit this disclosure. Attached Figure Description

[0037] The accompanying drawings, which are incorporated in and form a part of this specification, illustrate embodiments consistent with this disclosure and, together with the description, serve to explain the principles of this disclosure.

[0038] Figure 1 This is a schematic diagram illustrating an application testing architecture according to an exemplary embodiment;

[0039] Figure 2 This is a flowchart illustrating an application testing method according to an exemplary embodiment;

[0040] Figure 3This is a flowchart illustrating an application testing method according to another exemplary embodiment;

[0041] Figure 4 This is a flowchart illustrating an application testing method according to another exemplary embodiment;

[0042] Figure 5 This is a flowchart illustrating an application testing method according to another exemplary embodiment;

[0043] Figure 6 This is a block diagram of an application testing apparatus according to an exemplary embodiment;

[0044] Figure 7 This is a block diagram of an electronic device according to an exemplary embodiment.

[0045] In the picture:

[0046] 100 - Determine module; 200 - Test module; 400 - Electronic device; 402 - Processing component; 404 - Memory; 406 - Power supply component; 408 - Multimedia component; 410 - Audio component; 412 - Input / output interface; 414 - Sensor component; 416 - Communication component; 420 - Processor. Detailed Implementation

[0047] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this disclosure. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this disclosure as detailed in the appended claims. It should also be understood that the term “and / or” as used in this disclosure refers to and includes any or all possible combinations of one or more of the associated listed items.

[0048] In today's digital age, electronic devices have become an indispensable part of people's daily lives, and their widespread use has greatly promoted the booming development of applications. Whether in social networking, entertainment, education, or practical tools, a plethora of applications have emerged, greatly satisfying user needs. To bring users new features and fix existing defects, operating systems need to be updated regularly. However, because applications cannot always keep up with operating system updates, some outdated applications will malfunction when running on the updated operating system. Therefore, it is necessary to perform runtime testing on applications to promptly identify and resolve these issues.

[0049] In related technologies, an application testing method is provided, comprising: testers installing the application under test on the operating system; testers launching the application under test and performing various operations on it; testers determining the test results based on the application's performance; and testers manually recording the test results. This method, by having testers manually run the application under test, can identify applications with anomalies for subsequent follow-up and testing. However, because the application's runtime testing is performed manually by testers, it consumes a significant amount of time, resulting in low efficiency in application testing.

[0050] To address the aforementioned technical issues, this disclosure provides an application testing method that automates runtime testing of the application under test, eliminating the need for manual testing by testers and reducing testing time, thereby improving application testing efficiency. Furthermore, since the application being tested is a previously untested application that is also available for updating, the number of applications tested is reduced, and invalid tests are avoided, further enhancing application testing efficiency.

[0051] To facilitate understanding, the application testing architecture of this disclosure will be described first. For example... Figure 1As shown, the application testing architecture includes a data input module, an automated testing module, a database, and an app store. The data input module has test request, user feedback, data import, and tag detection functions. The test request function transmits test data from testers to the database. The user feedback function transmits user feedback on application runtime anomalies to the database. The data import function imports test data output from the automated testing module into the database. The tag detection function detects the status of the first tag of the application in the app store and adjusts the second tag's status to match the first tag's status if the first tag's status is inconsistent with the corresponding second tag's status in the database. The automated testing module has application list retrieval, test execution, update check, test data output, and test data sending functions. The application list retrieval function retrieves the list of applications containing the application under test from the database. The test execution function runs the application under test. The update check checks if the application under test is updated. The test data output function outputs the test data from the application's test execution. The test data sending function sends the test data to testers via email. The database has data storage and tag status update functions. The data storage function stores application data, test data, and tag status. The tag status update function updates the status of corresponding tags based on test data. The app store includes application adjustment and risk warning functions. The application adjustment function adjusts applications that have been removed from the store. The risk warning function alerts users to applications that have failed testing and are experiencing operational issues. Test data includes, but is not limited to, test results, runtime logs, and exception information.

[0052] This disclosure provides an application testing method, such as... Figure 2 As shown, the method includes:

[0053] S100: Identify the application under test that failed the test.

[0054] S200. If the application under test is updated, run the updated application under test to obtain the first test result.

[0055] In this embodiment, if an application fails the test due to malfunction, it needs to be tested again to identify the applications that failed the test. If an update to the application exists, the updated application may run normally and pass the test. The updated application is then run and tested to obtain a first test result, thus achieving automated testing of the application. By automating the testing of the application, manual testing by testers is eliminated, improving the efficiency of application testing. Furthermore, since testing is only performed on applications that failed the test and have been updated, the number of applications tested is reduced, and invalid tests are avoided, further improving the efficiency of application testing.

[0056] For example, the application under test can be an application that failed the second test when running the test at a historical time, or it can be a newly released application in the app store.

[0057] For example, the application under test fails the test due to at least one of the following abnormal conditions: crashing on startup, crashing during operation, or freezing during operation.

[0058] In one embodiment, such as Figure 3 As shown, the application under test that fails the test in step S100 can be determined in the following way:

[0059] S110, Obtain the first application list.

[0060] S120. Identify the applications in the first application list as the applications to be tested.

[0061] In this embodiment, since applications that fail the test are stored in a first application list, the first application list is obtained, and the applications in the first application list are identified as applications to be tested. Identifying applications to be tested using the first application list efficiently identifies these applications and avoids omissions, thereby improving the efficiency of application testing.

[0062] In one embodiment, the first list of applications is based on the test settings of the applications by the testers.

[0063] In this embodiment, since the operating system needs to undergo internal testing before release, operators randomly run the application on the operating system to be tested. When an anomaly occurs during the application's runtime test, the testers capture the runtime logs and reproduce the problem, adding the application with the anomaly to a first application list. By setting a first application list during the operating system testing process, application runtime testing can be performed as early as possible, thereby improving the reliability of application testing.

[0064] In one embodiment, the first list of applications is set based on user feedback on the applications.

[0065] In this embodiment, because the testing methods used during application runtime testing may differ from users' habits, users may encounter anomalies when using the application. By setting a first list of applications based on user feedback, missed applications can be tested, thereby improving the reliability of application testing.

[0066] In one embodiment, the first list of applications is set based on the application's second test results at a historical moment.

[0067] In this embodiment, since a second test result is obtained after running the application at a historical time, applications that failed the test can be filtered out from the second test result. By setting a first application list based on the second test result, applications that failed the test at a historical time can be retested, thereby improving the reliability of application testing.

[0068] In one embodiment, such as Figure 4 As shown, before determining the application under test that failed the test in step S100, the application testing method further includes:

[0069] S300: Determine the status of the application in the first application list on the first tab of the app store.

[0070] S310. Remove the application whose first tag status is "passed the test" from the first application list.

[0071] In this embodiment, testers may manually test some applications under test to verify the effectiveness of automated testing or operating system compatibility. If the test results change after manual testing, the testers adjust the application's first tag status in the app store. To avoid invalid testing, the status of the applications in the first application list's first tag in the app store is determined before identifying applications that failed the test. By removing applications with a first tag status of "passed the test" from the first application list, retesting these applications is avoided, thereby improving the efficiency of application testing.

[0072] For example, each application has a corresponding first label in the app store. The status of the first label is used to inform the user whether the application can run normally under the current operating system. The status of the first label can be a second test result or a test result set by the tester.

[0073] For example, in addition to identifying applications in the first application list as applications to be tested, applications in the app store whose first label status is "not tested" can also be identified as applications to be tested.

[0074] In one embodiment, after determining the status of applications in the first application list under the first tab in the app store in step S300, the application testing method further includes:

[0075] If the state of the first tag differs from the state of the corresponding second tag in the database, the state of the second tag is adjusted to match the state of the first tag. The state of the second tag is the second test result of the application in the first application list at a historical moment.

[0076] In this embodiment, because the tester adjusts the state of the application's first tag in the app store, the state of the first tag in the app store changes, but the state of the corresponding second tag in the database does not change. When the state of the first tag differs from the state of the corresponding second tag, the state of the second tag is adjusted to match the state of the first tag to synchronize the state of the first tag with the database. By adjusting the state of the second tag in conjunction with the state of the first tag, the database is prevented from providing incorrect tag states during application testing, thereby improving the reliability of application testing.

[0077] For example, data in the database can be displayed on a visualization page. The visualization page can display information such as ID, application name, application version, problem description, and secondary tags, and allows for data filtering, searching, and display operations.

[0078] In one embodiment, before determining the application under test that failed the test in step S100, the application testing method further includes:

[0079] If an operating system update is available, the applications in the app store are run and tested on the updated operating system to obtain the third test result.

[0080] The application under test that failed the test in step S100 can also be determined in the following way:

[0081] Applications that fail the third test are identified as applications to be tested.

[0082] In this embodiment, when the operating system is updated, applications in the app store may become incompatible with the updated operating system and malfunction, regardless of whether they have passed testing. The applications in the app store are run and tested on the updated operating system to obtain a third test result, thus achieving the testing of each application. Since applications that fail the test need to be retested after the update, applications that fail the third test are identified as applications to be tested. By running and testing applications after the operating system update, incompatible applications can be identified in a timely manner for retesting, thereby improving the reliability of application testing.

[0083] For example, an operating system update can be a minor version update or a major version update. Minor and major versions can be distinguished by the operating system's version number.

[0084] For example, after obtaining the third test result, the application whose third test result is not passed can be set in the first application list.

[0085] For example, the application under test that fails the test in step S100 can also be determined in the following way:

[0086] The application to be tested is determined after a preset time interval.

[0087] The preset time can be 1 hour, 12 hours, 24 hours, etc.

[0088] For example, if the application under test has been updated, this can be identified by detecting the application's version number. When an update is available, the version number, update time, and other information of the application under test are updated in the app store. The step S200, which involves running a test on the updated application under test, can be implemented using automated testing tools such as UIAuto. If the application under test runs normally, the first test result is "pass." That is, if the application under test does not exhibit any abnormalities such as startup crash, runtime crash, or runtime freeze, the first test result is "pass." If the application under test exhibits abnormalities, the first test result is "fail." That is, if the application under test exhibits at least one of the abnormalities of startup crash, runtime crash, or runtime freeze, the first test result is "fail."

[0089] In one embodiment, after running the updated application under test in step S200 to obtain the first test result, the application testing method further includes:

[0090] Update the status of the app under test in the first tab of the app store to the first test result.

[0091] In this embodiment, by updating the status of the application under test in the first tab of the app store to the first test result, the user can determine whether to install the updated application under test based on the status of the first tab, thereby improving the user experience.

[0092] In one embodiment, after running the updated application under test in step S200 to obtain the first test result, the application testing method further includes:

[0093] Update the status of the application under test in the second tag of the database to the first test result.

[0094] In this embodiment, by updating the status of the application under test in the second tag of the database to the first test result, testers can identify applications that have passed and failed the test on the visualization page for follow-up, thereby improving the reliability of application testing.

[0095] In one embodiment, after running the updated application under test in step S200 to obtain the first test result, the application testing method further includes:

[0096] Applications that fail the first test are added to a second list of applications, which are then used for subsequent running tests of the applications.

[0097] In this embodiment, if the first test result is a failure, the application under test needs to be run again after the next update, and the application under test will be added to the second application list. By adding the application under test that failed the test to the second application list, the application under test is not missed during subsequent test runs, thereby improving the reliability of application testing.

[0098] For example, when identifying applications that fail the test later, applications from the second application list are selected as the applications to be tested. That is, the second application list can be the first application list for the next application test.

[0099] For example, in addition to adding the application to be tested to the second application list, the application to be tested can also be removed from the first application list. When subsequently identifying applications that fail the test, the applications in the first application list will still be identified as applications to be tested.

[0100] For example, after running tests on the updated application under test in step S200 and obtaining the first test result, the application testing method further includes:

[0101] The initial test results are sent to the testers via email so that the application under test can be followed up.

[0102] In one embodiment, the application testing method further includes:

[0103] In response to a user installing the application under test from the app store, a prompt message is sent to the user, indicating that the application under test is malfunctioning.

[0104] In this embodiment, in response to a user's installation of an application under test from an app store, the installed application may malfunction during runtime, affecting the user experience. A prompt message is then sent to the user. By issuing a prompt message when a user installs an application that has failed testing, the user can decide whether to install the application under test based on the prompt, thereby improving the user experience.

[0105] This disclosure provides an application testing method, such as... Figure 5 As shown, the method includes:

[0106] S400: If the operating system is updated, run the applications in the app store on the updated operating system to obtain the third test result.

[0107] S410. Add the application that failed the third test to the first application list in the database.

[0108] S420. Every day, determine the status of the applications in the first application list on the first tab of the app store.

[0109] S430. If the state of the first tag is different from the state of the corresponding second tag in the database, adjust the state of the second tag to the state of the first tag.

[0110] S440: Remove the application whose first tag status is "Passed Test" from the first application list.

[0111] S450: Retrieve the first application list from the database.

[0112] S460. Identify the applications in the first application list as the applications to be tested.

[0113] S470. If the application under test is updated, run the updated application under test to obtain the first test result.

[0114] S480, Update the status of the application under test in the first tab of the app store and the status of the second tab in the database to the first test result.

[0115] S490. Add the application to be tested that failed the first test to the second application list.

[0116] In this embodiment, when the operating system is updated, the applications in the app store are run and tested on the updated operating system to obtain a third test result. Since applications that fail the test need to be retested after the update, applications with the third test result indicating failure are added to the first application list in the database. Because testers may manually adjust the state of the application's first tag in the app store, the state of the first tag is determined. If the state of the first tag differs from the corresponding state of the second tag in the database, the tester adjusts the state of the first tag after testing, synchronizing the second tag state with the first tag state. Applications with the first tag state indicating success are removed from the first application list to avoid invalid retesting. Since applications in the first application list need retesting, the first application list is retrieved from the database, and the applications in the first application list are identified as applications to be tested. If the applications to be tested are updated, the updated applications are run and tested to obtain a first test result. The state of the first tag of the applications to be tested in the app store and the state of the second tag in the database are updated to the first test result to synchronize the test results. Applications to be tested with the first test result indicating failure are added to the second application list for subsequent retesting. By automating the running tests of applications under test, manual testing by testers is eliminated, thus improving the efficiency of application testing. Furthermore, since testing is only performed on applications that have failed tests and are subject to updates, the number of applications tested is reduced and invalid tests are avoided, further improving application testing efficiency.

[0117] In one exemplary embodiment, an application testing apparatus is provided for implementing the method described above. (Reference) Figure 6 As shown, the application testing apparatus may include a determination module 100 and a testing module 200, wherein, during the implementation of the above method,

[0118] Module 100 is configured to identify applications under test that have failed tests.

[0119] Test module 200 is configured to run tests on the updated application under test when the application under test is updated, and obtain the first test result.

[0120] In one exemplary embodiment, an application testing apparatus is provided, wherein a determining module 100 is configured to:

[0121] Get the first list of applications.

[0122] The applications in the first application list are identified as the applications to be tested.

[0123] In one exemplary embodiment, an application testing apparatus is provided, wherein a determining module 100 is configured to:

[0124] Determine the status of the applications in the first list on the first tab of the app store.

[0125] In one exemplary embodiment, an application testing apparatus is provided, the apparatus further comprising:

[0126] The adjustment module is configured to remove applications whose first tag status is "passed" from the first application list.

[0127] In one exemplary embodiment, an application testing apparatus is provided, wherein an adjustment module is configured to:

[0128] If the state of the first tag differs from the state of the corresponding second tag in the database, the state of the second tag is adjusted to match the state of the first tag. The state of the second tag is the second test result of the application in the first application list at a historical moment.

[0129] In one exemplary embodiment, an application testing apparatus is provided, wherein a testing module 200 is configured to:

[0130] If an operating system update is available, the applications in the app store are run and tested on the updated operating system to obtain the third test result.

[0131] In one exemplary embodiment, an application testing apparatus is provided, wherein a determining module 100 is configured to:

[0132] Applications that fail the third test are identified as applications to be tested.

[0133] In one exemplary embodiment, an application testing apparatus is provided, the apparatus further comprising:

[0134] The update module is configured to update the status of the application under test in the first tab of the app store and / or the status of the second tab in the database to the first test result.

[0135] In one exemplary embodiment, an application testing apparatus is provided, the apparatus further comprising:

[0136] The settings module is configured to add applications that fail the first test to a second list of applications, which is used for subsequent running tests of the applications.

[0137] In one exemplary embodiment, an application testing apparatus is provided, the apparatus further comprising:

[0138] The prompt module is configured to send a prompt message to the user in response to the user's action of installing the application under test in the app store. The prompt message is used to inform the user that the application under test is malfunctioning.

[0139] In one exemplary embodiment, an electronic device is provided, such as a mobile phone, a laptop computer, a tablet computer, and a wearable device.

[0140] refer to Figure 7 As shown, the electronic device 400 may include one or more of the following components: processing component 402, memory 404, power supply component 406, multimedia component 408, audio component 410, input / output (I / O) interface 412, sensor component 414, and communication component 416.

[0141] Processing component 402 typically controls the overall operation of electronic device 400, such as operations associated with display, telephone calls, data communication, camera operation, and recording. Processing component 402 may include one or more processors 420 to execute instructions to perform all or part of the steps of the methods described above. Furthermore, processing component 402 may include one or more modules to facilitate interaction between processing component 402 and other components. For example, processing component 402 may include a multimedia module to facilitate interaction between multimedia component 408 and processing component 402.

[0142] Memory 404 is configured to store various types of data to support the operation of electronic device 400. Examples of this data include instructions for any application or method operating on electronic device 400, contact data, phonebook data, messages, pictures, videos, etc. Memory 404 can be implemented by any type of volatile or non-volatile storage terminal or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk.

[0143] Power supply component 406 provides power to various components of electronic device 400. Power supply component 406 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to electronic device 400.

[0144] Multimedia component 408 includes a screen that provides an output interface between electronic device 400 and user. In some embodiments, the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touchscreen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensors may sense not only the boundaries of touch or swipe actions but also the duration and pressure associated with the touch or swipe operation. In some embodiments, multimedia component 408 includes a front-facing camera module and / or a rear-facing camera module. When electronic device 400 is in an operating mode, such as shooting mode or video mode, the front-facing camera module and / or rear-facing camera module may receive external multimedia data. Each front-facing camera module and rear-facing camera module may be a fixed optical lens system or have focal length and optical zoom capabilities.

[0145] Audio component 410 is configured to output and / or input audio signals. For example, audio component 410 includes a microphone (MIC) configured to receive external audio signals when electronic device 400 is in an operating mode, such as call mode, recording mode, and voice recognition mode. The received audio signals may be further stored in memory 404 or transmitted via communication component 416. In some embodiments, audio component 410 also includes a speaker for outputting audio signals.

[0146] I / O interface 412 provides an interface between processing component 402 and peripheral interface modules, such as keyboards, click wheels, buttons, etc. These buttons may include, but are not limited to, home buttons, volume buttons, power buttons, and lock buttons.

[0147] Sensor assembly 414 includes one or more sensors for providing state assessments of various aspects of electronic device 400. For example, sensor assembly 414 may detect the on / off state of electronic device 400, the relative positioning of components such as the display and keypad of electronic device 400, changes in position of electronic device 400 or a component of electronic device 400, the presence or absence of user contact with electronic device 400, orientation or acceleration / deceleration of electronic device 400, and temperature changes of electronic device 400. Sensor assembly 414 may include a proximity sensor configured to detect the presence of nearby objects without any physical contact. Sensor assembly 414 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, sensor assembly 414 may also include an accelerometer, gyroscope, magnetometer, pressure sensor, or temperature sensor.

[0148] Communication component 416 is configured to facilitate wired or wireless communication between electronic device 400 and other terminals. Electronic device 400 can access wireless networks based on communication standards, such as WiFi, 2G, 3G, 4G, 5G, or combinations thereof. In one exemplary embodiment, communication component 416 receives broadcast signals or broadcast-related information from an external broadcast management system via a broadcast channel. In one exemplary embodiment, communication component 416 also includes a near-field communication (NFC) module to facilitate short-range communication. For example, the NFC module may be implemented based on radio frequency identification (RFID) technology, Infrared Data Association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.

[0149] In an exemplary embodiment, the electronic device 400 may be implemented by one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing terminals (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic components to perform the methods shown in the above embodiments or combinations thereof.

[0150] In one exemplary embodiment, a non-transitory computer-readable storage medium including instructions is also provided, such as a memory 404 including instructions, which can be executed by a processor 420 of an electronic device 400 to perform the methods shown in the embodiments or combinations thereof. For example, the non-transitory computer-readable storage medium may be a ROM, random access memory (RAM), CD-ROM, magnetic tape, floppy disk, and optical data storage terminal, etc. When the instructions in the storage medium are executed by the processor of the terminal, the terminal is able to perform the methods shown in the embodiments or combinations thereof.

[0151] Other embodiments of this disclosure will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This disclosure is intended to cover any variations, uses, or adaptations of this disclosure that follow the general principles of this disclosure and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this disclosure are indicated by the claims.

[0152] In the description of this specification, the references to terms such as "one embodiment," "some embodiments," "example," "specific example," or "some examples," etc., indicate that a specific feature, structure, material, or characteristic described in connection with that embodiment or example is included in at least one embodiment or example of this disclosure. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples. Moreover, without contradiction, those skilled in the art can combine and integrate the different embodiments or examples described in this specification, as well as the features of different embodiments or examples.

[0153] Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one of that feature. In the description of this disclosure, "a plurality of" means at least two, such as two, three, etc., unless otherwise explicitly specified.

[0154] It should be understood that the various forms of processes shown above can be used to rearrange, add, or delete steps. For example, the steps described in this disclosure can be executed in parallel, sequentially, or in different orders, as long as the desired result of the technical solution disclosed in this disclosure can be achieved, and this is not limited herein.

[0155] The specific embodiments described above do not constitute a limitation on the scope of protection of this disclosure. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this disclosure should be included within the scope of protection of this disclosure.

Claims

1. An application testing method, characterized in that, The application testing method includes: Identify the application under test that failed the test; If the application under test is updated, the updated application under test is run and tested to obtain the first test result.

2. The application testing method according to claim 1, characterized in that, The process of identifying applications that fail the test includes: Get the list of first applications; The applications in the first application list are identified as the applications to be tested.

3. The application testing method according to claim 2, characterized in that, The first list of applications is based on the test settings of the application by the testers; and / or, the first list of applications is based on the feedback settings of the application by the users; and / or, the first list of applications is based on the second test results of the application at a historical time.

4. The application testing method according to claim 2, characterized in that, Before identifying the application under test that failed the test, the application testing method further includes: Determine the status of the applications in the first application list in the first tab of the app store; Remove the application whose status is "passed the test" from the first application list.

5. The application testing method according to claim 4, characterized in that, After determining the status of applications in the first application list on the first tab of the app store, the application testing method further includes: If the state of the first tag is different from the state of the corresponding second tag in the database, the state of the second tag is adjusted to the state of the first tag. The state of the second tag is the second test result of the application in the first application list at a historical moment.

6. The application testing method according to claim 1, characterized in that, Before identifying the application under test that failed the test, the application testing method further includes: If the operating system is updated, the applications in the app store are run and tested on the updated operating system to obtain a third test result. The process of identifying applications that fail the test includes: The application that fails the third test is identified as the application to be tested.

7. The application testing method according to claim 1, characterized in that, After running the updated application under test and obtaining the first test result, the application testing method further includes: Update the status of the application under test in the first tab of the app store and / or the status of the second tab in the database to the first test result.

8. The application testing method according to claim 1, characterized in that, After running the updated application under test and obtaining the first test result, the application testing method further includes: The application under test that fails the first test is added to the second application list, which is used for subsequent running tests of the application under test.

9. The application testing method according to any one of claims 1 to 8, characterized in that, The application testing method also includes: In response to the user's installation of the application under test from the app store, a prompt message is sent to the user, indicating that the application under test is malfunctioning.

10. An application testing device, characterized in that, The application testing device includes: A determination module, configured to determine applications under test that fail the test; A testing module is configured to run tests on the updated application under test when the application under test is updated, and obtain a first test result.

11. An electronic device, characterized in that, The electronic device includes: processor; Memory used to store the processor's executable instructions; The processor is configured to execute the application testing method as described in any one of claims 1 to 9.

12. A non-transitory computer-readable storage medium, characterized in that, When the instructions in the storage medium are executed by the processor of the terminal, the terminal is able to perform the application testing method as described in any one of claims 1 to 9.

Images