Automated end-to-end testing of mobile applications displaying optical barcodes

The system addresses the challenge of incomplete real-world simulation in mobile application testing by using a coordinator unit and robotic devices to simulate ambient lighting and device position, enhancing testing accuracy and scalability.

JP7588666B2Active Publication Date: 2024-11-22RAKUTEN GROUP INC
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
JP2023005804
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Priority Date
2022-04-29
Filing Date
2023-01-18
Publication Date
2024-11-22
Estimated Expiration
2043-01-18

AI Technical Summary

Technical Problem

Current automated testing of mobile applications fails to accurately simulate real-world conditions such as ambient lighting, scan angle, and device position during optical barcode scanning, leading to incomplete testing of mobile application performance.

Method used

A system and method for end-to-end testing that includes a coordinator unit, robotic devices, and agents to simulate real-world conditions like ambient lighting, scan angles, and device position, enabling comprehensive testing of mobile applications' barcode scanning functionality.

Benefits of technology

The system provides accurate simulation of real-world conditions, enhancing the testing of mobile applications' barcode scanning capabilities, improving performance and scalability through multiple test environments and robotic devices.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007588666000001
    Figure 0007588666000001
  • Figure 0007588666000002
    Figure 0007588666000002
  • Figure 0007588666000003
    Figure 0007588666000003
Patent Text Reader

Abstract

To provide a method, a device, and a system for end-to-end mobile application testing.SOLUTION: A method includes receiving, by a coordinator unit, a task for testing at least one electronic device; retrieving, by a first agent from the coordinator unit, the task for testing the at least one electronic device; controlling a first robotic device to test the at least one electronic device based on the retrieved task; and receiving, by the coordinator unit, a result of the task based on the testing of the at least one electronic device.SELECTED DRAWING: Figure 7
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present disclosure relates generally to methods, apparatus and systems for end-to-end mobile application testing. [Background technology]

[0002] Currently, there exists automated testing of applications for digital and some analog user methods. In analog methods, analog information is converted to a digital format for testing. The analog-to-digital conversion does not allow this testing to simulate real-world user actions and conditions. In the example of a user presenting a barcode on an electronic device for scanning in a brick-and-mortar store, to test this, a screenshot of the barcode is taken and an application is used that converts this screenshot into a barcode number. However, this automated testing process does not test exactly how the analog optical barcode scan signal is captured and does not take into account real-world conditions such as ambient lighting conditions, scan angle, device position and brightness settings. Summary of the Invention

[0003] According to one aspect of the present disclosure, a method includes receiving, by a coordinator unit, a task for testing at least one electronic device; retrieving, by a first agent, the task for testing the at least one electronic device from the coordinator unit, controlling a first robotic device to test the at least one electronic device based on the retrieved task; and receiving, by the coordinator unit, a result of the task based on the testing of the at least one electronic device.

[0004] According to one aspect of the present disclosure, a system includes a memory that stores instructions and a processor configured to execute the instructions, the processor configured to execute instructions to receive, using a coordinator unit, a task for testing at least one electronic device, retrieve, by a first agent, the task for testing the at least one electronic device from the coordinator unit, control a first robotic device to test the at least one electronic device based on the retrieved task, and receive, using the coordinator unit, a result of the task based on the testing of the at least one electronic device.

[0005] Additional aspects will be set forth in part in the description that follows, and in part will be apparent from the description, or may be learned by practice of presented embodiments of the present disclosure.

[0006] The above and other aspects, features, and aspects of embodiments of the present disclosure will become more apparent from the following description taken in conjunction with the accompanying drawings. [Brief description of the drawings]

