KR20180021927A - Robotic device tester - Google Patents

Abstract

The present invention provides software that simplifies and expedites the configuration of a test system to test the device and improve the test procedures performed, and provides data that easily identifies the cause and nature of the resulting error during testing Hardware, and the like. The camera captures a still image on the display screen of the device under test and another camera captures a video image of the device under test and the partner device. A wizard is used to create a configuration file based on what was previously generated on a similar device. A mounting portion for the device under test can be configured to suitably mount a plurality of differently configured devices thereon and to easily adjust the vertical and horizontal orientations on the plane and the angle of the device relative to the plane have.

Description

[0001] ROBOTIC DEVICE TESTER [0002]

This application is related to US Provisional Patent Application No. 61 / 046,355, entitled " Robotic Device Tester ", filed on April 18, 2008, and entitled " U.S. Patent Application No. 12 / 239,271, filed on March 26, 2006, the contents of which are incorporated herein by reference in their entirety.

The present invention relates to a robotic device tester and a device testing method using the robot.

BACKGROUND OF THE INVENTION Many devices, especially portable communication devices such as mobile phones, are being produced and updated in large numbers. Each of these devices can be used for the production of new devices or new software for use in current devices or new devices, prior to mass production and sale, and during development and design of new devices and after development and design, For example.

The conventional test system exposes the internal interface of the device under test and accesses the interface in order to simulate the operation of the device according to the preset test sequence that has been input. However, the operation of such a test system is insufficient because it does not accurately reflect how the device is ultimately used, i. E., By pressing a button or by the operation of other input hardware such as a scroll bar, wheel or joystick. Also, in the event of a failure, for example, if a failure occurs during an unattended long-term test, the operator must make a difficult decision on the correct failure or reason, for example for troubleshooting. Moreover, with respect to the device, since the communication from the device under test is not known at the receiving device to be transmitted during the test, and since the communication from the other device can not be received by the device under test, It is incomplete.

Another conventional test system provides a robotic arm to push a button to simulate the use of a device under test. A screen shot or short video of the device under test during the test process, which can help in troubleshooting, can be captured by the camera. However, even such devices are insufficient because they can not determine the results at other receiving devices and can not test the function of the device under test when receiving communications from other communication devices.

Moreover, conventional test systems require verbose and detailed configuration and calibration for each of the test target devices. This results in severe inconvenience when the first device under test is removed from the test system to fix, for example, minor defects, and then returned to the test system after testing the second device under test, This is because the initial test of one device must be in the following state. This situation requires a second configuration of the test system for the second test of the first device under test.

It is an object of the present invention to provide a robotic device tester that provides improved device test performance and a device test method using the robot.

Embodiments of the present invention provide an apparatus, system, and method for solving each of the problems described above with respect to a conventional device test system. Embodiments of the present invention can be applied to both hardware and software stress testing methods. The device test system may include a robotic arm for operating a device under test and may include a second test to communicate with the device under test, including initiating a call to the device under test or communicating a message to the device, Lt; RTI ID = 0.0 > device. ≪ / RTI > The first camera is provided to record a snapshot of the display screen of the device under test and the second camera is provided to capture a video of the device under test and the second untested device within the visual range as a whole.

This function is a major use of the first camera and the second camera. In variants, however, both of these cameras capture a snapshot, or both snapshots and video. In another variation, the first camera captures video while the second camera captures a snapshot.

A wizard may be included to facilitate rapid configuration of the test system for each device under test. The wizard refers to a set of pre-stored input test scenarios to be applied to various test target devices. The wizard also creates a new combination of some or all of the configuration files associated with the new test target device, with reference to the configuration files associated with the previously tested device. The newly created configuration files with respect to the new test target device may also be changed to customize the files for the features of the new test target device.

The configuration of the test system includes three-dimensional coordinate records for each button or one or more buttons of the device under test or other input means such as, for example, a joystick, trackball, thumwheel, switch, The two coordinates represent the two-dimensional position of the input device on the plane of the device under test. The third coordinate may be used to register the operation in a state in which the test target device registers the operation of the input device, for example, the plane of the input device or the test target device is not excessively extended due to too hard pressing of the button, For example, in a direction orthogonal to the two-dimensional plane. In the input device of the device under test, in which three-dimensional coordinates must be recorded, after the coordinates representing the two-dimensional plane are input, the device test system compares the coordinates obtained from the force sensor during movement of the robot arm in a direction orthogonal to the input plane The coordinates of the third dimension are automatically determined and recorded based on the signal.

The device test system includes a single main workstation that performs test configuration and performs subsequent tests. The device test system may also include a second workstation that is less complex than the main workstation, for example by omitting some hardware or software, such as the abbreviation of a robot arm. According to this embodiment, some configuration of the device test system for testing the device under test may be performed using a less complex second workstation. This is because not a main test location where the main workstation is located can provide flexibility for a group of workers to work together in a separate location, e.g., in a distributed location such as each desk or house, helpful. It may be required to perform some configuration steps using the main workstation. Following this configuration, portions of the device under test may be moved to the main workstation for testing in accordance with this configuration, and some of these tests may be done at a second location.

According to an exemplary embodiment of the present invention, for each test target device in which the device test system is configured, a unique code is stored. The code may be associated with configuration files to be used during testing of the device under test. At any time, the device test system can be reconfigured for previously tested devices by entering the code. Moreover, each of the codes can be encoded in the form of a bar code, so as to perform quick reconstruction without any user input. A barcode may be displayed on the attachment or each device under test attached during the test of the device. At the start of the sequence of test procedures, the camera of the test system captures an image of the device under test and / or the fixture and displays the image of the test system in a database or other file structure, Matches the barcode, and automatically loads the configuration associated with the imaged barcode.

According to an exemplary embodiment of the present invention, the fastening device of the device under test includes an attachment plate having a middle lip extending therethrough and a lip on either side of the intermediate lip, Some extend along at least a portion of the middle aperture. The fixture of the device under test further comprises a base comprising a wide base and a narrow base on the broad base, wherein the broad base extends under at least two lips and the narrow base extends between at least two lips . The device securing device further comprises a first vertical plate extending upward from a surface of the narrow base parallel to the surface of the attachment plate extending through the two long holes and the intermediate hole, From its surface, at least two holes extending in a direction perpendicular to the direction in which the first vertical plate extends from the narrow base. The fixing device of the device under test further includes a second vertical plate having a curved hole extending through the second vertical plate and having at least two Wherein the second vertical plate is slidably connectable to the first vertical plate through a coupling into at least two holes of the two fixtures and the second vertical plate is slidably coupled to the first vertical plate when the second vertical plate is coupled to the first vertical plate, And a structure extending from the surface of the second vertical plate parallel to the surface of the narrow base on which the plate extends and having a predetermined shape. The fixing device of the device under test further includes a mounting plate, and the mounting plate includes a second vertical plate that is slidably received in the first hole of the mounting plate to connect the second vertical plate to the mounting plate A first hole of a shape corresponding to the shape of the structure;

At least one second vertical plate extending from the surface of the mounting plate perpendicular to the first hole and a surface of the narrow base on which the first vertical plate extends when the mounting plate is coupled to the second vertical plate and the second vertical plate is coupled to the first vertical plate, And the engagement of the mounting plate with respect to the second vertical plate is achieved by tightly inserting at least one fixture through the at least one second hole into the structure of the second vertical plate extending through the first hole.

