KR101664150B1 - Terminal software verification system and verification method - Google Patents

Terminal software verification system and verification method Download PDF

Info

Publication number
KR101664150B1
KR101664150B1 KR1020160073073A KR20160073073A KR101664150B1 KR 101664150 B1 KR101664150 B1 KR 101664150B1 KR 1020160073073 A KR1020160073073 A KR 1020160073073A KR 20160073073 A KR20160073073 A KR 20160073073A KR 101664150 B1 KR101664150 B1 KR 101664150B1
Authority
KR
South Korea
Prior art keywords
test
terminal
basic
software
voltage level
Prior art date
Application number
KR1020160073073A
Other languages
Korean (ko)
Inventor
이무철
Original Assignee
(주) 피에스소프트
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by (주) 피에스소프트 filed Critical (주) 피에스소프트
Priority to KR1020160073073A priority Critical patent/KR101664150B1/en
Application granted granted Critical
Publication of KR101664150B1 publication Critical patent/KR101664150B1/en

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/36—Preventing errors by testing or debugging software
    • G06F11/362—Software debugging
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/36—Preventing errors by testing or debugging software
    • G06F11/3668—Software testing
    • G06F11/3672—Test management
    • G06F11/3688—Test management for test execution, e.g. scheduling of test suites
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/36—Preventing errors by testing or debugging software
    • G06F11/3668—Software testing
    • G06F11/3696—Methods or tools to render software testable

Abstract

A terminal software verification system, which modifies test software on a basis of results of a basic test and a repeated test, includes: a test confirmation unit for confirming hardware version information, software version information, voltage information, battery remaining amount, test items, and test procedures; a terminal mounting unit arranged thereon with at least one terminal to be verified, for applying a test software onto each of the terminals; a basic test unit for driving the test software to proceed with a basic test and generate basic test data; a repeated test unit for proceeding with at least one repeated test while sequentially moving each of the terminals which has completed the basic test, to generate repeated test data; and a control unit for modifying the test software on a basis of the basic test data and the repeated test data.

Description

Technical Field [0001] The present invention relates to a terminal software verification system and a verification method thereof,

The present invention relates to a terminal verification technique, and more particularly, to a terminal software verification system and a verification method thereof.

Due to the widespread use of handsets, the production volume of terminals with complex functions is enormous. Conventionally, in confirming whether or not to implement a complex function implemented in a vast amount of terminals, it is generally executed by hand or by some physical machine.

Therefore, there is a limit due to the mechanical action. Therefore, it is difficult to judge whether or not to execute the complex function implemented in the terminal. Accordingly, a fatal bad phenomenon such as power on / off operation or rebooting of the terminal may be caused due to an error occurring when the data of the most critical memory area is written or read (read) .

In order to solve the above problem, Korean Patent Registration No. 10-0713469 has been proposed. However, there is a limitation that it is possible to simply check whether the function is implemented by simply repeating the functions.

KR10-0713469B

SUMMARY OF THE INVENTION The present invention provides a terminal software verification system and a verification method thereof that can modify test software based on a result of a basic test and a repeated test.

According to an embodiment of the present invention, a test verification unit confirms hardware version information, software version information, voltage information, battery remaining amount, test items, and test proceeding procedures; A terminal seating part for sorting at least one terminal to be tested and applying test software to each terminal; A basic test unit for driving the test software to proceed with the basic test and generate basic test data; At least one or more repetition testing units for sequentially performing at least one repetition test and generating repetitive test data while sequentially moving each of the terminals for which the basic tests have been completed; And a software control unit for modifying the test software based on the basic test data and the repeated test data.

The basic test may include at least one of a telephone call, a message transmission / reception, a memo record, a schedule record, and a contact record, and the repetitive test may include power off, file write / And includes at least one of Read / Write, Power on / off, Booting, Sleep / Wakeup, and Cover open.

Also, according to another embodiment of the present invention, there is provided a method of testing a battery pack, comprising: checking hardware version information, software version information, voltage information, remaining battery amount, test items, Arranging at least one terminal to be verified and applying test software to each terminal; Driving the test software to proceed with the basic test and generate basic test data; Performing at least one or more repeated tests while sequentially moving each of the terminals having undergone the basic test and generating repeated test data; And modifying the test software based on the basic test data and the repeated test data.

The basic test is characterized by including at least one of a telephone call, a message sending / receiving, a memo record, a schedule record, and a contact record.

The repetition test may be performed by using a power off, a file read / write, a power on / off, a boot, a sleep / wakeup, And at least one of a cover open and a cover open.