[0007] [Figure 1] FIG. 2 is a diagram of devices of a system according to one embodiment. [Diagram 2] FIG. 2 is a diagram of components of the device of FIG. 1 according to one embodiment. [Diagram 3] FIG. 1 is a diagram of a system for end-to-end mobile application testing according to one embodiment. [Figure 4] FIG. 1 is a diagram of a system for distributing test tasks according to one embodiment. [Figure 5A] FIG. 1 is a diagram of the operational flow of end-to-end mobile application testing according to environment. [Figure 5B] FIG. 1 is a diagram of the operational flow of end-to-end mobile application testing according to environment. [Figure 6A]FIG. 1 is a diagram of a mobile application testing environment according to one embodiment. [Figure 6B] FIG. 1 is a diagram of a mobile application testing environment according to one embodiment. [Figure 7] 1 is a flowchart of a mobile application testing method according to one embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0008] The following detailed description of the example embodiments refers to the accompanying drawings, in which the same reference numbers in different drawings may identify the same or similar elements.

[0009] Figure 1 is a diagram of a system according to one embodiment, including a user device 110, a server device 120, and a network 130. The user device 110 and the server device 120 may be interconnected via wired connections, wireless connections, or a combination of wired and wireless connections.

[0010] The user device 110 may include a computing device (e.g., a desktop computer, a laptop computer, a tablet computer, a handheld computer, a smart speaker, a server device, etc.), a mobile phone (e.g., a smartphone, a wireless phone, etc.), a camera device, a wearable device (e.g., smart glasses or a smart watch), or a similar device.

[0011] The server device 120 may include one or more devices. For example, the server device 120 may be a server device, a computing device, etc.

[0012] Network 130 may include one or more wired and / or wireless networks. For example, network 130 may include a cellular network (e.g., a fifth generation (5G) network, a long-term evolution (LTE) network, a third generation (3G) network, a code division multiple access (CDMA) network, etc.), a public land mobile network (PLMN), a local area network (LAN), a wide area network (WAN), a metropolitan area network (MAN), a telephone network (e.g., a Public Switched Telephone Network (PSTN)), a private network, an ad-hoc network, an intranet, the Internet, a fiber-optic based network, etc., and / or a combination of these or other types of networks.

[0013] The number and arrangement of devices and networks shown in Figure 1 are provided as an example. In practice, there may be additional devices and / or networks, fewer devices and / or networks, different devices and / or networks, or the devices and / or networks may be arranged differently compared to those shown in Figure 1. Furthermore, two or more devices shown in Figure 1 may be implemented within a single device, or a single device shown in Figure 1 may be implemented as multiple distributed devices. Additionally or alternatively, a set of devices may be implemented in a single device. (eg, one or more devices) may perform one or more functions described as being performed by another set of devices.

[0014] 2 is a diagram of components of one or more devices of FIG. 1 according to one embodiment. Device 200 may correspond to user device 110 and / or server device 120.

[0015] As shown in FIG. 2, device 200 can include a bus 210, a processor 220, a memory 230, a storage component 240, an input component 250, an output component 260, and a communication interface 270.

[0016] Bus 210 includes components that enable communication between components of device 200. Processor 220 is implemented in hardware, firmware, or a combination of hardware and software. Processor 220 may be a central processing unit (CPU), a graphics processing unit (GPU), an accelerated processing unit (APU), a microprocessor, a microcontroller, a digital signal processor (DSP), a field-programmable gate array (FPGA), an application-specific integrated circuit (ASIC), or another type of processing component. Processor 220 includes one or more processors that can be programmed to perform functions.

[0017] Memory 230 may include random access memory (RAM), read only memory (ROM), and / or another type of dynamic or static storage device (e.g., flash memory, magnetic memory, and / or optical memory) that stores information and / or instructions used by processor 220.

[0018] Storage component 240 stores information and / or software related to the operation and use of device 200. For example, storage component 240 can include a hard disk (e.g., a magnetic disk, an optical disk, a magneto-optical disk, and / or a solid-state disk), a compact disc (CD), a digital versatile disc (DVD), a floppy disk, a cartridge, a magnetic tape, and / or another type of non-transitory computer-readable medium with a corresponding drive.