In an exemplary embodiment, the fixture of the device under test further comprises a base plate, said base plate having a plurality of holes extending from a surface of the base plate, said attachment plate extending through the attachment plate Wherein each of the elongate holes is located on each of opposite opposite sides of the mounting plate and the middle hole extends between the two elongated holes, wherein the mounting plate comprises a narrow base Through a coupling into two of the plurality of holes of the two respective fasteners each extending through each of the two long holes in a direction perpendicular to the surface of the fastener.

In an exemplary embodiment of the fixture of the device under test described above, the configuration of the structure is a long T shape.

As yet another variation of the exemplary embodiment just described, at least one second hole includes three holes.

In an exemplary embodiment, the fixture of the device under test further comprises an adhesive on the surface of the mounting plate perpendicular to its surface, wherein at least one second hole of the mounting plate extends from the surface, When connected to the vertical plate and the second vertical plate is connected to the first vertical plate, the mounting plate is parallel to the surface of the narrow base on which the first vertical plate extends.

An embodiment of the present invention is a camera system including a first camera having a first field of view and a first axis corresponding to the first field of view, a second camera having a second field of view wider than the first field of view, and a second axis corresponding to the second field of view, A memory for storing data of the first camera and the second camera, a platform supporting a tested portable communication device and a partner communication device, wherein at least a portion of the display screen of the tested portable communication device Wherein the first axis is perpendicular to the display screen of the tested portable communication device and the second axis is a platform that is not perpendicular to the display screen, the input hardware of the tested portable communication device And the tested portable communication device is mounted on the platform Wherein the input hardware operation of the tested portable communication device causes the tested portable communication device to communicate with the partner communication device, To compare the images received from the first camera with data of the first camera and the second camera during operation of the tested portable communication device and to determine whether an error has occurred based on the comparison And to cause the memory to store images received from the second camera of the tested portable communication device during the period in which the error occurred.

In this embodiment, the second field of view of the second camera may include all of the display screen of the tested portable communication device.

In this embodiment, the display screen of the tested portable communication device may be more focused by the first camera compared to the second camera and may be illuminated at a higher resolution.

In this embodiment, the determination that the error has occurred may be based on an optical character reading (OCR) of one or more images of the display screen of the tested portable communication device.

In this embodiment, the tested portable communication device may be located laterally displaced from the second axis extending through the display screen of the tested portable communication device through the lens of the second camera.

In this embodiment, at least one of the first camera and the second camera is initially configured to acquire a reference image and the processor processes the reference image to identify a test sequence, and in accordance with the test sequence, A robotic arm may be configured to operate the tested portable communication device.

In this embodiment, the processor may be configured to activate at least one light at a plurality of illumination levels while at least one of the first camera and the second camera is operating.

In this embodiment, the processor is configured to identify at least one of a position and a boundary of the display screen of the tested portable communication device based on a difference between light generated by the display screen and ambient light .

In this embodiment, the system may further include a compartment for receiving the tested portable communication device, the first camera, the second camera, the platform, and the robotic arm.

In this embodiment, the tested portable communication device may be fixedly mounted to the platform to be provided in the same initial position for each test.

Another embodiment of the present invention is a computer readable medium executed by hardware having stored program instructions for causing a processor to perform a method of testing a first portable communication device when executed, Operating the first portable communication device and the second portable communication device in accordance with test sequences to cause the communication device to communicate with the second portable communication device; Capturing an image of at least one of a first portable communication device and a second portable communication device using a second camera having a field of view greater than the field of view of the first camera, Capturing an image, Comprising: comparing an image captured by the first camera with a reference image; determining if an error has occurred based on comparing the image captured by the first camera with a reference image; and determining, And storing an image captured by the second camera of the first portable communication device during the period in which the determined error occurred, wherein the first portable communication device is provided on a platform, The second axis extending through the lens of the first camera and extending perpendicularly through the platform and the second axis extending through the lens of the second camera and at an angle not perpendicular to the platform.

In this embodiment, the determination of the occurrence of the error may be based on optical character reading (OCR) of the image on the display screen of the first portable communication device.

In the present embodiment, the first portable communication device may be positioned by moving a display screen of the first portable communication device laterally from the second axis extending through the lens of the second camera.

In this embodiment, at least one of the first camera and the second camera is initially configured to acquire an image, and the method further comprises processing the acquired image to identify a test sequence .

In the present embodiment, the method may further comprise operating at least one light at a plurality of illumination levels while at least one of the first camera and the second camera is operating.

In this embodiment, the method further comprises identifying at least one of a position and a boundary of the display screen based on the difference between the light generated by the display screen of the first portable communication device and the ambient light .

In the present embodiment, the first portable communication device may be fixedly mounted to the platform to be provided in the same initial position for each test.

According to the present invention, a robotic device tester capable of providing improved device test performance and a device testing method using a robot can be obtained.

1 is a schematic diagram showing components of a system according to an embodiment of the present invention.
2 is a schematic view showing a robot arm and a plate according to an embodiment of the present invention.
Figures 3 and 4 illustrate embodiments in which the device under test and the partner device are closely spaced during testing.
FIG. 5 illustrates components of a base plate of a barcode and a fixture of a device under test according to an embodiment of the present invention.
Figure 6 shows the components of a robot according to an embodiment of the present invention.
Fig. 7 shows the components of a device fixing apparatus in a disassembled state according to an embodiment of the present invention.
FIG. 8 shows the fastening device of the device of FIG. 7 assembled in accordance with an embodiment of the present invention.
Figure 9 shows a post used to prevent distortion of a device under test, according to an embodiment of the present invention.
10 is a schematic diagram illustrating a mini-workstation, in accordance with an embodiment of the present invention.
11 is a screen shot showing an exemplary file structure of configuration files according to an embodiment of the invention.
12 is a cross-functional flowchart illustrating a method of testing a device, including generating and testing configuration files according to an embodiment of the present invention.
13 is a flow diagram illustrating a method for generating a partial configuration file, e.g., in a mini-workstation, in accordance with an embodiment of the present invention.
14 is a flowchart showing a method of completing a configuration file according to an embodiment of the present invention.

1A shows a device test system 1 according to an example of the present invention. The device test system includes a compartment 100 that houses a robot 102, a platform 104, a user terminal 105, a lighting device 110, and a camera device 111. The robot 102 may include an arm 103 for operating the device 115 to be tested. As used herein, the term " test target device " refers not only to a device currently under test but also to a device capable of configuring the test system 1 to perform a test on the device. However, in a particular context, the device under test 115 will be described as the device under test.

The compartment 100 may be completely enclosed during the test and / or test system 1 configuration of the device under test 115 so that illumination can be controlled at an optimum level in various stages of configuration and / or testing .

The platform 104 includes an attachment point for attaching the securing device 114 of the device, to which the device under test can be securely mounted, e.g., with an adhesive. The platform 104 may include, for example, recesses and pegs extending from the underside of the device securing device 114 may be inserted into the recesses and the device securing device 114 may be mounted Ensures that the device securing device 114 can be placed in the same position relative to the robot 102 every time the device securing device 114 is placed for testing of the device 115 under test.

During the construction and / or testing, the plane of the device under test 115 including the display screen is perpendicular to the direction of extension of the arm 103 towards the platform 104 to operate the device under test 115, A device under test 115 is placed for the device test system. In the device under test 115, a portion including most of the user-operable input devices, such as a keypad, for example, is connected in a hinge manner to a portion including the display screen, The keypad portion is disposed at an angle less than or greater than 180 degrees with respect to the display screen portion so that the keypad portion can be positioned in a direction perpendicular to the plane of the platform 104 to manipulate the various buttons of the device under test 115 It may actually be required to extend the arm 103 to various positions.