The terminal software verification system and the verification method thereof according to the embodiment of the present invention can improve the test reliability by modifying the test software based on the results of the basic test and the repeated test.

1 is a configuration diagram of a terminal software verification system according to an embodiment of the present invention;
2 is a diagram illustrating a terminal software verification method of FIG. 1;

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings, in order to facilitate a person skilled in the art to easily carry out the technical idea of the present invention.

1 is a configuration diagram of a terminal software verification system 1 according to an embodiment of the present invention.

The terminal software verification system 1 according to the present embodiment includes only a brief configuration for clearly explaining the technical ideas to be proposed.

Referring to FIG. 1, a terminal software verification system 1 includes a test verification unit 100, a terminal placement unit 200, a basic test unit 300, a repetitive test unit 410 and 420, (500).

The detailed configuration and main operation of the terminal software verification system 1 configured as described above will be described below.

In this embodiment, a terminal is a general term for a device that a user can use while being portable, such as a mobile phone, a smart phone, and a smart pad, and is assumed to be a terminal configured as a smart phone in the present embodiment.

The test verification unit 100 confirms the hardware version information, the software version information, the voltage information, the remaining battery amount, the test items, and the test progress procedure. That is, the test verification unit 100 confirms whether the test software conforms to preset test conditions.

The terminal placement unit 200 arranges at least one terminal to be verified and applies test software to each terminal.

The test software may be defined as an operating system (Operating System) and a basic application installed in the terminal. For example, the operating system can be any of Symbian, Android, iOS, Blackberry OS, Windows Phone, Linux, Web OS, etc. The default application is Android based phone call, send / (APK) associated with the record and contact record.

Since the connection terminal (USB port, COM port, etc.) of each terminal is electrically connected to the terminal seating unit 200, the test software can be transmitted using the connection terminal of each terminal.

The basic test unit 300 drives the test software to advance the basic test and generate basic test data. The basic test unit 300 conducts a test by transmitting an electrical control signal through a connection terminal (USB port, COM port, etc.) of each terminal.

That is, the basic test unit 300 drives the software of the terminal equipped with the test software to advance the basic test, and then stores the test result as basic test data.

The basic test includes at least one of a telephone call, a message sending / receiving, a memo record, a schedule record, and a contact record,

For example, the basic test unit 300 drives an application related to memo recording and stores the result of the operation as basic test data.

After all the basic tests are completed, a plurality of terminals are automatically transferred to the repeated test sections 410 and 420. At least one of the repeated test sections 410 and 420 is provided. In this embodiment, two repetitive test sections, that is, a first repetition test section 410 and a second repetition test section 420 are provided.

The iterative test units 410 and 420 sequentially move each terminal that has completed the basic test and proceed to at least one iterative test and generate each of the repeated test data.

Repeated tests include power off, file read / write, power on / off, booting, sleep / wakeup, and cover open Cover open).

For example, assuming that the test of the first iteration test unit 410 is defined as a file write / read and the test of the second iteration test 420 is defined as booting,

The first repetition testing unit 410 repeatedly performs file writing / reading (File Read / Write) and stores the progress result as first repeated test data.

Also, the second repetition testing unit 420 repeats the booting and stores the progress result as the second repetition test data.

On the other hand, the software control unit 500 can modify the test software based on the basic test data and the repeated test data.

Basic test data stores test results for telephone calls, sending / receiving messages, memo records, calendar records, and contact records.

In addition, the repeated test data includes power off, file read / write, power on / off, booting, sleep / wakeup, Test results for cover open are stored.

Therefore, the software control unit 500 may analyze the basic test data, the first repetitive test data, and the second repetitive test data to modify the test software for testing the terminal.

For example, when the basic test data in which the memo recording test result is stored and the repeated test data in which the file write / read (File Read / Write) test result is stored are provided to the software control unit 500, Change the test software through the process of.

At this time, the test result is determined to be defective / normal whether or not the terminal groups are tested at the same time. For example, if the number of terminals of the first terminal group tested simultaneously is five, and the operation of three or more terminals is bad, the test result of the first terminal group is determined to be bad. When the number of terminals of the second terminal group tested simultaneously is seven, when the operation of four or more terminals is bad, the test result of the second terminal group is determined to be bad.

Therefore, whether the test result is defective or not is judged for each terminal group unit.

First, when the memo recording test result of the terminal group is defective and the file read / write test result is also defective, the software control unit 500 changes the version of the operating system (Operating System) , And controls the terminal mounted on the terminal seating unit 200 to proceed with the test.