[0019] Input components 250 include components (e.g., a touchscreen display, a keyboard, a keypad, a mouse, buttons, switches, and / or a microphone) that enable device 200 to receive information, such as through user input. Input components 250 can include sensors (e.g., global positioning system (GPS) components, accelerometers, gyroscopes, and / or actuators) that detect information.

[0020] Output components 260 include components that provide output information from device 200, such as a display, a speaker, and / or one or more light-emitting diodes (LEDs).

[0021] Communications interface 270 includes transceiver-like components (e.g., a transceiver and / or a separate receiver and transmitter) that enable device 200 to communicate with other devices, such as via a wired connection, a wireless connection, or a combination of wired and wireless connections. Communications interface 270 may enable device 200 to receive information from and / or provide information to another device. For example, communications interface 270 may include an Ethernet interface, an optical interface, a coaxial interface, an infrared interface, a radio frequency (RF) interface, a universal serial bus (USB) interface, a Wi-Fi interface, a cellular network interface, etc.

[0022] Device 200 may perform one or more processes described herein. Device 200 may perform operations based on processor 220 executing software instructions stored by a non-transitory computer-readable medium, such as memory 230 and / or storage component 240. A computer-readable medium is defined herein as a non-transitory memory device. A memory device includes memory space within a single physical storage device or memory space distributed across multiple physical storage devices.

[0023] The software instructions may be loaded into memory 230 and / or storage component 240 from another computer readable medium or from another device via communications interface 270. The software instructions stored in memory 230 and / or storage component 240, when executed, may cause processor 220 to perform one or more processes described herein.

[0024] Provided herein is a system and method for automatically performing end-to-end testing of real-world optical barcode scanning conditions for mobile applications running on electronic devices. The system and method simulates user conditions for barcode scanning testing, enhances the barcode scanning testing environment to account for multiple devices, and enables a scalable system that includes multiple scanning devices and robotic devices. The end-to-end testing system includes analog testing of barcode scanning functionality, testing of mobile application user interface (UI), and testing of back-end application programming interface (API). The system and method provide the ability to automate end-to-end regression testing of mobile application analog optical barcode scanning processes, simulating real-world user conditions such as ambient lighting conditions, scanning angles, device position, brightness settings, barcode scanner characteristics, barcode position settings on the device, etc.

[0025] The system and method may be implemented with multiple test environments and / or in multiple locations. For example, one test environment may be located in a first location and another test environment may be located in a second location. These locations may have different characteristics specific to their respective locations, such as different types of Global Positioning System (GPS) signals, country codes, different physical conditions (e.g., lighting), devices available only in certain locations, brands of devices, etc. Thus, the system and method may perform testing based on location-specific characteristics. Additionally, the system and method with multiple test environments provides a "backup" in the event that one test environment is unavailable (e.g., power outage, in use by another test device, etc.). Thus, the system and method provides business continuity planning (BCP) (i.e., the system and method may be implemented and utilized without significant interruption).

[0026] 3 is a diagram of a system for end-to-end mobile application testing according to one embodiment. The system may include a continuous integration (CI) / continuous delivery (CD) pipeline 300 (e.g., the system including the server device 120 and the network 130 in FIG. 1), an automated test tool 302 (e.g., the system including the server device 120 and the network 130 in FIG. 1), a mobile test platform 304 (e.g., the system including the server device 120 and the network 130 in FIG. 1), a coordinator 306 (e.g., the system including the server device 120 and the network 130 in FIG. 1), an agent 308 (e.g., the system including the server device 120 and the network 130 in FIG. 1), a robotic device 310, an electronic device 312 (e.g., the device 110 in FIG. 1), and a back-end server 314 (e.g., the system including the server device 120 and the network 130 in FIG. 1). Although FIG. 3 illustrates a system having a single component, the system may include multiple components (eg, multiple coordinators, multiple agents, multiple robotic devices, etc.).

[0027] The CI / CD pipeline 300 begins running the automated tests.

[0028] The automated test tool 302 may execute test cases and act as a client that sends tasks to the coordinator 306. The automated test tool 302 may be implemented as an external function. The automated test tool 302 may communicate with the mobile test platform 304 and the backend server 314.