The arm 103 is attached to the body of the robot 102 such that the arm 103 can be displaced laterally from the vertical axis of the robot 102 body through the arm plate 140, do. Such a displacement provides a better image for the device under test 115 to the camera of the camera device 111 during configuration and / or testing.

As shown in FIG. 1B, the camera device 111 includes a first camera 113 and a second camera 112. In an embodiment of the invention, the second camera 112 is at an angle such that an axis extending vertically through the lenses extends at an angle that is not perpendicular to the platform 104, 115 of the second embodiment. The display screen of the device under test 115 may be laterally displaced toward the platform 104 from an extended axis passing vertically through the lenses of the second camera 112. [ In addition, the portion 115a of the device under test 115, including the display screen, may be at an angle other than 90 degrees with respect to the axis extending through the lenses of the second camera 112. [

In an embodiment of the present invention, the first camera 113 is disposed substantially parallel to the surface of the display screen of the device under test 115, with the lenses being substantially parallel to the platform 104. The camera 113 and the device under test device fixing device 114 are arranged such that the axis extending vertically through the lenses of the camera 113 extends substantially vertically through the display screen of the device under test 115, For example, extend through the center of the display screen. Thereby, the display screen of the device under test 115 is irradiated with a larger resolution by the first camera 113 than by the second camera 112 and more focused, so that the second camera 112 While the first camera 113 records an image, e.g., a moving image, of the entirety of the device under test 115, the display screen may be configured such that the display screen can be processed by image recognition software, including, for example, optical character reading (OCR) Record images that are more clearly depicted. In the exemplary embodiment, the zoom setting of the first camera 113 causes the display screen to include all or almost all of the view of the first camera 113.

The device fixation device 114 may include a device under test 115 and a partner device 116 located proximate to the device under test 115 as illustrated in the two exemplary embodiments of Figures 3 and 4, And the partner device 116 itself can serve as a device under test and may be tested during various test operations of the test system 1. [ The camera 112 can be placed and the settings of the camera can be configured such that the device 115 under test and the partner device 116 are located within the field of view of the camera 112, The generated images are for both the test target device 115 and its partner device 116 at the same time.

The user terminal 105 includes a processor 106, a memory 107, a display 108 and an input device 109. [ The processor 106 includes any suitable conventional processing circuitry that may be embodied in any conventional manner, such as a central processing unit (CPU) of a personal computer (PC). The memory 107 may be any suitable conventional memory device such as a random access memory (RAM), a read only memory (ROM), a hard disk, a magnetic tape, a compact disc (CD), a flash memory based device, and / . The memory 107 is coupled to the processor 106 to perform various functions described herein for configuration and operation of the test system 1 and operation of the partner device 116 in the manner of the various embodiments described herein. Lt; RTI ID = 0.0 > executable < / RTI >

In an embodiment of the present invention, the processing circuit includes a robot controller PC and a test execution PC (TEPC), wherein the two PCs are connected to the station's Ethernet switch and communicate over the local network. The TEPC sends the button input signal and other commands to the robot controller PC, which includes software to receive and operate the commands. The display and input devices are common to both TEPC and robot controller PCs and are connected by a KVM switch.

The test target device 115 and the partner device 116 may each be a communication device such as a mobile phone. The processor 106 may be connected to the partner device 116 via a communication / control interface, such as, for example, a serial interface of the partner device 116. In an exemplary embodiment, the partner device is connected to the TEPC. While testing the device under test 115, it is possible to execute partner device instructions 120 in memory 107 that are part of the instruction 120 in a portion of the memory 107 that the TEPC processor is accessing, The processor 106 may input commands to the partner device 116 via the serial interface of the partner device 116. [ The command simulates the operation of the input hardware of the partner device 116, which allows the partner device 116 to transfer the communication to the device 115 to be tested.

In an embodiment of the invention, processor 106, such as, for example, TEPC, may also intercept data of partner device 116, which is used to generate a display on the display screen of partner device 116. [ During testing of the device under test 115, when the device under test 115 is enabled to communicate communications to the partner device 116, the processor 106, e.g., the TEPC, analyzes the intercepted data from the partner device 116 The memory 107 is compared with the intercepted data stored in, for example, the TEPC memory to determine whether a suitable result for the expected communication from the device under test 115 has been obtained. If the result is not expected, the processor 106 determines that an error has occurred. Likewise, during a portion of the test of the device under test 115, if the device under test 115 does not communicate with the partner device 116, the processor 106, e.g., the TEPC, If intercepted, it is determined that an error has occurred.

In an embodiment of the present invention, processor 106, e. G. TEPC, is connected to cameras 112 and 113. The processor 106, e. G. TEPC, receives the image sensed by the sensor of the camera 113 capturing the light through the lenses of the camera 113. The processor 113, The processor 106, e.g., the TEPC, can execute the image processing software 121 to compare the image received from the camera 113 with the image of the display screen image collection 122 stored in the memory of, for example, TEPC, ) Matches the images in the collection 122 stored in the TEPC memory, for example. For example, for each of the images of the collection 122 stored in the memory of the TEPC, the collection 122 identifies the particular individual operation (s) of the device under test 115 associated with the image. For each identified one or more actions, when the robot 102 performs the identified action (s), the processor 106, e. G., The TEPC, determines the action (s) associated with the performed action (s) Immediately after the execution, the images captured by the camera 113 are compared.

The camera 112 also provides an image to the user terminal 105 while the camera 113 provides the image to the user terminal 105. [ The images provided by the camera 112 are moving images, i.e. moving images. The moving image is stored in, for example, a buffer of memory 107 of TEPC. In response to a determination by the processor 106 that an error has occurred, e.g., TEPC, the processor 106, e.g., a TEPC, passes a plurality of images of the buffer to a permanent memory location, Images can be played. In an embodiment of the present invention, the delivered images include a time period beginning immediately before an error occurs and ending immediately after an error has occurred.

In an embodiment of the present invention, the buffer is configured as a first-in-first-out (FIFO) memory and can only maintain a small number of images. Once full, for each newly received image, the FIFO image received prior to all other images in the FIFO is deleted and the newly received image is written to the FIFO. In an exemplary embodiment, all of the images in the FIFO or images obtained in video form are transmitted to be permanently stored upon error detection. Alternatively, the number of images of the temporary memory transferred to be permanently stored is based on a preset number or a predetermined time interval from which the configuration of the processor 106, e.g., TEPC, is made. Note that, for example, when the frame capture rate of the camera 112 changes, the number of recorded image frames representing the time interval may also vary. Alternatively, all images are stored in files on a local disk. In error detection, multiple images can be stored in separate memory locations to review the errors. In yet another alternative, all images are stored as temporary files, which are deleted if no errors occur and permanently stored if errors are detected. As described with respect to these embodiments, the persistent storage conditions for images at the time of error detection do not save the full length video for all processes, e.g. from test start to end, do.

In an embodiment of the present invention, for example, the memory 107 of the TEPC includes a configuration file database 123, which is stored in a respective configuration file for each test target device 115 in which the test system 1 is configured Or a folder. In an embodiment of the present invention, the configuration of the test system 1 for the location of the input hardware controlled by the robot 102 during the test, and the tasks performed during testing of the device, The same test target device 115 shares the same configuration file or folders. In an exemplary variation, regardless of whether the features are similar or not, the two test target devices, such as phones, do not share the same configuration file, and each test target device has its own configuration file / folder structure. For each different configuration file or folder, a unique code may be generated by the processor 106. Alternatively, a separate PC outside the robotic station generates and / or prints the code. The code can be coded, for example, as a bar code. In an embodiment of the present invention, a code such as, for example, a bar code may be placed in the device under test 115 or in the device fixation device 114. 5 shows that the bar code 500 is arranged on the device fixing device 114 near the test target device 115 with respect to the axes extending vertically through the lenses of the camera 112 so that the device fixing device 114 The barcode 500 is in the field of view of the camera 112 when installed in the platform 104 of the test site.

In the initialization of the test system 1 performing the test, the processor 106, e.g., a TEPC, activates the camera 112 to acquire an image. A processor 106, such as a TEPC, for example, that executes image processing software 121 stored in the TEPC, detects the barcode 500 in the acquired image, processes the barcode 500 to read the code, Compares the code set stored in the memory 107 with the code, selects a configuration file or a folder associated with the code, starts the operation of the robot 102 according to the configuration parameters contained in the configuration file or folder, Or an outlined test sequence in a folder.

According to another exemplary embodiment, when the barcode is not detected, the processor 106, e.g., a TEPC, may cause an error message to be output on the display 108, or a user may be manually input a code via the input device 109 , Or outputs a message requesting the user to start a process for creating a new configuration file or a folder. In an embodiment of the present invention, processor 106, e.g., a TEPC, indicates whether a barcode is not included (or an embedded barcode is not recognized) and whether a configuration file exists that may be used for the installed device 115 An error message may be displayed requesting an input indicating whether or not an error has occurred. When the user indicates that the configuration file is present, he prompts the user to input the code. If the user indicates that the configuration file is not yet available, the user may be prompted to start the process for the creation of the configuration file or folder.

In an exemplary variation, the user is prompted to create a configuration file or folder only if (a) no barcode is found, or (b) there is a barcode but no configuration data for that phone. The user is not prompted for the existence of a configuration file because it programmatically decides it.

In an embodiment of the invention, the illumination device 110 may comprise, for example, light emitting diodes (LEDs), for example two LEDs. In an embodiment of the invention (not shown), the lighting device 110 is two independently controllable lighting devices, one each on each side of the cameras, each lighting device comprising approximately six LEDs. The illumination device 110 is configured to generate a plurality of levels of light. A processor 106, such as a TEPC, is connected directly or indirectly to a lighting device 110 and is coupled to a lighting control program 124, e.g., a TEPC lighting control program 124, to change the lighting level generated by the lighting device. To control the lighting device 110 according to the lighting conditions.

In particular, the illumination device 110 may be configured to generate light at two different illumination levels. When initializing the test system 1 to perform the test of the device under test 115, the processor 106, e.g., a TEPC, which executes the illumination control program 124, 110 and activates the camera 112 to record an image while the illumination device 110 is emitting light at the first level. The processor 106, e.g., a TEPC, processes an image obtained from the camera 112 that is activated while the illuminator is emitting at the first level, allowing the barcode 500 to be recognized (if the barcode is included).

After reading the code used to obtain and / or obtain the image / barcode 500, or otherwise obtain the necessary configuration file or folder, the processor 106, e.g., a TEPC, turns off the lighting device 110 Do not illuminate anymore. For example, the processor 106, e.g., the TEPC, executing commands in the selected configuration file in the database 123 may also operate the robot 102 to manipulate the device under test 115 while the illuminator 110 is turned off So that the display screen of the device under test 115 is turned on. To detect the precise location and boundary of the display screen of the device under test 115 relative to the camera 113 based on the contrast between the unlit ambient and the light generated by the display screen, The contrast may also be configured such that an image obtained from the camera 113 while the illumination device 110 is turned off and the display screen is activated and illuminated, for example, The results of the analysis are as follows. The location of the device fixation device 114 relative to the platform 104 is determined by the device fixation device 114 on the platform 140 in place for testing 114, the process of finding the display screen is performed by processor 106, e.g., TEPC, because despite this situation, some of the display screen for camera device 111 Which results in miscalculation of Regions Of Interest (ROIs) used for image processing during testing of the device 115 under test. For example, the above-described movement is caused by slight differences in the camera apparatuses in various copies of the test system.

After determining the position of the display screen relative to the camera 113, the processor 106, e. G., The TEPC, determines the illumination device 110 to emit at a second level different from the first level used to read the barcode of the fixture. . The second level is maintained for the remainder of the testing process of the device under test 115. In particular, the second illumination level may be lower than the first level, such that the light illuminated on the display screen is emitted by the illumination device 110 at a second level rather than when the illumination device 110 illuminates at the first level Becomes more clear about the light being emitted.

In an embodiment of the present invention, compartment 100 is completely enclosed. Surrounding the compartment 100 on one side or more sides is accomplished through a door or curtain that is openable for the user to access the compartment 100 interior. Enclosing the compartment 100 enables precise control of the level of illumination in the compartment without being affected by ambient light from outside the compartment 100.

In an embodiment of the present invention, the processor 106, e.g., TEPC, executes a test target device button location training wizard 125 stored in the memory 107, e.g., TEPC. For example, a user may enter a command via the input device 109 to cause the processor 106, e.g., the TEPC, to load and execute the wizard 125. The command of the wizard 125 may cause the processor 106 to provide a prompt to the user for manual operation of the various data or robotic arms 103, e.g., via the display 108. [ In response to user input and arm operation, the processor 106 creates a new configuration file and / or a folder or a new sub-file or folder thereof in the database 123. In an embodiment of the present invention, in response to user input and actuation of the arm, no new configuration files or folders are created, but existing configuration files may be modified to include the practice location of the buttons.

During execution of the wizard 125, the processor 106, such as the TEPC, may provide a prompt to the user to enter the underlying software features supported by the new test target device 115. For example, the prompt may be a series of "yes / no" forms of questions or checkboxes, each questioning whether the new device under test 115 includes individual basic features. A comprehensive list of exemplary features that the processor 106 queries includes support for various tasks such as calls, message delivery, and / or e-mail, and support for a variety of tasks, such as, for example, Type and / or the surface of the device under test 115 on which the respective input hardware is located. At this time, the processor 106 determines whether the database 123 includes a configuration file or a folder for another device having characteristics similar to those input to the new test target device 115. [ For example, if most of the features entered for the new test target device 115 match the input features provided when configuring the test system 1 for another device, the processor 106 determines that these two devices are similar do. Further, if more than one device is determined by the processor 106 to be similar to the new device under test 115, the processor 106 selects the most similar device as determined by the input to the new device under test 115 do.

In an exemplary variation, the program does not determine whether the two devices are similar. Instead, the user makes this determination and selects a pawn of similar characteristics as a basis for modification.

In an embodiment of the invention, the processor 106, e.g., the TEPC, first requests that the test system 1 be identified with a device that the user has determined is the one that was previously configured and most similar to the new test target device 115. When the user identifies such a device and the processor 106 finds a configuration file or folder in the database 123 associated with the identified device, the processor 106 requests the user to enter the basic features of the new test target device 115 Can be omitted. In an exemplary variation, the steps are not omitted. Although all the configuration steps are in progress, only a small amount of work is required to perform only the change of the reference file, instead of generating configuration file characteristics by information gathering.

The processor 106 determines whether the device associated with the configuration file or folder of the database 123 is similar to the new test target device 115 or if the user confirms with a similar device, Obtains a relevant configuration file or folder from the device or phone configuration directory and generates a copy of the configuration file or folder thus obtained as a configuration file or folder associated with the new test target device 115 and creates a copy of the configuration file or folder in the database 123 or other device or phone configuration directory . The folders are named according to the manufacturer and model of the device under test. For example, a folder may be named by the manufacturer, which may include sub-folders, each of which is associated with each device being tested and named by the respective manufacturer of the device under test . The production folder may include sub-folders for the button sequence used and the display screen image. The files may correspond to other display screen images and other sequences. An example of the file structure is shown in Fig.

The wizard may automatically populate a configuration file that identifies supported features of the device under test 115, such as the approximate placement of the camera's inclusions and buttons, including supported operations and embedded hardware. These files are used to determine which test cases are driven to test the features of the device under test 115. [

However, all the settings do not accurately reflect the new test target device 115 because the configuration file or folder was first created for another device. Thus, the wizard may take steps through a series of display screens that can interact with the user to enter information relating to the new test target device 115 for operability during testing. The display screen is first populated with information that reflects the configuration file or other device from which the folder was created. Whenever a user becomes aware of a discrepancy between the displayed data and the data that accurately reflects the new test target device 115, the user can enter the necessary changes. For example, to accomplish a particular task, the user may update the button sequence to be used for the new test target device 115 and / or display it on the display screen of the test target device 115 at a particular event or after a specific event The display screen image can be updated.

Furthermore, if the new test target device 115 includes additional features for a device for which the old configuration file does not provide the same configuration file, then the new sub-file or sub-element for the added feature is added to the configuration file Lt; / RTI > Similarly, the processor 106, e.g., TEPC, removes the sub-files or sub-elements corresponding to features for which the new test target device 115 does not provide the same configuration file.

If the processor 106 determines that the stored configuration file or folder of the database 123 is not associated with a device similar to the new test target device (if any) by the processor 106, e.g., TEPC, It requests to input all necessary information and creates a new configuration file or folder from the collected information. In an exemplary variation, the user is always required to select an existing phone / device so that the wizard automatically generates a configuration file for the new device based on the file of the selected device. For example, when programming a wizard, an initial configuration file may be stored to later create a file for the device to be tested.

After reconfiguring the configuration file for the support features of the device under test 115, the wizard may take action through a plurality of test cases previously configured by the wizard. During each step through the test cases, for each case, the wizard prompts the user to operate the new test target device 115, so that the display screen of the new test target device 115 is installed in the field of view of the camera 113 While the display screen of the new test target device 115 displays the resulting screen from each test case. Once the resulting screen is displayed, the user enters an indication that the screen is being displayed. The processor 106, e.g., the TEPC, writes an image obtained from the camera 113, recorded by the camera 113 in association with the test case, in the configuration file when the user inputs an indication that the requested screen has been displayed . The processor 106 compares the images obtained from the camera 113 while testing the device under test 115 with the images of the configuration file associated with the device 115 under test.

In an embodiment of the present invention, the processor 106, e.g., TEPC, is configured to initialize the configuration file with the configuration file of the device 106, which is similar to the new test target device 115, It can be populated. The user can display for each test case whether another display is provided. In a variation of the present invention, a new display screen is always required for each new test target device 115, ensuring that the processor 106, e.g., TEPC, considers some spatial variations in the display screen .

In an exemplary embodiment of the present invention, the robot 102 includes a force sensor 600 as shown in FIG. The force sensor 600 senses the force exerted by the arm 103 in a direction parallel to the platform 104 and perpendicular to the platform 104. The arm 103 can actuate the input hardware of the device under test 115 by pressing buttons on the surface of the device under test 115 parallel to the platform 104 and the device under test Lt; RTI ID = 0.0 > 115 < / RTI > In the above case, the force sensed in the vertical direction increases as the button is depressed, while in the latter case, the force sensed in the parallel direction increases as the button is depressed. Other parts of the arm 103 are used to depress buttons in the direction in which the buttons are depressed. For example, the end 601 of the arm is used to press the button in a vertical direction, and the side element 602, e.g., formed of a ring, is used to press the button in a parallel direction.

In an embodiment of the present invention, during the generation of a configuration file for the device under test 115, the processor 106, e.g., the TEPC, Record the coordinates of the input hardware. Based on the information provided in the configuration file representing the input hardware contained in the new test target device 115 and detailed as described above, the wizards 125 may be configured for each hardware input means, The user is prompted to manually move the robot arm 103 to a position where the processor 106, e.g., TEPC, coincides with the position of the button in a plane different from the plane in which the button is disposed. For example, for buttons on the surface of the device under test 115, parallel to the platform 104, the arm end 601 may be in line with the button, but on the surface of the device under test 125 where the button is located The user moves the arm 103 so that it is in a different but parallel plane. For the buttons on the surface of the device under test 115 that is perpendicular to the platform 104, the side element 602 is in line with the button, but different from the surface of the device under test 125 where the button is located, The user moves the arm 103 in a plane.

For a button on the surface of the device under test 115 parallel to the platform 104, once the user enters an indication that the robotic arm 103 has been moved to the required position, the processor 106, Where the x coordinate and the y coordinate of the arm end 601 are recorded in the configuration file where the x coordinate is a position on the axis extending along the plane of the platform 104 in the horizontal direction and the y coordinate is the position on the platform 104 in the vertical direction, Lt; / RTI > The processor 106, e.g., TEPC, also actuates the arm 103 to extend in the vertical direction to depress the button. If the force sensor 600 providing the readout value to the processor 106, e.g., the robot controller PC, detects that the preset force has been reached, the processor 106, e.g., the TEPC, Lt; RTI ID = 0.0 > z < / RTI > Where the z coordinate is a position on the plane extending perpendicular to the platform 104. For most buttons, the force used for the preset force is determined to be about 500 grams. However, other forces previously set may be used for other buttons.

In an exemplary variation, when the user enters an indication that the robotic arm 103 has moved to the desired location, the processor 106, e.g., the TEPC, prioritizes the x coordinate and y coordinate as well as the initial z coordinate in the configuration file Record. After force calibration the z coordinate is updated.

For a button on the side of the device under test 115 that is perpendicular to the platform 104, when the user enters an indication that the robot arm 103 has moved to the desired position, the processor 106, e.g., TEPC, Record the z coordinate and y coordinate (and the initial x coordinate in the example) of the arm end 601 in the file. The processor 106, e.g., TEPC, also operates to extend the arm 103 in one of the parallel directions (along the side of the device under test 115 where the button is located) to press the button. When the force sensor 600 detects that a preset force has been reached, the processor 106 writes the current x-coordinate of the arm 103, e.g., the changed x-coordinate, in association with the button, in the configuration file. During subsequent testing of the device under test 115, the processor 106, e.g., the TEPC, causes the robot arm 103 to move to the recorded x, y, and z coordinates in accordance with the associated configuration file, (115).

During the creation or modification of the configuration file for the test target device 115, the processor 106, e.g., the TEPC, is configured to test the test target device 115, while configuring the test system 1 for the new test target device 115, The lighting device 110 is operated in a manner similar to that described above with respect to operation. For example, a barcode is placed in the device holding device 114 before the configuration of the test system 1 for the new device under test 115. [ When the configuration is initiated, the processor 106 causes the processor 106 to operate the illuminator 110 to illuminate to a first level to detect the bar code 500. When a barcode is detected, the processor 106, e.g., the TEPC, turns off the illuminator 110 and urges the user to activate the display screen of the new test target device 115. When the processor 106 receives an indication that the display screen is activated, the processor 106 reads the correct position of the display screen for the camera 113 by the light contrast of the display screen, do. After recording the position of the display screen, the processor 106, e.g., the TEPC, activates the illumination device 110 to illuminate it at a second level. Processor 106 records template display screens as described in detail above while illuminator 110 illuminates at a second illumination level.

It should be noted that the configuration of the test system 1 for the new test target device 115 is temporarily stopped, stored as an undefined configuration file, and can be restarted at a later time. Each time, the configuration is resumed and the processor 106, e. G. TEPC, re-executes one or more of the lighting control steps. For example, each time processor 106, e.g., TEPC, activates illumination device 110 to illuminate at a first illumination level to read the bar code and determine which configuration file to open for modification. If all of the display screen templates have not yet been performed, other lighting control steps may be performed. In the embodiment of the present invention, the first illumination control step is omitted when the user does not need to manually input the code and read the bar code. In an embodiment, the test system always attempts to read a bar code and urges the user to configure a new device, e.g., a pawn, if the read is unsuccessful.

In an embodiment of the invention, the test system 1 includes a mini-workstation 1100 to perform a substantial portion of the test system 1 configuration for the new test target device 115, as shown in Fig. 10 . For example, the mini workstation 1100 can be used to perform all configurations, except for recording input hardware coordinates. Many of the elements of the main workstation that perform the configuration and testing of the input hardware coordinates are omitted in the mini workstation 1100. For example, one or more robots 102, partner device commands 120, a portion of the configuration wizard 125 used to input input hardware coordinates, and most image processing software (but, for example, barcode 500) Except for those used for recognition) may be omitted in mini workstation 1100. [ In the embodiment, many of the software of the main workstation is also included in the mini-workstation 1100 because it is necessary for a large portion of the same software to obtain template images at the mini-workstation 1100. Any portion of the configuration file associated with the new test target device 115, e.g., except for input of input hardware coordinates, can be created and modified at the mini-workstation 1100. The mini workstation includes a lighting device 110 and a camera device 111 as described above in connection with the main workstation, each of which can be operated as described above with respect to the main workstation. Although not shown in FIG. 10, the mini workstation may be connected to or included in a user terminal that includes a processor, an input device, and an output device so that a user can control the processor to operate the device and create and / or modify a configuration file . 10, the compartment 1102 of the mini workstation 1100 in which the device under test 115 is disposed for the configuration of the test system 1 includes walls and doors and / or curtains Surrounding compartment 1102 for control of increased lighting conditions within compartment 1102.

The mini workstation 1100 provides the flexibility for many users to collaborate to perform various portions of the configuration, e.g., simultaneously and / or in many places.

At any time, the configuration may be stopped at the mini workstation 1100 or at the main workstation and then resumed. The device under test 115 mounted on the device fixture 114 may be moved to the main workstation to perform actual testing on the device under test 115 or to include data specifying input hardware coordinates You can change the configuration file. The user has the option to use only the main workstation for all configurations and tests.

In the embodiment of the present invention, another test sequence is used for another test target device 115. [ The configuration file associated with the device under test 115 confirms the test sequence applied to each device under test 115 when the device under test 115 is tested. The processor 106, e.g., the processor 106 with the TEPC and the robot controller PC coupled, operates the robot 102 during testing according to a test sequence in the associated configuration file. The processor 106 may also interface with the partner device 116 in accordance with the test sequence included in the configuration file to control the partner device 116 to communicate with the device 115 under test.

In an exemplary variation, the test sequences are not designed to be placed in the phone configuration directory (the Phone Config Directory) or the configuration file, but are designed to be comprehensive for all devices. The configuration and reference images and reconstructed button sequence files in the phone configuration directory are referenced in the test sequence to achieve this by isolating the operating characteristics of the device from the comprehensive test sequences. Since the partner device 116 is constant, the file governing that control is stored outside the phone configuration directory.

Figure 12 illustrates a process for testing a device, including generating a configuration file and performing a test, in accordance with an embodiment of the present invention. At step 1200, the processor of the mini workstation automatically turns on the illumination to the first level. In step 1202, the camera of the mini workstation is used to detect the barcode while the illumination is maintained at the first level. In step 1204, the processor automatically turns off the illumination. While the light is off, the processor detects the location of the display screen of the device under test with respect to the camera in step 1206. In step 1208, the processor automatically turns the illumination on to the second level. At step 1210, the processor generates a portion of the configuration file associated with the detected barcode. An exemplary detailed description of the creation of the configuration file is shown in FIG.

In step 1212, steps 1200-1208 may be repeated in the main station. By detecting the barcode at the main station (step 1202), the configuration file associated with the barcode is selected. In step 1214, the configuration file is completed. Fig. 14 is a detailed explanatory diagram of the completion of the configuration file.

In step 1216, the device under test and the partner device are operated according to the configuration file and the stored test sequence. For example, the device under test is manipulated using a robot arm, while the partner device is manipulated through an interface to the partner device. If the operation of the devices for using and testing the main station is completed, for example, completion of generation of the configuration file by stopping power transmission of the main station, or configuration or testing of another device, steps 1200-1208 are repeated immediately before step 1216 .

In step 1217, the video images of the device under test and the partner devices can be captured using one camera. In step 1218, a still image of the device under test may be obtained using another camera, and still images and text on the display of the partner device are obtained through an interface to the partner device. At step 1220, the processor compares the captured still image with the stored image or compares the captured text displayed on the display screen with the stored comparison text and compares at least one of them. The text displayed on the display screen can be captured as an ASCII text value and compared to the stored comparison text. In step 1222, the processor determines if an error has occurred based on the comparison. If an error has occurred, the processor stores the still image and / or video image captured at step 1226 in persistent storage means. If no error has occurred or after step 1226, the process continues from step 1216 if the test sequence has not been completed (N branching at step 1224). Otherwise, the process is terminated.

Figure 13 illustrates some details of step 1210 according to an embodiment of the present invention. At step 1300, the processor outputs a prompt for input of a device feature. In step 1302, the processor compares the features entered in response to the prompt with features of other devices included in other configuration files associated with the other devices. If the device is determined to be similar based on the comparison, the processor obtains configuration files associated with a similar device in step 1304 and copies it as a new configuration file associated with the device under test. If a similar device is not found, the processor creates a new configuration file at step 1303. Subsequently, the processor updates the configuration file associated with the device under test in response to the user input according to the assignment file indicating the assignment to be performed during the test, as previously described above in step 1306. In an exemplary embodiment, step 1306 includes repeating step 1300 for each of the device features for further reconfiguration.

In an exemplary variation, the process begins at step 1302 with the user manually comparing the features of the other device with the features of the device under test. At step 1304, the user selects the comparison device and the processor retrieves and copies the configuration file of the device. The process proceeds from step 1304 to step 1300, where the processor modifies the copied configuration file by prompting for input of the device ' s properties and reconstructs it for the new device in step 1306. [ This variant can also omit such a decision and step 1303 because the test system always requires the selection of a previously saved configuration file when using a set-up wizard. Thus, according to a variant, the sequence of the inventive method is from step 1302 to step 1304 to step 1300 to step 1306.

Figure 14 illustrates some details of step 1214 according to an embodiment of the present invention. At step 1400, the processor outputs a prompt indicating movement of the robotic arm such that the robotic arm is positioned in two-dimensional coordinates of a plane parallel to the plane in which the button is located, wherein the two- . In that position, the processor causes the robotic arm to extend toward the button, step 1402. In step 1404, the force sensor senses the force at the tip of the robotic arm and provides a readout to the processor, e.g., the robot controller PC. In step 1406, the processor, for example the robot controller PC, compares the sensed force with a preset force value. If the sensed force value has not reached the preset value, the process continues from step 1402 again. Otherwise, the process records the three-dimensional coordinates of the robotic arm with respect to the button in step 1408. The process is repeated for all buttons. The coordinates are recorded for all buttons and the process is terminated.

In an embodiment of the present invention, the steps of Figure 14 are divided into two separate loops. In the first loop, step 1400 is performed for all buttons. In step 1400, if the robot arm is in the indicated position, the processor records the two-dimensional coordinates of the button. In an exemplary variation, the processor initially records the initial three-dimensional coordinates of the button, and then the coordinates are changed in step 1408. [ In a subsequent loop, steps 1402-1408 are performed on all buttons.

An embodiment of the present invention relates to a processor, which is implemented using any conventional processing circuitry, and is configured to perform any processing, such as by combining the above-described features, one by one, And execute code provided on a computer readable medium executed by the hardware.

An embodiment of the present invention is directed to a computer-readable medium in which instructions executable by a processor are executed by hardware to perform any of the above-described features, including control of other hardware components, .

An embodiment of the present invention is directed to a method comprising the step of delivering an executable instruction by a processor to perform any processing by combining the above mentioned features one by one, including control of different hardware elements.

In an embodiment of the present invention, a device securing device 114 is provided to have a small landing point to allow placement of the device under test 115 and the partner device 116 adjacent thereto. The device securing device 114 can also be configured to quickly, easily, and conveniently adjust the position of the device under test 115 with respect to the robot 102 and / or the camera device 111. Particularly, as described above, it is advantageous to arrange the device under test 115 so that the display screen of the device under test 115 is substantially parallel to the platform 104 so as to be in good focus and focus of the camera 113. The device securing device 114 is also adapted to accommodate a number of different types of test devices 115 having different configurations without requiring a difficult reconfiguration. FIG. 7 shows the components of an exemplary device securing device 114 that provides all of the advantages described above, except for the base plate to which the illustrated components are attached. 8 shows the structure of an exemplary device securing device 114 in an assembled state, except for the base plate.

The device securing device 114 includes an attachment plate 700, a base 702 including a wide base 703 and a narrow base 704, a first vertical plate 705, a second vertical plate 706, Plate 750 as shown in FIG. 7 and 8 can be fixed to the base plate 900 shown in Fig.

The attachment plate 700 has respective elongated holes 701 passing through both side surfaces thereof. The screw penetrates through the long hole 701 and extends into the screw hole 902 of the base plate 900 and is screwed so that the components shown in FIGS. 7 and 8 are fixed to the base plate 900. Due to the vertical extension length of the screw extending through the elongated hole 701, the attachment plate 700 can be adjusted to the length of the elongated hole 701 subtracting the thickness of the screw until the screw is substantially tightened to the screw hole 902 And can be moved with respect to the base plate 900 by the same distance.

The attachment plate 700 also includes a window 710 formed in a substantial portion of the attachment plate 700 between the elongated holes 701. The attachment plate 700 is moved relative to the base plate 900 after at least a screw extending through the elongated hole 701 is engaged with the hole 902 until at least the screw is tightly fastened to the hole 902 The base 702 is slid in the window 710 in a direction perpendicular to the direction. Removal of the base 702 from the attachment plate 700 through the window 710 is prevented by contact between the lip 715 of the attachment plate 700 and the wide base 703. The thickness 708 of the broad base 703 may be greater than the height 709 of the lip 715 from the bottom of the attachment plate 700 on which the broad base 703 slides. The compressive force of the attachment plate 700 against the broad base 703 due to the difference between the thickness 708 of the wide base 703 and the height 709 Thereby preventing the base 702 from sliding relative to the attachment plate 700. Alternatively, the thickness 708 and the height 709 may be the same, and tightening of the screw may create a frictional force to prevent sliding of the base 702 relative to the attachment plate 700.

The first vertical plate 705 includes a plurality of holes 730, for example, two holes 730, which are arranged in a first direction perpendicular to the direction in which the base 702 slides relative to the attachment plate 700 And extends through the vertical plate 705. The second vertical plate 706 includes a curved through-hole 707. The screw extends through the curved through hole 707 and is screwed into the hole 730 so that the second vertical plate 706 is connected to the first vertical plate 705. The second vertical plate 704 can be rotated relative to the first vertical plate 705 before the screws extending through the holes 730 are tightened, The surface angle of the T-shaped structure portion 740 of the vertical plate 706 can be changed. The first vertical plate 705 which changes the angle of the T-shaped structure portion 740 with respect to the attachment plate 700 and the base plate 900 as the frictional force is increased by tightening the screw extending in the hole 730, Further movement of the second vertical plate 706 relative to the second vertical plate 706 is prevented.

The mounting plate 750 includes a T-shaped hole 752 that extends through the length of the mounting plate 750 below the mounting plate 750. The T-shaped structure portion 740 and the T-shaped hole 752 are formed in a fitting manner so that the T-shaped structure portion 740 extends through the T-shaped hole 752 so that the mounting plate 750 is inserted into the second vertical plate 0.0 > 706 < / RTI > It will be appreciated that other shapes may be used for the fitting structure of the vertical plate 706 with the holes of the mounting plate 750, which allows the mounting plate 750 to be similarly connected to the vertical plate 706. The mounting plate 750 may further include holes 755 extending into the T-shaped hole 752 in a direction perpendicular to the T-shaped hole 752. As the mounting plate 750 is slid into the vertical plate 706 as described above and then the set screws are inserted until a substantial compressive stress is applied to the T-shaped structure 740, Thereby preventing further movement of the mounting plate 750, thereby preventing disassembly of the mounting plate 750 from the second vertical plate 706. [

The device under test 115 is attached to the mounting plate 750 by, for example, double-sided adhesive tape. The mounting plate 750 is attached to the vertical plate 706 as described above. The overall fastening device 114 is disposed in a workstation, such as a main workstation, for example by connecting legs extending downwardly from the bottom surface of the device fastening device 114 into the receiving holes of the platform 104. [ Alternatively, the device fixation device 114 may include a plurality of holes, e.g., four holes, e.g., one at each corner, each corresponding to a corresponding plurality of O- Post, e. G., Four posts. When placing devices, the user decides what adjustment is necessary. The adjustment may be performed by movement of the second vertical plate 706 relative to the first vertical plate 705, movement of the base 702 within the window 710, and / . In particular, the angle of the second vertical plate 706 relative to the platform 104 is adjusted such that the display screen of the device under test 115 is substantially parallel to the camera 113.

The device under test 115 includes buttons on its side, i.e., the portion including the display screen, so that the pushing direction of the buttons extends parallel to the surface plane of the display screen. When the robot 102 presses the side button, a torque force is generated. The post 1000 is installed in a screwed manner into the hole 902 of the base plate 900 so as to prevent the device under test 115 from being rotated by this force, The position is a position at which the post 1000 is brought into contact with the device under test 115 on the side opposite to the side on which the side button of the device under test 115 is disposed. In the case where the side buttons are disposed on both sides of the device under test 115, the posts 1000 are also disposed on both sides. If there are no side buttons, the posts are omitted.

Those skilled in the art will readily appreciate from the foregoing description that the present invention can be embodied in various forms and that various embodiments may be practiced alone or in combination. Therefore, it should be understood that the embodiments of the present invention have been described in connection with specific examples only, and that the true scope of embodiments and / or methods of the present invention is not so limited because other modifications may occur to those skilled in the art And is apparent from the drawings and the description of the invention and claims.

1: device test system 100: compartment
102: robot 103; Arm
104: Platform 105: User terminal
106: processor 107: memory
108: display 109: input device
110: illumination device 111: camera device
115: Test target device 120: Command
123: Database

Claims (20)

As a device test system,
A memory for storing a plurality of screenshots associated with the first device;
A first camera;
A second camera;
A platform disposed such that at least a portion thereof is in a field of view of the first camera and a field of view of the second camera;
A robot arm; And
A processor connected to the first camera and the second camera and to the memory;
And,
The first camera being arranged so that an axis extending through the lenses of the first camera extends substantially perpendicularly toward the platform;
Wherein the second camera is arranged such that an axis extending through the lenses of the second camera extends at an angle that is not substantially perpendicular to the platform so that the second camera has a smaller zoom setting than the first camera, The camera senses a larger field of view than the first camera;
Wherein the first camera is configured to transmit the captured image to the processor;
Wherein the processor is operative to cause the robotic arm to actuate the first device when the first device is placed on the platform and to compare images received from the first camera with stored screen shots during operation of the first device, Determining that an error has occurred if at least one image received from the first camera during operation does not match a plurality of stored screen shots and determining that an error has occurred if a video captured by the second camera for a predetermined period of time And wherein the device test system is configured to store in memory. 2. The apparatus of claim 1, further comprising a force sensor configured to sense a force generated by the robot arm;
Wherein the processor is configured to generate a configuration file, wherein operation of the first device is performed in accordance with the configuration file, and the generation of the configuration file includes, for at least a subset of the plurality of buttons of the first device, Extending the robotic arm in a direction perpendicular to the surface of the button until a preset force value is sensed by the sensor and writing coordinates to the configuration file along the axis of the robot arm along an axis extending perpendicularly to the surface of the button ;
The actuation of the first device includes adjusting each of the at least one subset of buttons sufficient to cause each signal in the first device to be acknowledged for adjustment of each button;
For each of the at least one subset of buttons, the adjustment is based on a configuration file in a direction perpendicular to the respective button surface until the position of the robotic arm corresponds to a respective coordinate recorded in the configuration file for each button. To extend the robot arm. 6. The system of claim 1, further comprising a mini-workstation having a camera device, a processor and a platform under the camera device, wherein the mini-workstation does not have a robotic arm capable of operating the first device;
Wherein operation of the first device is performed in accordance with one or more configuration files associated with the first device;
Wherein the one or more configuration files comprise a screenshot of a display screen that is compared to an image captured during operation of the first device;
Wherein at least a portion of the one or more configuration files is configured to be generated by capturing a screen shot using a camera device of a mini workstation. A device testing method comprising:
Operating the first device according to a stored test sequence;
Capturing a still image of a display screen of a first device using a first camera having a field of view substantially occupied by the display screen;
Capturing a video image using a first camera and a second camera having a field of view in which a second device communicating with the first device during a test of the first device is located;
Comparing the captured still image with a stored screen shot in a first comparison step;
Determining whether an error has occurred based on the comparison; And
Storing a video clip corresponding to a period in which an error has occurred and captured by the second camera on the condition of a determination that an error has occurred
/ RTI > 5. The method of claim 4, further comprising storing one or more captured still images in a memory, subject to a determination that an error has occurred. 5. The method of claim 4, wherein the period ends at an end time after an error occurs, starting at a start time before an error occurs. 5. The method of claim 4, further comprising: locating a code region within an image captured by at least one camera of a camera viewing the first device;
Processing the code region to obtain a code that is encoded in the code region;
Obtaining a configuration file based on the relationship between the code and the configuration file
Wherein the operation of the first device is in accordance with the configuration file. 8. The method of claim 7, wherein the code is a bar code. 5. The method of claim 4, further comprising detecting a position of a display screen with respect to a field of view of a first camera, and performing the first comparing step according to the detected position. 8. The method of claim 7, further comprising: during the step of locating the code area, activating the illuminator such that the processor automatically illuminates at a first level;
Following the positioning of the code area, the processor automatically activates the illuminator so that the illuminator does not illuminate while detecting the position of the display screen; And
Following the step of detecting the position of the display screen, the processor further comprises activating the illumination device to automatically illuminate at a second level during capturing still and video images. 5. The method of claim 4, further comprising generating a configuration file in which operation of a first device is performed in accordance with a configuration file;
The creation of a configuration file for at least a subset of the plurality of buttons,
Extending the robotic arm in a direction perpendicular to the surface of the button until a preset force value is sensed by the force sensor;
Writing the coordinates of the robot arm position along an axis extending perpendicular to the surface of the button to a configuration file;
Wherein the actuation of the first device is performed through a robotic arm and comprises adjusting for each of the at least one subset of buttons such that an individual signal confirming adjustment of each button is sufficient to occur in the first device;
For each of the at least one subset of buttons, the adjustment is performed in a vertical direction relative to the respective button surface until the position of the robotic arm coincides with the respective coordinates recorded in the configuration file for each button Wherein the method is performed by extending a robotic arm on the basis of the robot arm. 5. The method of claim 4, further comprising generating a first device configuration file in which operation of the first device is performed in accordance with a configuration file; Wherein the creation of the first device configuration file comprises:
Retrieving a third device configuration file associated with a third device similar to the first device;
Storing a copy of the third device configuration file as a first device configuration file;
And updating the first device configuration file to reflect a received user input, identifying a difference between the first device and the third device. 13. The method of claim 12, wherein generating the first device configuration file further comprises determining whether the third device is similar to the first device in response to receiving a user input representing characteristics of the first device, 3 device configuration file is retrieved in response to a similarity determination between the first device and the third devices. 13. The method of claim 12, wherein the third device configuration file is retrieved in response to a user input selecting a third device configuration file. 5. The method of claim 4, further comprising generating a configuration file in which operation of the first device is performed in accordance with a configuration file; The generation of the configuration file may be performed in accordance with a file identifying a plurality of test tasks,
Outputting a prompt for information identifying each set of device operation sequences that can be used to perform each task; And
And in response to the received information for the prompt, updating the configuration file to include the received information. 5. The method of claim 4, further comprising: forming an interface with a second device to simulate mechanical adjustment of an input device of a second device, wherein the simulator allows the second device to communicate with the first device Test method. 17. The method of claim 16, further comprising: forming an interface with a second device to capture at least one of text and still images displayed on a display screen of a second device;
Comparing the stored screenshot with the captured still image of the display screen of the second device and the stored comparison text with the captured text displayed on the display screen of the second device in a second comparison step;
Further comprising determining whether an error has occurred based on the comparison of the second comparison step. 18. The method of claim 17, wherein the text displayed on the display screen is captured as an ASCII text value and compared to the stored comparison text. A computer-readable medium executed by a hardware, the medium storing instructions therein, the instructions performing a device test method by a processor when driven, the device test method comprising:
Operating the first device in accordance with stored test sequences;
Operating a first camera having a field of view substantially including the display screen to capture still images of a display screen of the first device;
Operating a second camera such that a second camera having a view wherein a first device and a second device communicating with the first device in a first device test are disposed, captures a video image;
In a first comparison step, comparing the captured screen shots with the captured still images;
Determining if an error has occurred based at least in part on the comparison; And
And storing the video clip captured by the second camera in at least one of the memory and the disk during the period in which the determined error occurred
≪ / RTI > wherein the computer-readable medium is executable by a computer. 20. The computer-readable medium of claim 19, wherein activating the first device in accordance with the stored test sequences comprises causing the robotic arm to interact with the first device.

Images