Next, when the memo recording test result of the terminal group is bad and the file read / write test result is normal, the software control unit 500 changes the version of the basic application among the test software, So that the mobile terminal 200 is tested.

Next, when the memo recording test result of the terminal group is normal and the file read / write test result is bad, the software control unit 500 determines the version of the operating system (Operating System) And controls the version of the basic application to be changed so that the test of the terminal mounted in the terminal seating unit 200 is performed.

Next, when the memo recording test result of the terminal group is normal and the file write / read test result is normal, the software control unit 500 keeps the test software in the same state, The mobile terminal is tested.

For reference, the terminal seating unit 200 is provided with a power supply unit to supply power to the terminal,

When the software control unit 500 corrects the test software, the software control unit 500 transmits a power control signal to the power supply unit of the terminal seating unit 200 to measure the driving voltage level and the driving current amount provided by the power supply unit, Can be set to be variable.

That is, a period in which a basic test of a terminal is performed, that is, a period in which one kind of basic test is performed, is divided into a plurality of intervals, and a driving voltage level and a driving current amount are controlled to be supplied differently for each interval.

For example, when the period in which one basic test is performed is divided into the first period to the tenth period in time sequence, the driving voltage level is gradually lowered (the amount of current is fixed) during the first period to the fifth period, To the tenth section, the drive voltage level of the fifth section can be maintained and the drive current amount can be gradually controlled.

As another example, the amount of current gradually decreases (the drive voltage level is fixed) during the first to fifth periods, while the amount of current in the fifth period is maintained during the sixth to tenth periods and the drive voltage level is gradually decreased Can be controlled.

The first example (drive voltage level descent) and the second example (current amount descent) may be performed sequentially.

At this time, the test results according to the change of the driving voltage level and the driving current amount for each section are all stored in the basic test data.

The software control unit 500 tests a predetermined number of terminals (a plurality of terminal groups) through the above-

After aligning the defect rate of the terminal operation based on the test results of all the basic test data corresponding to the respective test conditions (software version, voltage level, and current amount) and the test results of all the repeated test data,

It is determined that each test condition (software version, voltage level, and current amount) having the lowest defect rate is determined as a final test condition, and all the terminals are tested again, and the final determination as to whether each terminal is good or not is finally controlled.

At this time, the software control unit 500 repeats the above-described process for determining the final test condition every time the hardware version of the terminal is changed. The terminal seating unit 200 basically aligns the terminals having the same hardware version to form one test group.

For reference, the connection terminal (USB port, COM port, etc.) of the terminal settlement unit 200 and each terminal is electrically connected through a cable, as well as the wireless communication module of the terminal settlement unit 200 and the wireless communication Because modules can be connected wirelessly,

The test software can be delivered at the connection terminal of each terminal or wireless communication method. Here, the wireless communication module may be defined as a Bluetooth communication module.

The basic test unit 300 drives the test software to advance the basic test and generate basic test data. In this case, since the wireless communication module of the basic test unit 300 and the wireless communication module of each terminal can be connected in a wireless manner, the basic test unit 300 can connect the connection terminal (USB port, COM port, etc.) The test is carried out by transmitting an electrical control signal through the test circuit.

That is, the basic test unit 300 drives the software of the terminal equipped with the test software to advance the basic test, and then stores the test result as basic test data. At this time, the basic test data can be transmitted in real time to the software control unit 500 through the wireless communication method.

That is, since the basic test unit, the repeat test unit, the terminal mount unit, and the software control unit include the Bluetooth wireless communication module, they can be configured to exchange data in a wireless manner with each other.

Therefore, the software control unit can receive the basic test data and the repeated test data wirelessly in real time, and can transmit the modified test software directly to the terminal in a wireless manner or can be controlled to be transmitted in a wireless manner.

In addition, the software control unit performs a test of a predetermined number of terminals at the same time using a wired method and a wireless method, and then compares the result of the test in the wired manner and the test result in the wireless manner. At this time, if the test results of the wired method and the wireless method match, the terminal that is supplied later conducts the test only in a wireless manner. That is, the test software, the basic test data, and the repeated test data are wirelessly transmitted and received while the test is performed.

At this time, the test is performed periodically in a wired manner at regular test intervals, and then compared with the result of the wireless method. If the results match, the test is continuously conducted wirelessly. If the result is different, .

2 is a diagram illustrating a terminal software verification method of FIG.

Referring to FIG. 2, as described above, the terminal software verification method of the terminal software verification system 1 includes:

(S10) confirming hardware version information, software version information, voltage information, battery remaining amount, test items, and test progress procedure,