[0029] The mobile test platform 304 may be implemented as a virtual device that installs and controls a mobile application on the electronic device 312. Thus, the mobile test platform 304 may communicate with the electronic device 312 and configure the electronic device 312 to execute an application (e.g., a barcode application) that displays a barcode for a test task.

[0030] The coordinator 306 may act as a central component that manages tasks sent from the automated test tools 302. The coordinator 306 may generate a queue from the received tasks and assigns tasks to agents upon request by the agents. In some embodiments, the agents request tasks from the coordinator 306, which does not initiate communication with the agents. Thus, multiple agents can be easily added to the system, providing scalability and extensiveness. The coordinator 306 may include a user interface for user authentication and login, and an agent interface for agent-coordinator communication.

[0031] The agent 308 may retrieve tasks from the coordinator 306. Although only one agent is shown, the system may be implemented with multiple agents.

[0032] FIG. 4 is a diagram of a system for distributing test tasks according to one embodiment. In the embodiment shown in FIG. 4, a coordinator 400 may be in communication with a first test environment 402 at a first location and a second test environment 404 at a second location. The first test environment 402 may include an agent 406 in communication with the coordinator 400 and with a robotic device 410 and, in some embodiments, a set of electronic devices 412. The second test environment 404 may include an agent 408 in communication with the coordinator 400 and with a robotic device 420 and, in some embodiments, a set of electronic devices 422. A communication link between the agents 406 and 408 and the coordinator 400 (described in more detail below) allows multiple network environments to be easily added or removed as needed / desired.

[0033] The agents 308 may be configured to execute tasks retrieved from the coordinator 306. The agents 308 may be configured to communicate one-way with the coordinator 306 and periodically check if there are tasks in the coordinator's queue. The one-way communication structure allows for dynamic scaling of the system (i.e., easy addition or removal of agents) to support multiple electronic devices and multiple agents. The agents 308 may be configured to control the robotic devices 310 based on the retrieved tasks. The agents 308 may register themselves with the coordinator 306.

[0034] The communication link between the coordinator 306 and the agent 308 may include multiple API endpoints. The first API endpoint may include a registration endpoint that is the entry point for the agent, through which the agent 308 registers with the coordinator 306. If the registration is successful, the coordinator 306 adds the agent 308 to a list of registered agents.

[0035] The second API endpoint may include a request endpoint that serves as a sanity check: the agent 308 sends a one-way communication with the coordinator 306 (which may have a static uniform resource locator (URL)) to ask if the coordinator 306 currently has requests (i.e., the coordinator 306 has not initiated a call to the agent 308). If the coordinator 306 does not have enough requests from an agent, the coordinator 306 may assume that the agent is unavailable.

[0036] A third API endpoint may include a reporting endpoint. The agent 308 may send the results of a task to the coordinator 306. The agent 308 may also send the status or progress of a task to the coordinator 306 if the task is still running. For example, the agent 308 (or other software controlling the robotic device 310) may report to the coordinator 306 that the robotic device 310 has moved to a target device, scanned a barcode, etc. The agent 308 may report the completion percentage status of the task (e.g., 10% complete, 90% complete, etc.).

[0037] Each API endpoint may contain a different payload depending on the functionality of the API, for example, a request API endpoint may contain a barcode.

[0038] The robotic device 310 (or, in some embodiments, multiple robotic devices) may be configured to be controlled by the agent 308 (or other software) to perform the retrieved task. The robotic device 310 may have a scanner or scanning device attached to it or its arm that scans a barcode displayed on the electronic device 312. The robotic device 310 may be configured to scan multiple electronic devices. The robotic device 310 may include a physical slider or other movable structure (e.g., tracks, motion guidelines, motors, etc.) that allows the agent 308 to adjust the position of the robotic device 310 relative to the electronic device 312 so that the robotic device 310 can be properly aligned with the electronic device 312 to perform the task (e.g., scan a barcode displayed on the electronic device). The physical slider / movable structure may allow the robotic device 310 to move horizontally, vertically, and other directions (e.g., diagonally, rotationally, etc.).

[0039] The electronic device 312 may include one or more electronic devices capable of running task-subject application software and, in some embodiments, having a display capable of displaying a barcode to be scanned by the robotic device 310. The one or more electronic devices 312 may be positioned to be within a working range of the robotic device 310 such that the robotic device 310 can be aligned with the electronic device 312.

[0040] Backend servers 314 may include servers that host the backend of the application being tested.

[0041] 5A and 5B are diagrams of an operational flow of end-to-end mobile application testing according to an environment. The system may include a CI / CD pipeline 502, an automated test tool 504, a mobile test platform 506, a coordinator 508, an agent 510, a robotic device 512, and a backend server 514. FIGs. 5A and 5B show an example communication flow with one coordinator, one agent, and one robotic device. However, multiple coordinators, multiple agents, and multiple robotic devices may be implemented as described herein.

[0042] At operation 520, CI / CD 502 starts the test suite. At operation 522, automated test tool 504 sends instructions to mobile test platform 506 to install the application to be tested on the target electronic device (e.g., device N). If the installation is complete, mobile test platform 506 sends a success confirmation to automated test tool 504 at operation 524. At operation 526, automated test tool 504 sends instructions to mobile test platform 506 to launch the installed application on device N. At operation 528, if the launch is successful, mobile test platform 506 sends a success confirmation to automated test tool 504.

[0043] In operation 530, the automated test tool 504 sends a request to the coordinator 508 to create a scan task. In operation 532, the coordinator 508 creates the scan task. In operation 534, the agent 510 queries the coordinator 508 about the task. Operation 534 may loop. When there is a task to be retrieved by the agent 510, in operation 536, the agent 510 sends a command to the robotic device 512 to execute the task.

[0044] In operation 538, the agent 510 checks the robotic device 512 whether the task is complete, and in operation 540, the robotic device 512 sends the task status to the agent 510. Operations 538 and 540 may loop until the task is complete. In operation 542, if the task is complete, for example, the agent 510 requests the barcode value (i.e., the result of the task) to be obtained by the robotic device 512. In operation 544, the robotic device 512 sends the barcode value to the agent 510. In operation 546, the agent 510 sends the barcode value to the coordinator 508. In operation 548, the coordinator 508 sends the barcode value to the automated test tool 504. In operation 550, the automated test tool 504 sends the barcode value to the backend server 514. At operation 552, after the backend server 514 determines the results of the tests, the backend server 514 sends those test results (i.e., success or failure) to the automated testing tool 504. At operation 554, the automated testing tool 504 indicates to the CI / CD pipeline that testing for the task is complete.

[0045] 6A and 6B are diagrams of a mobile application testing environment according to one embodiment. The testing environment includes a robotic device 602, a scanning device 604 attached to the robotic device, a number of electronic devices 606, and a moving track 608. An agent (or other software) can be configured to control the robotic device 602. When the agent picks up a task to test an electronic device 610, the agent can control the robotic device 602 to move along the moving track 608 from a first position shown in FIG. 6A to a second position shown in FIG. 6B to align the scanning device 604 with the electronic device 610 so that the robotic device 602 can scan a barcode displayed on the electronic device 610.

[0046] 7 is a flow chart of a mobile application testing method according to an embodiment. In operation 702, the system may receive a task for testing at least one electronic device from the coordinator unit by the coordinator unit. In operation 704, the system may retrieve a task for testing at least one electronic device from the coordinator unit by the first agent. In operation 706, the system may control the first robotic device to test the at least one electronic device based on the retrieved task. In operation 708, the system may receive a result of the task based on the testing of the at least one electronic device from the coordinator unit by the coordinator unit.

[0047] Additional aspects may be implemented in the end-to-end testing process disclosed herein. For example, a robotic device may be equipped with multiple scanners to test variations of the scanner against a displayed barcode. The robotic device may be configured to be controlled by an agent to swap scanners attached to the robotic device based on a retrieved task.