(S20, S30) of arranging at least one terminal to be tested and applying test software to each terminal,

A step (S40, S50) of driving the test software to proceed with the basic test and generating basic test data,

A step (S62, S64, S66, S68) of carrying out at least one or more repeated tests and generating respective repeated test data while sequentially moving each terminal having undergone the basic test,

A step S70 of modifying the test software based on the basic test data and the repeated test data is performed.

Herein, the basic test includes at least one of telephone conversation, message sending / receiving, memo recording, schedule recording, and contact recording, and the repetitive test includes power off, file read / Write, power on / off, boot, sleep / wakeup, and cover open.

The terminal software verification system and the verification method thereof according to the embodiment of the present invention can improve the test reliability by modifying the test software based on the results of the basic test and the repeated test.

Thus, those skilled in the art will appreciate that the present invention may be embodied in other specific forms without departing from the spirit or essential characteristics thereof. It is therefore to be understood that the embodiments described above are to be considered in all respects only as illustrative and not restrictive. The scope of the present invention is defined by the appended claims rather than the detailed description and all changes or modifications derived from the meaning and scope of the claims and their equivalents are to be construed as being included within the scope of the present invention do.

100: test verification unit
200: Terminal seating part
300: Basic test section
410, 420: Repetition test section
500: Software control section

Claims (5)

A test verifying unit for confirming hardware version information, software version information, voltage information, remaining battery amount, test items and test proceeding procedures;
A terminal seating part for sorting at least one terminal to be tested and applying test software to each terminal;
A basic test unit for driving the test software to proceed with the basic test and generate basic test data;
At least one or more repetition testing units for sequentially performing at least one repetition test and generating repetitive test data while sequentially moving each of the terminals for which the basic tests have been completed; And
And a software controller for modifying the test software based on the basic test data and the repeated test data,
Wherein the basic test includes at least one of a telephone call, a message sending / receiving, a memo record, a schedule record, and a contact record, and the repetitive test includes power off, file read / A power on / off, a boot, a sleep / wakeup, and a cover open. In this case,
The software control unit may be configured to transmit a power control signal to the power supply unit of the terminal seating unit to vary the driving voltage level and the driving current amount by a predetermined time unit, For example,
The control unit controls the driving voltage level and the driving current amount to be supplied differently for each section after dividing the section in which the basic test is performed, that is, the section in which one type of basic test is performed, into a plurality of sections,
The driving voltage level is gradually decreased (the amount of current is fixed) during the first period to the fifth period, and the driving voltage level of the driving voltage in the sixth period to the tenth period is gradually decreased Level and the driving current amount is controlled to be gradually lowered,
During the eleventh to fifteenth intervals, the amount of current gradually decreases (the driving voltage level is fixed). During the sixteenth to twentieth periods, the amount of current in the fifteenth section is maintained and the driving voltage level is gradually controlled to be low,
The software control unit tests a predetermined number of terminals and then aligns the defective rate of the terminal operation based on the test results of all the basic test data corresponding to the respective test conditions (voltage level and current amount) and the test results of all the repeated test data after,
Determining a test condition (voltage level, current amount) having the lowest defect rate as a final test condition, testing all terminals again, and finally determining whether each terminal is good or not.
delete Confirming the hardware version information, the software version information, the voltage information, the remaining battery amount, the test items and the test proceeding procedure;
Arranging at least one terminal to be verified and applying test software to each terminal;
Driving the test software to proceed with the basic test and generate basic test data;
Performing at least one or more repeated tests while sequentially moving each of the terminals having undergone the basic test and generating repeated test data; And
And modifying the test software based on the basic test data and the repeated test data,
Wherein the basic test includes at least one of a telephone call, a message sending / receiving, a memo record, a schedule record, and a contact record, and the repetitive test includes power off, file read / And at least one of a write, a power on / off, a boot, a sleep / wakeup, and a cover open.
In varying the driving voltage level and the driving current amount in units of a predetermined time when power is supplied to the terminal,
The control unit controls the driving voltage level and the driving current amount to be supplied differently for each section after dividing the section in which the basic test is performed, that is, the section in which one type of basic test is performed, into a plurality of sections,
The driving voltage level is gradually decreased (the amount of current is fixed) during the first period to the fifth period, and the driving voltage level of the driving voltage in the sixth period to the tenth period is gradually decreased Level and the driving current amount is controlled to be gradually lowered,
During the eleventh to fifteenth intervals, the amount of current gradually decreases (the driving voltage level is fixed). During the sixteenth to twentieth periods, the amount of current in the fifteenth section is maintained and the driving voltage level is gradually controlled to be low,
After a certain number of terminals are tested, the defect rate of the terminal operation is sorted on the basis of the test results of all the basic test data corresponding to the respective test conditions (voltage level and current amount) and the test results of all the repeated test data,
Determining each test condition (voltage level, current amount) having the lowest defect rate as a final test condition, testing all terminals again, and finally determining whether each terminal is good or not. delete delete
KR1020160073073A 2016-06-13 2016-06-13 Terminal software verification system and verification method KR101664150B1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
KR1020160073073A KR101664150B1 (en) 2016-06-13 2016-06-13 Terminal software verification system and verification method

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
KR1020160073073A KR101664150B1 (en) 2016-06-13 2016-06-13 Terminal software verification system and verification method