[0048] In further embodiments, the agent retrieving the task may further determine whether the agent can perform the task based on its corresponding test environment. As described above, based on location or other conditions, the electronic device may include various characteristics that can only be tested in a particular test environment (e.g., the location of the electronic device, the lighting of the area where the electronic device is located, the brand of the electronic device, the brightness of the screen of the electronic device, etc.). The generated task may include a task to test electronic devices having specific characteristics, and the agent may determine whether any of the electronic devices in the corresponding test environment include those characteristics to be tested. The agent may accept the task when the test environment includes electronic devices that can be tested based on the task's specific characteristics, and the agent may reject the task when the test environment does not include electronic devices or does not include a sufficient number of electronic devices required to complete the task. In one example, the task may be to test electronic devices of a specific brand and / or model of electronic device. The agent may retrieve the task and then determine whether any of the electronic devices are of a specific brand and / or model of electronic device. The agent may then accept or reject the task based on this determination.

[0049] Additionally, in some embodiments, the test environment may be configured to simulate conditions. For example, the test environment may be configured to simulate ambient lighting conditions, scanning angles of the scanner, resting angles of the device, and brightness settings of the device. Additionally, the test environment may be provided with monitoring equipment that performs real-time monitoring of the test environment. Inventory management of devices, their capabilities and settings, and application versions may be centralized. Additionally, the coordinator may provide a dashboard or interface for interacting with the test environment and the entire system.

[0050] Additionally or alternatively, hard-wired circuitry may be used in place of or in combination with software instructions to implement one or more of the processes described herein. Thus, the embodiments described herein are not limited to any specific combination of hardware circuitry and software.

[0051] The above disclosure provides illustration and description, but is not intended to be exhaustive or to limit the implementation to the precise form disclosed, as modifications and variations are possible in light of the above disclosure or may be acquired from practice of the implementation.

[0052] Some embodiments may relate to systems, methods, and / or computer-readable media at any possible level of technical detail integration. The computer-readable media may include a computer-readable non-transitory storage medium (or media) having computer-readable program instructions recorded thereon that cause a processor to perform operations.

[0053] A computer-readable storage medium may be a tangible device capable of holding and storing instructions for use by an instruction execution device. A computer-readable storage medium may be, for example, but not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination thereof. A non-exhaustive list of more specific examples of computer-readable storage media includes the following: portable computer diskettes, hard disks, random access memories (RAMs), read-only memories (ROMs), erasable programmable read-only memories (EPROMs or flash memories), static random access memories (SRAMs), portable compact disk read-only memories (CD-ROMs), digital versatile disks (DVDs), memory sticks, floppy disks, punch cards, or mechanically encoded devices such as protruding structures in grooves with instructions recorded thereon, and any suitable combination thereof. As used herein, computer-readable storage media should not be construed as transitory signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating in a waveguide or other transmission medium (e.g., light pulses through a fiber optic cable), or electrical signals transmitted in wires.

[0054] The computer readable program instructions described herein may be downloaded from a computer readable storage medium into each computing / processing device, or may be downloaded to an external computer or external storage device via a network, such as the Internet, a local area network, a wide area network, and / or a wireless network. The network may include copper transmission cables, optical transmission fiber, wireless transmission bodies, routers, firewalls, switches, gateway computers, and / or edge servers. A network adapter card or network interface in each computing / processing device receives the computer readable program instructions from the network and transfers these computer readable program instructions to storage in a computer readable storage medium within the respective computing / processing device.