Publications (1)

Publication Number Publication Date
KR101664150B1 true KR101664150B1 (en) 2016-10-10

Family

ID=57146465

Family Applications (1)

Application Number Title Priority Date Filing Date
KR1020160073073A KR101664150B1 (en) 2016-06-13 2016-06-13 Terminal software verification system and verification method

Country Status (1)

Country Link
KR (1) KR101664150B1 (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107908557A (en) * 2017-11-14 2018-04-13 上海电子信息职业技术学院 A kind of embedded software credible attribute modeling and verification method

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20050043982A (en) * 2002-09-20 2005-05-11 인터내셔널 비지네스 머신즈 코포레이션 Method and apparatus for automatic updating and testing of software
KR100713469B1 (en) 2005-07-05 2007-04-30 삼성전자주식회사 Device and method for software inspecting of wireless terminal
KR20090068677A (en) * 2007-12-24 2009-06-29 삼성전기주식회사 Apparatus and method for testing communication system with wifi
KR100991198B1 (en) * 2008-04-28 2010-11-01 (주)밸류플러스 Test and program download device for mobile-phone

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20050043982A (en) * 2002-09-20 2005-05-11 인터내셔널 비지네스 머신즈 코포레이션 Method and apparatus for automatic updating and testing of software
KR100713469B1 (en) 2005-07-05 2007-04-30 삼성전자주식회사 Device and method for software inspecting of wireless terminal
KR20090068677A (en) * 2007-12-24 2009-06-29 삼성전기주식회사 Apparatus and method for testing communication system with wifi
KR100991198B1 (en) * 2008-04-28 2010-11-01 (주)밸류플러스 Test and program download device for mobile-phone

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107908557A (en) * 2017-11-14 2018-04-13 上海电子信息职业技术学院 A kind of embedded software credible attribute modeling and verification method
CN107908557B (en) * 2017-11-14 2020-10-20 上海电子信息职业技术学院 Embedded software credible attribute modeling and verifying method

Similar Documents

Publication Publication Date Title
CN101690303B (en) Method for testing mobile radio device
CN102914704B (en) Automatic testing device, automatic testing system and automatic testing control method
CN103631707A (en) Method and device for obtaining code coverage rate
CN113407393B (en) Chip verification method, terminal device, verification platform and storage medium
CN106685479B (en) Fault excitation method and system in RS485 communication of electric energy meter
CN108228465A (en) A kind of Software function test method and device
US20140149815A1 (en) System and method for programming chips on circuit board through boundary scan technology
CN106776323B (en) Application testing method and device
CN105842559A (en) Test result write-in method, test result write-in device, testing system and mobile terminal
CN110362469A (en) Based on modular testing use-case control method, device, terminal and storage medium
CN111679982A (en) Automatic testing method for REST API (representational State transfer) interface software
CN112735505A (en) System and method for testing memory chip
KR101664150B1 (en) Terminal software verification system and verification method
CN103064772A (en) Mobile terminal test method and system
CN101277504A (en) Method, system and apparatus for testing wireless performance
CN110597675A (en) Chip testing method and device, storage medium and burner
CN110544505B (en) Test system and method for screening poor Die in Wafer
CN113032200A (en) Micro control unit processing method and related equipment
CN115422091B (en) Firmware debugging method and device, electronic equipment and storage medium
CN100426248C (en) Test system and method for network additive storage device
CN105471582B (en) Resource acquiring method, system and relevant device
CN108834126B (en) Card changing equipment and method
CN101080084B (en) Roaming function test system, device and method
CN108334448A (en) Code verification method, apparatus and equipment
CN111124881B (en) eMMC firmware test method and device

Legal Events

Date Code Title Description
E701 Decision to grant or registration of patent right
GRNT Written decision to grant