[0055] The computer readable program code / instructions for carrying out the operations can be either assembler instructions, instruction-set-architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, state setting data, configuration data for an integrated circuit, or source or object code written in any combination of one or more programming languages. Programming languages ​​include object-oriented programming languages ​​such as Smalltalk, C++, and procedural programming languages ​​such as the "C" programming language or similar programming languages. The computer readable program instructions may run in whole or in part on the user's computer as a standalone software package, or may run in part on the user's computer and in part on a remote computer, or may run in whole on a remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or this connection may be made to an external computer (e.g., through the Internet using an Internet Service Provider). In some embodiments, electronic circuitry including, for example, a programmable logic circuit, a field programmable gate array (FPGA), or a programmable logic array (PLA) may execute computer readable program instructions by personalizing portions of the electronic circuitry using state information of the computer readable program instructions to perform an aspect or operation.

[0056] These computer-readable program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine such that the instructions, executed by the processor of the computer or other programmable data processing apparatus, create means for implementing the functions / acts specified in one or more blocks of the flowcharts and / or block diagrams. These computer-readable program instructions may be stored on a computer-readable storage medium capable of directing a computer, programmable data processing apparatus, and / or other device to function in a particular manner. In a particular manner, the computer-readable storage medium on which the instructions are stored may be such that it constitutes an article of manufacture including instructions implementing aspects of the functions / acts specified in one or more blocks of the flowcharts and / or block diagrams.

[0057] The computer readable program instructions may be loaded onto a computer, other programmable data processing apparatus, or other device and may generate a sequence of operational steps to be performed on the computer, other programmable apparatus, or other device as a computer-implemented process, where the instructions executing on the computer, other programmable apparatus, or other device perform the function(s) / act(s) specified in the flowchart and / or block diagram block(s).

[0058] The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer-readable media according to various embodiments. In this regard, each block in the flowcharts or block diagrams may represent a module, segment, or portion of instructions that includes one or more executable instructions to implement the specified logical function(s). These methods, computer systems, and computer-readable media may include additional, fewer, different, or differently arranged blocks than those shown in the figures. In some alternative implementations, the functions shown in the blocks need not be performed in the order shown in the figures. For example, two blocks shown in succession may in fact be executed simultaneously or nearly simultaneously, depending on the functionality involved, or the blocks may sometimes be executed in the reverse order. It should also be noted that each block of the block diagrams and / or flowchart illustrations, as well as combinations of blocks in the block diagrams and / or flowchart illustrations, may be implemented by a dedicated hardware-based system that executes the specified functions or operations, or a dedicated hardware-based system that executes a combination of dedicated hardware and computer instructions.

[0059] It is apparent that the systems and / or methods described herein may be implemented in different forms of hardware, firmware, or a combination of hardware and software. The actual specialized control hardware or software code used to implement these systems and / or methods does not limit the implementation of s. Thus, the operation and behavior of the systems and / or methods are described herein without reference to specific software code. That is, it is understood that software and hardware can be designed to implement the systems and / or methods based on the description herein.

[0060] No element, act, or instruction used herein should be construed as essential or required unless expressly stated otherwise. Additionally, as used herein, the articles "a" and "an" are intended to include one or more items and may be used interchangeably with "one or more." Additionally, as used herein, the term "set" is intended to include one or more items (e.g., related items, unrelated items, a combination of related and unrelated items, etc.) and may be used interchangeably with "one or more." When only one item is intended, the term "one" or similar language is used. Additionally, as used herein, the terms "having" and the like are intended to be open-ended terms. Additionally, the term "based on" is intended to mean "based at least in part on" unless expressly stated otherwise.

[0061] The description of various aspects and embodiments is presented for illustrative purposes and is not intended to be exhaustive or to limit the disclosed embodiments. Although combinations of features are recited in the claims and / or disclosed herein, these combinations are not intended to limit the disclosure of possible implementations. Indeed, many of these features can be combined in ways not specifically recited in the claims and / or specifically disclosed herein. Although each dependent claim recited below may directly depend on only one claim, the disclosure of possible implementations includes each dependent claim combined with every other claim in the set of claims. Many modifications and variations will be apparent to those skilled in the art without departing from the scope of the described embodiments. The terms used in this specification are selected to best explain the principles of the embodiments, practical applications or technical improvements beyond the technology found in the market, or to enable other skilled in the art to understand the embodiments disclosed herein.

Claims

1. receiving, by a coordinator unit, a task to test at least one electronic device having at least one characteristic related to a test environment; retrieving, by a first agent, the task of testing the at least one electronic device from the coordinator unit; controlling a first robotic device to test the at least one electronic device based on the retrieved task; receiving, by the coordinator unit, a result of the task based on the testing of the at least one electronic device; the at least one characteristic includes a characteristic of lighting in an area in which the electronic device is located; retrieving the task for testing the at least one electronic device includes accepting the task when the first agent determines that a set of electronic devices corresponding to the first agent includes an electronic device having the at least one characteristic related to a test environment for the task. method.

2. The method of claim 1 , wherein the task of testing the at least one electronic device includes a scan task of scanning a barcode generated by an application installed on the at least one electronic device.

3. the first robotic device comprises a scanner; controlling the first robotic device includes aligning the scanner of the first robotic device with the barcode displayed on the at least one electronic device. The method of claim 2.

4. aligning the scanner of the first robotic device includes sliding the first robotic device from a first position in which the first robotic device is not aligned with the barcode to a second position in which the first robotic device is substantially aligned with the barcode. The method according to claim 3.

5. The method of claim 2 , wherein the result of the task includes a barcode value generated by scanning the barcode.

6. The method of claim 1, further comprising generating the task for testing the at least one electronic device based on at least one characteristic related to the test environment.

7. and rejecting the task of testing the at least one electronic device based on a determination, by the first agent, that no electronic device in the set of electronic devices corresponding to the first agent includes the at least one characteristic related to a testing environment for the task. The method of claim 1.

8. The method of claim 1 , wherein the at least one characteristic comprises a location of the electronic device, lighting in an area in which the electronic device is located, a brand of the electronic device, a model of the electronic device, or a brightness of a screen of the electronic device.

9. A memory for storing instructions; A processor configured to execute the instructions, instructions for receiving, using a coordinator unit, a task for testing at least one electronic device having at least one characteristic related to a test environment; instructions for retrieving, by a first agent, the task of testing the at least one electronic device from the coordinator unit; instructions for controlling a first robotic device to test the at least one electronic device based on the retrieved task; receiving, using the coordinator unit, results of the tasks based on the tests of the at least one electronic device; A processor configured to execute Equipped with the at least one characteristic includes a characteristic of lighting in an area in which the electronic device is located; the instructions for retrieving the task from the coordinator unit include instructions for accepting the task when it is determined by the first agent that a set of electronic devices corresponding to the first agent includes an electronic device having the at least one characteristic related to a test environment of the task. system.

10. 10. The system of claim 9, wherein the task of testing the at least one electronic device includes a scan task that scans a barcode generated by an application installed on the at least one electronic device.

11. the first robotic device comprises a scanner; the processor is further configured to control the first robotic device by aligning the scanner of the first robotic device with the barcode displayed on the at least one electronic device. The system of claim 10.

12. the processor is further configured to align the scanner of the first robotic device by sliding the first robotic device from a first position, in which the first robotic device is not aligned with the barcode, to a second position, in which the first robotic device is substantially aligned with the barcode. The system of claim 11.

13. The system of claim 10 , wherein the result of the task includes a barcode value generated by scanning the barcode.

14. 10. The system of claim 9, wherein the processor is further configured to generate the tasks for testing the at least one electronic device based on at least one characteristic related to the test environment.

15. 10. The system of claim 9, wherein the processor is further configured to reject the task of testing the at least one electronic device with the first agent based on a determination that no electronic device in the set of electronic devices corresponding to the first agent includes the at least one characteristic related to a test environment for the task.

16. The system of claim 9 , wherein the at least one characteristic comprises a location of the electronic device, lighting in an area in which the electronic device is located, a brand of the electronic device, a model of the electronic device, or a brightness of a screen of the electronic device.

Citation Information

Patent Citations

  • General-purpose automated testing of embedded systems

    JP2020501221A